Bug with textures displaying the error texture when using sodium with modpack
steliosfil opened this issue ยท 6 comments
I just discovered Sodium and used it in a modpack (All Of Fabric 3) to test it.
I have Sodium version sodium-fabric-mc1.16.3-0.1.0 and AOF3 version 2.6.9 according to CurseForge
At first I was SURPRISED of the performance increase, but then noticed that some textures were displaying the error texture.
Tried the modpack again without Sodium, everything is fine. Placing Sodium back in, same textures display the error texture.
Already checked if the models/blocks of the items display the same error texture... but nope. Models/blocks are just fine and the item texture is bugged.
You can see in the last image that I'm holding the bugged oak sapling, but the model itself is fine.
As I checked the error textures it seems there is no patern, just random textures appear bugged.
Effectively a duplicate of #5 (i think)
Fabric Rendering API is not implemented in sodium at the moment. it is on the road map, no eta
I posted this because I've read people saying that it doesn't even launch their game, but it does launch mine, it's just the textures that are bugged.
This is due to the lack of Fabric Rendering API compatability. Some mods in that mod pack use the FRAPI, and hence their textures break
Oh okay, I really thought it was something else because I haven't seen any post that is similar to my case
This is still caused by lack of Fabric Rendering API support, and you will likely run into more issues. Last I checked, many Applied Energistics 2 blocks would crash the game with Sodium.
For now it would be best to play AoF3 without Sodium, or you could look into using Indium to add FRAPI support to Sodium (another project, not by us).