After MC loads, settings can be found reset to default, including at least:
- Keyboard & Mouse > Mappings
- General > Tutorial
- Video > In-game graphics mode switching
- Video > Mode > all
No error is thrown. But regardless of whether the issue is triggered, minecraft.log details one of two warnings:
- libEGL
ok Game closed (exit 0).
info No known cause. Logs: ....
- page fault
ok Game closed (exit 0).
warn Likely cause:
warn • Minecraft itself crashed with a memory access violation ....
It's unclear whether this issues occurs after launching or after exiting MC.
It occurs whether BOL stays running or is just started.
It occurs after no particular number of game plays.
It occurs after no particular in-game actions.
It seems unrelated to the frequent memory access violations.
As I've observed it only in Ray Traced mode, it may be related to ray tracing generally or the Vanilla RTX/BetterRTX mod specifically.
BOL 2.1.4 (and earlier) AppImage (and AUR bin), AMD, Nvidia, Hyprland, CachyOS
After MC loads, settings can be found reset to default, including at least:
No error is thrown. But regardless of whether the issue is triggered, minecraft.log details one of two warnings:
It's unclear whether this issues occurs after launching or after exiting MC.
It occurs whether BOL stays running or is just started.
It occurs after no particular number of game plays.
It occurs after no particular in-game actions.
It seems unrelated to the frequent memory access violations.
As I've observed it only in Ray Traced mode, it may be related to ray tracing generally or the Vanilla RTX/BetterRTX mod specifically.
BOL 2.1.4 (and earlier) AppImage (and AUR bin), AMD, Nvidia, Hyprland, CachyOS