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

Bad water transparency layering in start level #53

Open
Macil opened this issue Mar 13, 2023 · 7 comments
Open

Bad water transparency layering in start level #53

Macil opened this issue Mar 13, 2023 · 7 comments

Comments

@Macil
Copy link
Contributor

Macil commented Mar 13, 2023

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: Novum/vkQuake#656. I thought this was vkQuake specific at first but guess not. This issue does show up slightly differently between the two ports though.

@sezero
Copy link
Owner

sezero commented Mar 13, 2023

@ericwa, @andrei-drexler, @Novum ?

@sezero
Copy link
Owner

sezero commented Mar 13, 2023

P.S.: Have you bisected this?

@Macil
Copy link
Contributor Author

Macil commented Mar 13, 2023

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

@sezero
Copy link
Owner

sezero commented Mar 13, 2023

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

@Macil
Copy link
Contributor Author

Macil commented Mar 13, 2023

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.

@sezero
Copy link
Owner

sezero commented Mar 13, 2023

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

@Macil
Copy link
Contributor Author

Macil commented Dec 24, 2023

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 andrei-drexler#139 (comment) explaining their solution.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants