Context
What I was doing:
I created a new world with Sable 2.0.3 and Create Aeronautics 1.3.0 on NeoForge 1.21.1. The game crashes immediately when the world loads, specifically during the initialization of the Rapier physics pipeline (Rapier3D.initialize). The crash is reproducible 100% of the time. Sometimes, after a crash and cleaning the .sable folder, the world loads once, but on subsequent re-entry, it crashes again.
What I've already tried:
- Changing Java runtime (Microsoft OpenJDK → Eclipse Temurin 21.0.11)
- Reducing/increasing memory (-Xmx8192M, -Xmx10000M)
- Disabling sound (all volume sliders to 0)
- Disabling AVX512 (via BIOS)
- Removing all other mods (only Sable + Create Aeronautics left)
- Deleting the
.sable folder and letting it regenerate
- Adding the
.sable folder and sable_rapier_x86_64_windows.dll to Windows Defender exclusions
- Checking for hanging
javaw.exe processes in Task Manager
- Trying older Sable versions (1.1.3, 1.2.2) – same crash
System information:
- OS: Windows 11 Pro (24H2, Build 26100.8521)
- CPU: AMD Ryzen 7 7800X3D
- GPU: NVIDIA GeForce RTX 5070 Ti (driver 610.62)
- RAM: 32 GB
- Java: Eclipse Adoptium Temurin 21.0.11+10 (64-bit)
- Mod loader: NeoForge 21.1.233
- Sable version: 2.0.3 (also tested 1.2.2 and 1.1.3)
- Create Aeronautics: 1.3.0
- Other mods: Create 6.0.10, Flywheel 1.0.6, Sodium 0.8.12 (and dependencies) – but crash also occurs without Sodium.
Crash details:
- Java error:
EXCEPTION_UNCAUGHT_CXX_EXCEPTION (0xe06d7363) in sable_rapier_x86_64_windows.dll at Rapier3D.initialize
- Windows Event Log:
BEX64 (0xc0000409) in OpenAL.dll (offset 0xa2b05) – but this seems collateral, as the crash originates in Rapier.
Additional notes:
I have seen similar reports from other users (e.g., issue #1016 and others). The crash appears to be related to the native library loading and initialization on Windows. The fix for path resolution in #1016 did not resolve the issue for me.
Attached logs:
hs_err_pid7080.log (JVM crash log)latest.log (Minecraft log)WindowsEventLog_BEX64_OpenAL.txt (extracted Windows Event Log entry)
Let me know if you need any further information. Thank you!
Crash Report
https://mclo.gs/6nRtPTv https://mclo.gs/0i0uhdX https://mclo.gs/Jgt7vpz
Context
What I was doing:
I created a new world with Sable 2.0.3 and Create Aeronautics 1.3.0 on NeoForge 1.21.1. The game crashes immediately when the world loads, specifically during the initialization of the Rapier physics pipeline (
Rapier3D.initialize). The crash is reproducible 100% of the time. Sometimes, after a crash and cleaning the.sablefolder, the world loads once, but on subsequent re-entry, it crashes again.What I've already tried:
.sablefolder and letting it regenerate.sablefolder andsable_rapier_x86_64_windows.dllto Windows Defender exclusionsjavaw.exeprocesses in Task ManagerSystem information:
Crash details:
EXCEPTION_UNCAUGHT_CXX_EXCEPTION (0xe06d7363)insable_rapier_x86_64_windows.dllatRapier3D.initializeBEX64(0xc0000409) inOpenAL.dll(offset 0xa2b05) – but this seems collateral, as the crash originates in Rapier.Additional notes:
I have seen similar reports from other users (e.g., issue #1016 and others). The crash appears to be related to the native library loading and initialization on Windows. The fix for path resolution in #1016 did not resolve the issue for me.
Attached logs:
hs_err_pid7080.log(JVM crash log)latest.log(Minecraft log)WindowsEventLog_BEX64_OpenAL.txt(extracted Windows Event Log entry)Let me know if you need any further information. Thank you!
Crash Report
https://mclo.gs/6nRtPTv https://mclo.gs/0i0uhdX https://mclo.gs/Jgt7vpz