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

[regression, d3d9] Supreme Ruler Ultimate alt tab render freeze #3784

Closed
Blisto91 opened this issue Jan 4, 2024 · 1 comment · Fixed by #3816
Closed

[regression, d3d9] Supreme Ruler Ultimate alt tab render freeze #3784

Blisto91 opened this issue Jan 4, 2024 · 1 comment · Fixed by #3816
Assignees

Comments

@Blisto91
Copy link
Contributor

Blisto91 commented Jan 4, 2024

Since commit 52ac271 when you alt tab in Supreme Ruler Ultimate the renderer will freeze and not snap out of it when you focus on the game again.
Note that the commit itself will show the game as only a black screen, which is fixed a couple of commits later, but i can see with the dxvk hud not updating that it should be the one.

d3d9.deviceLossOnFocusLoss does not make a difference.

Software information

Supreme Ruler Ultimate

System information

  • GPU: RX 6800
  • Driver: few days old mesa main
  • Wine version: Proton Experimental
  • DXVK version: 52ac271 and up

Apitrace file(s)

Two traces where i go to the main menu then hover back and forth on the buttons -> alt tab -> hover back and forth again before quitting. One made with dxvk master and one made with wined3d.
https://drive.proton.me/urls/M6DB662QVR#XZTSivf5Fw2P

Observe that when replaying with dxvk before the commit, e.g. 2.2, that the wined3d one will show me hovering over the buttons fine the second time after alt tabbing where as the dxvk one will end early before second attempt. When replaying with dxvk including the commit, e.g 2.3, both traces will end early and not show the hovering after alt tab.

Log files

SupremeRulerUltimate_d3d9.log
steam-314980.log

@K0bin K0bin self-assigned this Jan 22, 2024
@K0bin
Copy link
Collaborator

K0bin commented Jan 24, 2024

I strongly suspect this is a game bug. The game leaks a state block in both the WineD3D apitrace as well as the DXVK one.

I've also written a quick test to verify that this will indeed make D3D9Device::Reset fail.

Replaying the WineD3D apitrace with the Windows Nvidia D3D9 driver makes Apitrace complain about the reset call failing.

Lastly, there's this: https://steamcommunity.com/app/314980/discussions/0/1652171126118360822/

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

Successfully merging a pull request may close this issue.

2 participants