[Issue] Stuck On Last Phase of World Load When Paired with Latest Versions of Selene/Supplementaries
JuicyCosmos opened this issue ยท 8 comments
Futurepack Version: 1.16.5-31.2.6976
During the last phase of entering/creating worlds, game is stuck in an infinite loop with the log spammed by
"[Render thread/WARN] [futurepack/]: FPRecyclerTimeManipulatorManager: Waiting for Init!".
Steps to reproduce the behavior:
- Boot up the game with latest version of Selene/Supplementaries (version 1.8.0 and 0.17.2 respectively)
- For example create a new world
- Get stuck on the last phase of world load
- Wait for a while, force quit the game
- Check the log and see the log spam
I do have a lot of other mods installed, but only after updating Selene/Supp do I encounter this error. Reverting back to previous versions of Selene/Supp solves the issue for now. I've asked MehVahdJukaar the author of Selene/Supp and they suggested I open an issue here as well. If there should be other mods at play, I could do some testing myself and see if I can isolate the case with a just a few mods. (Not for now since I don't want to mess up my keybinds)
Minecraft Version: 1.16.5
Forge Version: 36.2.2
Futurepack Version: 1.16.5-31.2.6976
I'll just put a screenshot of the log (creating a new world) here:
I am experiencing the same issue with supplementaries/selene disabled I don't think that it is just its fault
most likley their isRapirable method of one of their items is crashing or their mixin is affecting our mod.
Did a binary search and it turns the culprit for me is Roots Classic 1.16.5-1.1.9
Here is some logs if they help
debug.log
FP-Latest.log
latest.log
in my case roots classic was not installed and I managed to get this error so it seems that there is mroe to this
@mcenderdragon
An update should come out pretty soon-ish. For now we can simply avoid updating Selene/Supp.
This was yesterday afternoon BJT (UTC + 8hrs)
@mcenderdragon
The updated versions of Selene/Supp have been working for several days for me now without any issue. (At least for me) You can close the issue if you feel like. But if there's anything that can be optimized you can keep the issue as a reminder. I'm not seeing any issue on my side for now.