openmw.org

When the player's camera it at the edge of the surface of the water, almost submerged, this happens:

Close (reflection looks normal):


Closer (pixelated):


Closest (a mess):


Screenshots were taken on the 0.44 Release Build with all water shader settings turned on highest.

What kinda hardware and OS are you running? Do you have an idea to driver/module version for your GPU?

Wait, this isn't a thing for everyone? I assumed it was just how the water shader worked.

AnyOldName3 wrote: ↑26 Nov 2018, 01:55 Wait, this isn't a thing for everyone? I assumed it was just how the water shader worked.

I honestly can't tell if this is sarcasm or not.

No, I've legitimately always had this issue and thought it was an edge case where our shader's approach just wasn't very good rather than a bug where the behaviour was unexpected and therefore worth investigating and fixing.

I saw this once and chalked it up to a driver/module issue. Now I'm curious... I have Intel, Nvidia and Amd lying around.

Can anyone else chime in if they can reproduce this and with what GPU hardware and driver version?

For reference, I'm seeing this on a Vega 56 with AMD's proprietary Windows driver. I tested on another machine, too, which has a GT 850M and Nvidia's proprietary Windows driver and it didn't exhibit the issue. I couldn't test on that machine's integrated Intel GPU as it's not detected as having S3TC support properly.

My pics were taken from an RX 580, so it probably is an AMD issue. Latest drivers, Windows 10.

I also use a AMD GPU(R9 390) with 18.5.1 drivers and get this issue.

I'll try running the shader through a GLSL verifier in case it's a case of the shader relying on undefined behaviour.