-
Notifications
You must be signed in to change notification settings - Fork 77
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
Broken rendering with Iris when shaders are enabled #416
Comments
Does this also happen with the release version? |
Yes, I can confirm that this happens using the latest 1.18.2 release versions of iris, sodium, and antique atlas |
According to #448 it also happens on forge |
Still a problem on iris 1.4.3, sodium 0.4.1 build 15 & indium 1.0.7 when using shaders but not when disabling shaders. |
Fixed in 99330bd thanks to @LangYueMc |
Turns out, those patches don't resolve the issue properly. |
This reverts commit 99330bd. Neither this commit alone, nor the follow-up commit solves the problem. It feels like a work-around and I haven't even understood the underlying problem yet. So I'm going to revert it for now.
This reverts commit 99330bd. Neither this commit alone, nor the follow-up commit solves the problem. It feels like a work-around and I haven't even understood the underlying problem yet. So I'm going to revert it for now.
I made a resource pack that kinda band-aid fixes this. The issue is with pixels with mixed transparency values overwriting other ones. This resource pack makes every pixel have 255 opacity. I think it works pretty well. I tested it with oculus on complementary. |
Describe the bug
Atlas rendering bug (see screenshots)
To Reproduce
Compile for 1.18.1 from 37038a3
Install Sodium and Iris
Enable shaders (e. g. BSL)
Expected behavior
Screenshots
Fabric version information:
Additional context
When Iris is installed, but no shaders are enabled, all renders normally
Sodium: 0.4.0-alpha5 (latest)
Iris: 1.1.3 (latest)
The text was updated successfully, but these errors were encountered: