quakespasm icon indicating copy to clipboard operation
quakespasm copied to clipboard

Bad water transparency layering in start level

Open Macil opened this issue 2 years ago • 7 comments

In the start level (using the rerelease basedir), if you look at the water before episode 4, you can see that specific sections of the bottom surface incorrectly render over specific sections of the top surface. (Specifically, lower surface's far-left corner renders over any part of the upper surface, and the rest of the lower surface's left two-thirds renders over everything in the upper surface except for a section on the near-left.)

spasm0000

Related: https://github.com/Novum/vkQuake/issues/656. I thought this was vkQuake specific at first but guess not. This issue does show up slightly differently between the two ports though.

Macil avatar Mar 13 '23 09:03 Macil

@ericwa, @andrei-drexler, @Novum ?

sezero avatar Mar 13 '23 09:03 sezero

P.S.: Have you bisected this?

sezero avatar Mar 13 '23 09:03 sezero

It's been in each version I've tested so far, including 0.94.4 (2022-05-14).

Macil avatar Mar 13 '23 10:03 Macil

It's possible that it was introduced between 0.93.1 and 0.94.x when re-release support patches went in.

sezero avatar Mar 13 '23 10:03 sezero

Note that this is specifically in the re-release's version of the start map, which has transparent water unlike the original, so it might be that this never worked.

Macil avatar Mar 13 '23 11:03 Macil

Vispatch'ed id1 looks OK to me? (i686 linux, qs from today's git, both with r_wateralpha 0.4)

ID1 1.06 + vispatch: spasm0000

ID1 - rerelease: spasm0001

sezero avatar Mar 13 '23 11:03 sezero

I've also spotted this issue in QS (and vkQuake) in some other levels like Dwell v2.2 (s2.sav.zip):

vkquake0000

I did notice that Ironwail does not have this issue. I search its issue tracker and found this post https://github.com/andrei-drexler/ironwail/issues/139#issuecomment-1271947987 explaining their solution.

Macil avatar Dec 24 '23 02:12 Macil