Embeddium + Supplementaries Forge 1.20.1 - Vertex Culling/Tearing Issues #536
Description
Bug Description
(NOTE: I originally reported this bug on the Supplementaries Discord server here.)
I've encountered rendering issues with Supplementaries and Embeddium that I wanted to share here. I've tested this to the best of my ability, and have been able to re-create them consistently.
When playing with both Supplementaries and Embeddium alongside other mods, I get what seems like vertex culling issues/tearing. I also get the following errors in my log (these occur even when it's just Supplementaries and Embeddium):
[Render thread/ERROR] [Embeddium-MixinTaintDetector/]: Mod mixin into Embeddium internals detected. This instance is now tainted. The Embeddium team does not provide any guarantee of support for issues encountered while such mods are installed.
[Render thread/WARN] [Embeddium-MixinTaintDetector/]: Mod(s) [supplementaries] are modifying Embeddium class me.jellysquid.mods.sodium.client.render.chunk.compile.pipeline.FluidRenderer, which may cause instability.
When just playing with Supplementaries and Embeddium, there aren't any noticeable tearing issues. However, when adding more mods to the instance, the issues become much more noticeable.
I've found that enabling the "Use Compact Vertex Format" setting in Embeddium helps slightly, but the issue still occurs.
Reproduction Steps
- Create a modded Minecraft instance with the following Forge version and mod list:
Forge Version: 47.4.10
Mod List Used During Testing:
Allurement 4.0.0
Autumnity 5.0.2
Blueprint 7.1.3
Boatload 5.0.1
Embeddium 0.3.31
Endergetic Expansion 5.0.1
Environmental 4.1.2
Neapolitan 5.1.0
Savage & Ravage 6.0.1
Supplementaries 1.20-3.1.41
Supplementaries Squared 1.20-1.1.28
Upgrade Aquatic 6.0.3
(NOTE: The Team Abnormals mods are there just because I needed a group of mods to test with.)
- Create a new Superflat world. You should see tearing/culling issues most prominently near the horizon, but also near the foreground as you walk/move the camera around.
Removing Supplementaries from the instance after the fact stops these issues from occurring, but I was recommended by the Supplementaries devs to post this here.