Mekanism

Mekanism

111M Downloads

[Crash] The game crashed whilst rendering overlay Error: net.minecraftforge.fml.ModLoadingException

DeclineD-Com-AMXX opened this issue · 10 comments

commented

Issue description

The game crashed whilst rendering overlay Error: net.minecraftforge.fml.ModLoadingException: Mekanism (mekanism) encountered an error during the done event phase

ERROR: 0:43: error(#162) Wrong operand types no operation ':' exists that takes a left-hand operand of type 'const int' and a right operand of type 'float' (or there is no acceptable conversion)

I've researched the problem hoping it would be my fault and tried everything but i can't get past this.

Steps to reproduce

No response

Minecraft version

1.19.2 (Latest)

Forge version

43.2.6

Mekanism version

Current Dev Branch (Manually Compiled)

Other relevant versions

No response

If a (crash)log is relevant for this issue, link it here: (It's almost always relevant)

https://pastebin.com/Z18UZgJB

commented

Does it happen without Rubidium? I'm also not familiar with all the mods you have, so consider others that might change rendering

commented

With Rubidium. As you mentioned it i'm gonna change it with Sodium and Indium and see if it still occurs, hopefully not.

commented

It probably has something to do with this line: https://github.com/mekanism/Mekanism/blob/1.19.x/src/main/resources/assets/mekanism/shaders/core/rendertype_mekasuit.fsh#L44 but I am guessing it is due to some other mod installed doing weird things to loading shaders. Does this crash happen when you are only using Mekanism?

commented

It seems that for this modpack i use, ALL THE MODS 8, it uses Rubidium to render something .. I tried with simple optifine and what i said above and either crash with errors or crash with error code 1 which can't be.

Can it be my java version? Or that i have an older graphics card? (ATI Radeon HD 3800)

(net.minecraftforge.fml.ModLoadingException: Mekanism (mekanism) encountered an error during the done event phase
§7net.minecraft.server.ChainedJsonException: Invalid shaders/core/rendertype_mekasuit.json: Couldn't compile fragment program (Mod Resources, mekanism:rendertype_mekasuit) : Fragment shader failed to compile with the following errors:
ERROR: 0:43: error(162) Wrong operand types no operation ':' exists that takes a left-hand operand of type 'const int' and a right operand of type 'float' (or there is no acceptable conversion))

commented

It could be (

) When you initialize a float doesn't the value have to be a float (0.0, 2.0, 2.4) instead of a simple integer?

float fog = 384.0f;

commented

Never tried Mekanism alone. I was using this modpack 'All the mods 8' and to some people it works but as the problem occurs when probably other mods come in (i will test tommorow since it's 3am here) i thought thst you should add that 'compatibility' so we can use this mod with many other mods. As i said idk for sure.

Also tried to change some lines in the mod's already compiled files (somehow it s still openable) and got me no better results but i will try changing that really fast to 0.0f and see if it occurs

commented

I'm getting this as well as part of Enigmatica 9 (version 1.4.2) with Mekanism-1.19.2-10.3.8.477 / Forge 43.2.4,
I've tested it on Enigmatica 9 with/without optifine/rubidium.
I've tested it on a fresh 1.19.2 install with just Forge (43.2.0, 43.2.4, 43.2.14) and Mekanism (with/without generators) and it still happens. Fresh install without mekanism is able to load.

https://pastebin.com/kVANtMX8

This is on ATI Mobility Radeon series 4500, so at least that's a pattern. No ATI drivers on win10 for this, just whatever Microsoft supplies.

commented

Hmm I will talk with some people about this, I wonder if maybe it is a gl implementation specific thing and has to do with the hardware you are on, and if so how to best maybe get around it.

commented

Thank you for looking into this. I realize it's an edge case.
I can test something if needed.

commented

Thank you! I edited it in, works.