-
-
Notifications
You must be signed in to change notification settings - Fork 55
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Doesn't load past mojang screen with Automobility (MOD INCOMPAT) #246
Comments
Try with just Steam 'n' Rails + Create |
Delete a mod called "MemoryLeakFix" |
Okay that worked, it doesn't crash but it still wont get off the "mojang" screen. here's another log: https://mclo.gs/xyEfENh |
Can you try just steam n rails + create? |
It works with just those two, the problem is that I want to know whats causing it to not work in the modpack. I'm trying to find the other incompatibilities as well and maybe hopefully get them fixed or at least known about. |
Try a binary search and if you find out what causes it let me know and I'll see if it's fixable on our side https://en.m.wikipedia.org/wiki/Binary_search_algorithm |
@IThundxr Found it. It was Automobility. Game wouldn't load pass the loading screen with it in. And yeah, memoryleakfix won't load with it either, but that was already known I think. Automobility Version: automobility-0.3+1.18.2 (latest release for 1.18.2) |
That's weird it works on 1.20 I guess this version is just too old and doesn't work |
@ConqAra https://modrinth.com/mod/autos_n_rails should fix it |
Describe the Bug
Crashes during loading screen (right after launch)
Reproduction Steps
Use latest version (fyi im using my modpack so mod incompats are bewared.)
Expected Result
Load up the game without crashing.
Screenshots and Videos
No response
Crash Report or Log
https://mclo.gs/Fbr0IN2
Operating System
Windows 10
Mod Version
1.4.4
Create Mod Version
0.5.1c
Minecraft Version
1.18.2
ModLoader and Version
Fabric 0.14.22
Other Mods
No response
Additional Context
No response
The text was updated successfully, but these errors were encountered: