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

Terrain Flickering in Entropia Universe #1364

Closed
PkmX opened this issue Jan 22, 2020 · 4 comments
Closed

Terrain Flickering in Entropia Universe #1364

PkmX opened this issue Jan 22, 2020 · 4 comments

Comments

@PkmX
Copy link

PkmX commented Jan 22, 2020

Software information

Entropia Universe VU 17 (D3D11 CryEngine based), any graphic settings

System information

  • GPU: AMD Radeon RX 590
  • Driver: Linux 5.4.10 / RADV 19.3.2
  • Wine version: 5.0-rc5-staging
  • DXVK version: 1.5.1

Apitrace file(s)

Log files

Imgur

Game shows massive amount of artifacts on distant (and sometimes nearby) terrain and flickers as the camera moves, which isn't present with Wine's own D3D11 implementation. No other rendering issues except this one. Unfortunately it is very laggy (<0.3 fps) and takes nearly half an hour to load during API tracing so I only traced the minimal frames to show the bug with the login portion trimmed.

@doitsujin
Copy link
Owner

doitsujin commented Jan 22, 2020

This is z-fighting that occurs because the game relies on two different vertex shaders to produce the same numerical values. I'm not sure if this can be fixed.

FWIW it doesn't happen with amdvlk, but that's probably just luck and can break any time.

Edit: I tried declaring the vertex positions as invariant, which fixes the problem on AMD but is known to break some other games on Nvidia for unknown reasons.

Edit 2: Fixed on RADV, not sure if this happens on Nvidia.

@aufkrawall
Copy link

I wonder if this might be also beneficial for this radv Just Cause 3 issue:
https://gitlab.freedesktop.org/mesa/mesa/issues/851

@doitsujin
Copy link
Owner

Doubt it since that issue is over a year old, whereas the NIR optimizations that break our stuff are very recent.

doitsujin added a commit that referenced this issue Jan 23, 2020
@PkmX
Copy link
Author

PkmX commented Jan 23, 2020

I can confirm in-game that it is indeed resolved. Thanks for the quick fix!

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

3 participants