You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
when you grab a sub level platform and put a powered AE2 setup on it the game crashes when saving the world, causing a "thread caused non-unwinding panic. aborting.", message in logs, followed by a core dump message and exit code 134
EDIT: ive done more testing, crash is directly related to Sable, game still crashes with Create: Aeronautics and Create removed,
versions and mods:
sable: 2.0.3
guideme: 21.1.16
AE2: 19.2.17
Some AE2 block would use setBlock to update neighboring block's state, for example this logic
That would trigger a sub level update back in sable
But at this time that sub level is already being removed, so the ID don't really exist in rapier's rigid body list
no entry found for key -> panic
Therefore based on my limited understanding, one possible fix would be to disable or defer any sub level property update (such as mass, pose, etc.) when it is about to be unloaded even if something happens to them. Or alternatively, the sub level can be fully settled first before it's removed from the rapier engine.
Hopefully this would help speed up any potential fix. Also a big thank you to the dev team for creating such a great mod
Edit: it seems an existing pull request, #1093 , can potentially fix this issue because they properly mark sublevels as removed and thus prevented these updates during removal.
Activity
[-]AE2 and sable incompatability[/-][+]AE2 and sable crash when saving world[/+]Water-Moon commentedon Jul 21, 2026
If it helps, here's my view on this issue while I attempted to fix a broken save.
I have managed to retrieve the exact stacktrace before this crash:
Dumped Call Stack
From this and based on the content in the native lib
sable/sable_rapier/src/main/rust/rapier/src/lib.rs
Lines 530 to 531 in 76e9ae7
Seems like what happened is that:
setBlockto update neighboring block's state, for example this logicno entry found for key-> panicTherefore based on my limited understanding, one possible fix would be to disable or defer any sub level property update (such as mass, pose, etc.) when it is about to be unloaded even if something happens to them. Or alternatively, the sub level can be fully settled first before it's removed from the rapier engine.
Hopefully this would help speed up any potential fix. Also a big thank you to the dev team for creating such a great mod
Edit: it seems an existing pull request, #1093 , can potentially fix this issue because they properly mark sublevels as removed and thus prevented these updates during removal.
noobte commentedon Oct 16, 2026
I have found through many crashes that it seems to be caused by (but probably not limited to) the ME IO Port block