Updating 2.1.0 to 2.1.2 causes Ticking World crash
Latest.log is same info
Backdating to 2.1.0 fixes the issue. Connector seems to fail prelaunch phase due to a FastUtil error caused by this. I can't find any related posts on Connector's page.
4 Replies
Does it work without Syntra Connector?
Or without Fast Utils?
Compatibility error between 3 mods at once will be hard to fix
And Syntra Connector says that is is an experiment and many thing will break
Fast Utils is embedded in Forge Mods
Connector is not the issue, it's just failing because of the ticking entity
Connector is in Alpha and works fine in other instances. I use 2.1.2 in another instance with 100 more mods. It's the update action that broke this and I'm really unsure why. I could delete the LOD cache and it would probably fix it, but 2.1.0 works fine for now
That crash log doesn't appear to contain DH and since DH doesn't shade in fastutil I'm not sure how 2.2 would cause issues where 2.1 doesn't.
2.1.2*
I've had no other issues until just before this started when I updated 2.1.0 to 2.1.2
That's my only data
The crash log is provided as info that I can't necessarily read as well as you, but it seems to me as well that it says nothing useful for this particular crash. I think it just marks failures related, but not causing the crash, unfortunately
The log is usually straightforward in relation to Connector crashes, but see how even with all the Connector traces, it still says that it's not the suspected mod?
In any case, it's not an option to swap it because it's a larger modpack I'm not in charge of