Skip to content
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

[Bug]: Water surface rendering issue after updating modpack to 1.1.0 and shaders to 5.1.1 #1814

Open
MaximusXXVIII opened this issue Feb 9, 2024 · 3 comments
Labels
Bug Something isn't working

Comments

@MaximusXXVIII
Copy link

MaximusXXVIII commented Feb 9, 2024

Possible Fixes

Yes

Modpack Version

1.1.0

What happened?

Hey, so I have an issue where if the unbound 5.1.1 shaders are enabled and I go underwater the surface of the water does not seem to render as it should:
huh
The body of the water itself is rendering fine, it seems, and I can see clearly inside and when I'm outside the water I see no issues, so the issue is only when you're underwater and looking at the surface of the water, as seen in the screenshot above. Pretty sure that's not how it's supposed to look.

This issue doesn't reproduce in reimagined 5.1.1, screenshot below:
huh2
Pretty sure that's how it's supposed to look in unbound as well when you're underwater.

This didn't happen before I updated the modpack to 1.1.0, I was on 1.0.25, and the shaders were 4.7.2 where I didn't have this issue.

Any ideas?

latest.log

https://gist.github.com/MaximusXXVIII/76ed5fac4f3e3e2ccd74e9e0614b1060

@MaximusXXVIII MaximusXXVIII added the Bug Something isn't working label Feb 9, 2024
@MaximusXXVIII
Copy link
Author

MaximusXXVIII commented Feb 9, 2024

For the record, I've already pinged about this issue on the Complementary discord server and they said that it's most likely a mod-related issue.

I wonder if anyone else using ATM8 1.1.0 and unbound 5.1.1 encountered it?

@MaximusXXVIII
Copy link
Author

MaximusXXVIII commented Feb 9, 2024

Just to make sure, I added Complementary 4.7.2 back, enabled it, and there we have it:
amazing

Same ATM8 version, 1.1.0, of course.

So, this issue is specific to unbound 5.1.1.

Also, I downloaded and enabled unbound versions 5.1, 5.0.1 and 5.0 and the same issue reproduced so this issue is specific to unbound v5.

@MaximusXXVIII
Copy link
Author

So, uh, it's been 3 weeks since I opened this. Nothing? No one encountered this issue?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant