-
Notifications
You must be signed in to change notification settings - Fork 815
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
End crystals render incorrectly sometimes with Complementary and Euphoria Patches since Sodium 0.6.0-beta.3 #2916
Comments
Does this reproduce with the latest release of sodium? |
Yes it persists in all versions since beta 3. If it was already fixed I wouldn't report it. |
It was not clear whether this is still an issue given that your logs use outdated versions. Thank you for clarifying. |
the issue first appears in commit 3fd78d9 |
Does it work with OptiFine? |
This feature is iris exclusive so no. |
It's probably a shader bug |
Both gri and I don't really understand this issue, unfortunately. Quote from gri "so I don't think I understand what's going on much better than you" :p |
I don't know what is causing the issue here, as the commit the bug was bisected to looks correct to me, and hasn't caused regressions elsewhere. |
IMS, Jelly and the shader devs all dazed by this issue. Hmmm Btw can I get a latest build but with this commit reverted? Just to be double sure its the cause |
The commits can be reverted cleanly on trunk. You can checkout the code and run the following commands:
|
yeah reverting these comits does fix the issue so it's definitely them |
Considering there is nothing in the shader-side code that relied on specific vertex ordering I think it's most likely this is an Iris issue where some code in Iris hasn't been updated to work correctly with the vanilla vertex order. Which will probably be an tremendous pain to find. Unless an Iris side fix is found, would reverting these commits be on the table? Or is core shader support higher priority? |
The patches are not going to be reverted. They are fixing problems that are more severe than what you have demonstrated. If someone knows what is causing the problem and can submit a patch to resolve this bug, and it doesn't re-introduce the problems the original patches were fixing, then we will accept that. |
I cannot find any code in Iris that relies on this specific ordering. This sounds like a shader assumption to me. |
Bug Description
Sodium had a weird regression which causes the voxelized end crystal effect from Euphoria Patches to jitter a lot.
I know sodium's the cause because I compared on the same minecraft & iris version so the only difference was sodium.
The issue first appears in Sodium 0.6.0 Beta 3 more specifically in this commit 3fd78d9
Video:
https://github.com/user-attachments/assets/36ad60ce-f938-4462-940d-18803f08e059
Reproduction Steps
ComplementaryUnbound_r5.3 + EuphoriaPatches_1.4.1.txt
/execute in minecraft:the_end run tp @s -31.54 107.00 -0.43 292.05 32.40
Log File
2024-12-06-7.log
Crash Report
crash-2024-12-06_01.14.07-client.txt
The text was updated successfully, but these errors were encountered: