-
Notifications
You must be signed in to change notification settings - Fork 811
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
Sodium still can't render water correctly #991
Comments
Layered translucency effects are not yet implemented, so the behaviour you're reporting with just water in 0.3.2 is a duplicate of #38 |
damn, i forgot to test barrier blocks, this will be broken also for light blocks. now on to why did this happen? it'll be caused by this here https://github.com/CaffeineMC/sodium-fabric/pull/892/files#diff-3486df2d697d632a02fa5eaeb85a0590a3a1e89df7c11488eeb9cf8b92d41fbbR324 the fix looks to be pretty simple, instead of checking for air i should have been checking |
Please keep this tone out of issues in the future. This is a free project that attempts to re-implement the entire chunk rendering pipeline. Like all software, it is subject to bugs. Water rendering in Minecraft is full of special cases and has been continuously hacked on to with every update of the game. It is not entirely straight forward to fix all these cases, and we sometimes miss regressions when one hacky behavior breaks another hacky behavior. |
You know what, you're totally right. My bad. Real quick, can I ask a question about the labels you have added to this issue? |
Yeah, I've noticed some stuff like that. I mean, I really appreciate how much optimization Sodium is able to pull off. Without Sodium, my computer can't get any better than like 20 fps in Minecraft. I just wish they could figure out how to make water look right. |
Still happens sadly and it's really jarring to look at. It's especially jarring behind ice or even worse behind tinted glass. |
Closing this issue and moving to a new one at #1369, as this issue is still present in newer versions of Sodium and Minecraft. |
We know the issue still happens, and it is being worked on. Creating new issues to report the same problem so that it "gets looked at" is not going to result in anything but the issue tracker getting spammed. |
According to the author of PepperCode1/Continuity#245, this bug still happens, but when the overlay texture is used should not deviate from vanilla since commit a2bb59e. Does this issue still happen or is there a different but seemingly related issue? |
The incorrect water overlay sprite has been fixed. The water having "holes" inside of it when looking at it from certain angles is a different issue (#38). |
Version information
sodium-fabric-mc1.17.1-0.3.3+build.8
Expected Behavior
When I began using Sodium a few months ago, I immediately noticed the performance improvements. This was expected/as advertised. However, I also expected Sodium to render things to look the same as they do in Vanilla Minecraft. This turned out to not be the case. For months now, Sodium has completely failed to render water columns correctly.
Actual Behavior
To demonstrate the problems that have existed in Sodium and still exist in Sodium with water rendering, I constructed a hollow column of barriers, into which I poured a water bucket. Only the top water block is a source block; the rest of the column is downward-flowing. It looks like this:
I then positioned myself at a specific angle, looking at the water column, and I took screenshots of the column in Sodium 0.3.2, Sodium 0.3.3, and Vanilla 1.17.1. Here are the results:
Next, I converted the entire column of water into water source blocks by placing kelp all the way up the column. I then positioned myself at the same angle as before, and took screenshots in the same three versions as before. Here are the results:
Reproduction Steps
Make a column of water, then run/fly around and look at it from assorted angles. Seriously, that's all you have to do.
Java version
16.0.1 64bit
CPU
Intel Core i7-10510U
GPU
NVIDIA GeForce MX250
Additional information
No response
The text was updated successfully, but these errors were encountered: