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

GTA IV - Rendering issues on AMD and Intel #99

Closed
NorbertHarangozo opened this issue May 12, 2019 · 7 comments
Closed

GTA IV - Rendering issues on AMD and Intel #99

NorbertHarangozo opened this issue May 12, 2019 · 7 comments

Comments

@NorbertHarangozo
Copy link

NorbertHarangozo commented May 12, 2019

Software information

GTA IV at max settings

System information

  • GPU: RX 580 4GB and UHD 620
  • Driver: AMDVLK 2019.Q2.2, RADV Git and ANV 19.0.3
  • Wine version: Proton 4.2-3
  • D9VK version: da39227

GTA IV has artifacting issues on AMD and Intel as well. On RADV and ANV the car textures aren't rendered correctly, AMDVLK doesn't have this problem. On Intel, there are even more issues.

AMDVLK:
amdvlk
amdvlk2
https://www.youtube.com/watch?v=2EukzCABdhA

RADV:
radv
radv2
https://www.youtube.com/watch?v=P1d1mlIO8Z8

Intel:
intel
intel2
https://www.youtube.com/watch?v=EIQZd-_AFks

Apitrace file(s)

Log files

@misyltoad
Copy link
Owner

Game seems to render fine on NVidia.

I ran a spirv-val on the shaders and everything seems to be OK -- I checked the shaders and didn't see anything too crazy it was doing.

Need to compile a new version of regular vk val layers to check those (current SDK is completely broken.)

@misyltoad
Copy link
Owner

This should be fixed (well, worked around) by the d3d9-hazards branch.

@QmwJlHuSg9pa
Copy link

The d3d9-hazards workaround fixed the issue for me, though at the expense of a framerate drop.

I tested the same scene several times, casually observing a drop from 85-110 fps (0.12 release; similar performance to native D3D9) down to 70-85 (d3d9-hazards)

Machine:

  • Windows 10 1809
  • Radeon RX 580
  • Ryzen 2600X

@K0bin
Copy link
Contributor

K0bin commented Jun 12, 2019

Unfortunately that has to be expected which is why it's a separate branch for now.

We're still looking for a better way to fix it but it's a very tricky problem.

@neVERberleRfellerER
Copy link

neVERberleRfellerER commented Jun 12, 2019

I found that when I retrace #164 I see the very same corruption as with trace from here, but OP in second issue seemingly does not see any colorful corruption (it's not visible in screenshots). The difference is that OP in second thread is on Vega 11, and I am on POLARIS10. hasHazards=true helps in both cases. Is this expected?

@misyltoad
Copy link
Owner

misyltoad commented Jun 15, 2019

This should be fixed in master? Can you try it?
Performance should also be OK.

@QmwJlHuSg9pa
Copy link

Tested with 0fd76277. Looks just like native D3D9 as far as I can tell. Performance is comparable, too. There's moments where it'll drop from ~110 down to ~65 but I think that's just an underlying limitation of the game engine.

Cheers!

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

5 participants