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

Misrendering in SteamVR Performance Test #1160

Closed
ryao opened this issue Aug 10, 2019 · 11 comments
Closed

Misrendering in SteamVR Performance Test #1160

ryao opened this issue Aug 10, 2019 · 11 comments
Labels

Comments

@ryao
Copy link
Contributor

ryao commented Aug 10, 2019

Software information

SteamVR Performance Test
Picked the do not report to valve launch option through the right click context menu under the Tools section of my Steam library.

System information

  • GPU: GeForce GTX 1070
  • Driver: 430.34
  • Wine version: Proton 4.11-2
  • DXVK version: Proton 4.11-2 bundled version

Apitrace file(s)

  • I cannot generate an API Trace. It crashes when trying to use WineD3D and I do not have Windows.

Log files

  • d3d11.log: Not generated by proton
  • dxgi.log: Not generated by proton
@ryao
Copy link
Contributor Author

ryao commented Aug 10, 2019

Some of the misrendering issues go away with d3d11.dcSingleUseMode = False. I found the d3d11.log and dxgi.log files. Their names were not what I expected:

vr_d3d11.log
vr_dxgi.log

@kwahoo2
Copy link

kwahoo2 commented Aug 27, 2019

After updating Proton to 4.11-3, the app is able to start and display something. But there are rendering artifacts (see screenshot)

System information

  • GPU: Radeon RX 580
  • Driver: 430.34 Mesa 19.3.0-devel (LLVM 8.0.0) + Valve ACO (tested with and w/o)
  • Wine version: Proton 4.11-3
  • DXVK version: Proton 4.11-3 bundled version

SteamVR Performance Test

vr_d3d11.log

vr_dxgi.log

@misyltoad
Copy link
Collaborator

Read above.

@kwahoo2
Copy link

kwahoo2 commented Aug 27, 2019

Read above.

This is with Proton 4.11-3, where dcSingleUseMode should be disabled, but according logs it isn't:

warn: D3D11: Command list submitted multiple times,
warn: but d3d11.dcSingleUseMode is enabled

@misyltoad
Copy link
Collaborator

Why would it? There's no release of DXVK with this fix that's in Proton afaik.

@kwahoo2
Copy link

kwahoo2 commented Aug 27, 2019

Ok, @ryao comment from ValveSoftware/SteamVR-for-Linux#218 mislead me a bit.

Is there a way to disable d3d11.dcSingleUseMode without recompiling DXVK?

@misyltoad
Copy link
Collaborator

dxvk.conf

@doitsujin
Copy link
Owner

There has been no DXVK update since 4.11-2, so yes, it is expected to be broken. Changing the option won't fix all of it since there were actually two different issues with it.

@kwahoo2
Copy link

kwahoo2 commented Aug 27, 2019

Changing the option won't fix all of it since there were actually two different issues with it.

Yes, I've just tried it, the difference is very minor https://i.imgur.com/VVipivV.png

@ryao
Copy link
Contributor Author

ryao commented Aug 28, 2019

Ok, @ryao comment from ValveSoftware/SteamVR-for-Linux#218 mislead me a bit.

Is there a way to disable d3d11.dcSingleUseMode without recompiling DXVK?

Sorry about the confusion. I had talked to people about getting ValveSoftware/Proton#2616 fixed in 4.11-3. I had expected that these patches would be pulled into it, so I did not explicitly ask about it. I had wanted to get both this and ValveSoftware/Proton#2616 fixed in 4.11-3. My view had been that ValveSoftware/Proton#2616 was less likely to be fixed in 4.11-3, so I had explicitly talked to people about it. It was not a bad assumption that this would be fixed too, but it ended up being incorrect. I regret not talking to people about this one too. I never thought that it would be omitted.

@kwahoo2
Copy link

kwahoo2 commented Aug 29, 2019

DXVK 1.3.3 fixed incorrect rendering for me. Performance looks ok too: 6.4 score, 0 frames below 60fps, 0 frames CPU-bound.

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

No branches or pull requests

4 participants