![CensoredASM](https://media.forgecdn.net/avatars/thumbnails/358/827/256/256/637520208754289091.png)
LoliASM breaks Thermal Expansion's textures and causes crashes
SirSlender opened this issue ยท 21 comments
https://paste.dimdev.org/cokeviwofi.mccrash
Is the crash report. Anytime I go to break a Thermal Expansion machine the game crashes and their textures are no longer showing up correctly as an item (pink and black checkered box), but I can still place and use them.
I also get a constant message to add some string in my config but I don't know what string to add? I add what the console says but it still spouts the same message.
Is there any progress about this issue? I got the same problem. (no crash but wrongly rendered models in item format)
This was fixed a long time ago, if you're booting for the first time, simply restart.
This was fixed a long time ago, if you're booting for the first time, simply restart.
Not really, I keep getting the same result after dozens of restart since the mod is installed in my modpack dev environment
It happens because face is null when rendering thermal expansion machine items
I haven't had proper time to investigate this but I haven't gotten a crash yet from the times I've tried. For the mean time turn logClassesThatNeedPatching
off. I've noticed codechicken.lib.util.VertexDataUtils
isn't being patched properly; hence why the messages still pop up, but shouldn't have anything to do with the crash.
If the message says: class codechicken.lib.render.buffer.BakingVertexBuffer needs their BakedQuad calls redirecting! Insert the string into config/loliasm.json and report to Rongmario.
, you add codechicken.lib.render.buffer.BakingVertexBuffer
to bakedQuadPatchClasses
in loliasm.json
Try to do that and eliminate all errors then see if you still get the crashes. If not I'll check it out.
When I did that, those messages still showed up and the textures were still broken. Disabling the baked quads of course fixed the issue. My log is from after adding those strings.
Yeah I think I broke it because of a refactor in 2.3, I'll be fixing it later today, can you test with 2.1 or 2.2?
This was from 2.2 but I did also try 2.3. I can try testing with 2.1 later today.