UnsatisfiedLinkError: Rapier3D.initialize on Windows 11 — native library fails to load on world join

[Hopk-e]

Context

Description

Sable crashes every time a world is loaded with an UnsatisfiedLinkError when trying
to link its Rapier native library. The game launches fine but crashes immediately on
world load. Tested on Sable 1.2.1 and 1.2.2 — same crash on both versions.

Steps to Reproduce

1. Install Sable (1.2.1 or 1.2.2) on NeoForge 1.21.1
2. Launch Minecraft
3. Try to load/create any world

Expected Behavior

World loads normally.

Actual Behavior

Crash on world load with:

java.lang.UnsatisfiedLinkError: 'void dev.ryanhcode.sable.physics.impl.rapier.Rapier3D.initialize(int, double, double,
double, double)'
at dev.ryanhcode.sable.physics.impl.rapier.Rapier3D.initialize(Native Method)
at dev.ryanhcode.sable.physics.impl.rapier.RapierPhysicsPipeline.init(RapierPhysicsPipeline.java:116)
at dev.ryanhcode.sable.sublevel.system.SubLevelPhysicsSystem.initialize(SubLevelPhysicsSystem.java:159)
at dev.ryanhcode.sable.Sable.defaultSubLevelContainerInitializer(Sable.java:76)

Environment

• Sable version: 1.2.2 (also tried 1.2.1)
• NeoForge: 21.1.229
• Minecraft: 1.21.1
• Java: 21.0.3 Microsoft OpenJDK (64-bit)
• OS: Windows 11 Home (amd64) 10.0.26200
• CPU: Intel Core i9-13900HX
• GPU: NVIDIA GeForce RTX 4080 Laptop GPU

Troubleshooting Already Tried

• Reinstalled Sable jar
• Cleared Java temp folder (%TEMP%)
• Tried both Sable 1.2.1 and 1.2.2
• Checked Windows Defender protection history — no blocked items found

Crash Report

Crash Report

https://mclo.gs/3OQg5d1