Terrain is invisible with Sodium and MultiConnect
Felix14-v2 opened this issue ยท 2 comments
Description
When using Bobby with Sodium and MultiConnect installed, the world terrain stops being rendered. This doesn't occur without Sodium or MultiConnect, but only when 3 mods are installed together.
Info
- Minecraft 1.19.3
- Fabric 0.14.11
- Bobby 4.0.3
- Sodium 0.4.9
- MultiConnect 1.6 beta-26
Log File
Additional
MultiConnect #525
Cannot reproduce this on my machine with the exact versions given.
I can however get the game to crash with a similar error if I modify my sodium configuration to disable half of the mod like you apparently did:
[12:43:29] [main/WARN]: Force-disabling mixin 'features.chunk_rendering.MixinChunkBuilder' as rule 'mixin.features.chunk_rendering' (added by user configuration) disables it and children
[12:43:29] [main/WARN]: Force-disabling mixin 'features.chunk_rendering.MixinClientChunkMap' as rule 'mixin.features.chunk_rendering' (added by user configuration) disables it and children
[12:43:29] [main/WARN]: Force-disabling mixin 'features.chunk_rendering.MixinClientPlayNetworkHandler' as rule 'mixin.features.chunk_rendering' (added by user configuration) disables it and children
[12:43:29] [main/WARN]: Force-disabling mixin 'features.chunk_rendering.MixinClientWorld' as rule 'mixin.features.chunk_rendering' (added by user configuration) disables it and children
[12:43:29] [main/WARN]: Force-disabling mixin 'features.chunk_rendering.MixinPackedIntegerArray' as rule 'mixin.features.chunk_rendering' (added by user configuration) disables it and children
[12:43:29] [main/WARN]: Force-disabling mixin 'features.chunk_rendering.MixinPalettedContainer' as rule 'mixin.features.chunk_rendering' (added by user configuration) disables it and children
[12:43:29] [main/WARN]: Force-disabling mixin 'features.chunk_rendering.MixinWorldRenderer' as rule 'mixin.features.chunk_rendering' (added by user configuration) disables it and children
MultiConnect makes zero difference for me.
if I modify my sodium configuration to disable half of the mod like you apparently did
Wait WHAT
Probably, it was done by one of the previously installed mods...
Thank you anyway, and I'm sorry that I didn't notice this on my own. I usually test mod conflicts in a completely new instance, but this time my laziness won :)