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
My Friend and I played ATM8 and we wanted to build a lot of Fusion Reactors (10) inside the Mining Dimension from AllTheModium. When we plugged we started our pipes with either Tesseracts and any Item Transportation pipe or ME-System (import/export) busses the game instantly crashed.
Because of this crash, when trying to load the server or world in singleplayer the game would instantly crash again when loading in, with the same error in the attached crashlog.
Some additional info
Modpack: ATM8 v1.0.8
Alchemisty version: alchemistry-1.19.2-2.2.3.jar
5 of them had reciped locked and auto balancer off (1x Helium (2) & 1x Hydrogen (1) for 1x Lithium (3))
the other 5 had the reciped unlocked and the auto balancer on (2x Hydrogen (1) for 1x Helium (2))
This crash, very similar report, occurred on my server on ATM8 v1.0.9. Player was using a AE2 system to automate it. Could not load the region files specifically, it was a crash that required proper roll back of the region files associated with it.
It really looks like it is when the Reactor is in a different Dimension. We re-created the same setup with just 8 reactors instead of 10 in the overworld and it works fines.
This crash, very similar report, occurred on my server on ATM8 v1.0.9. Player was using a AE2 system to automate it. Could not load the region files specifically, it was a crash that required proper roll back of the region files associated with it.
We tried with a Tesseract and ME system. Both resulting in a crash. Even with forced loaded chunks
My Friend and I played ATM8 and we wanted to build a lot of Fusion Reactors (10) inside the Mining Dimension from AllTheModium. When we plugged we started our pipes with either Tesseracts and any Item Transportation pipe or ME-System (import/export) busses the game instantly crashed.
Some additional info
Crashlog
The crashlog is attached to this issue.
crash-2023-01-25_20.39.14-server.txt
The text was updated successfully, but these errors were encountered: