protonscr

[d3d9] Book of Demons: White Textures

dxvkclosed d3d9
doitsujin/dxvk#1420 · opened 2020-02-08 by ryester19 · updated 2020-02-14 · 10 comments · github
1 matching comments, n / p to jump
Rryester19 2020-02-08 github

When you are in town or in the screen before entering town, almost all of the textures other than the character model and HUD is white

DXVK
Screenshot_20200207_215235
Screenshot_20200207_215249

WineD3D
Screenshot_20200207_215406
Screenshot_20200207_215418

Software information

Book of Demons on Arch Linux

System information

  • GPU: AMD RX 560
  • Driver: Mesa 19.3.3
  • Wine version: Proton 5.0-1
  • DXVK version: 1.5.4

Apitrace file(s)

https://mega.nz/#!bw5USK7Z!dicxTVg15baoWeZMpo_tOlwcZY-ekw2-Bft5VMoOAnM

Log files

steam-449960.log

Llucifertdark 2020-02-08 github

I can confirm the bug is present with Nvidia hardware GTX1650 & 440.48.02 drivers as well, here are logs from Proton 4.11-12 (no bug) & Proton 5.0-1 (with bug)
https://gist.github.com/lucifertdark/584c14275612e8e3c4a8070d428d8a02
Proton 4.11-12.steam-449960.log
Proton 5.0-1.steam-449960.log

Zziabice 2020-02-08 github

Game works well with:
Proton 4.11-12
Mesa 19.3.3 on AMD RX 580

Zziabice 2020-02-08 github

Tested Proton 5.0-1 and it doesn't work, as described.

steam-449960.log

Screenshot_20200208_141619

Mmisyltoad 2020-02-08 github

This trace is garbage because you traced OpenGL + WineD3D which is not useful to me.

Please trace Direct3D 9 + WineD3D. There is a guide on the Wiki.

Rryester19 2020-02-08 github

I can confirm the bug is present with Nvidia hardware GTX1650 & 440.48.02 drivers as well, here are logs from Proton 4.11-12 (no bug) & Proton 5.0-1 (with bug)

D9VK was not the Proton default until 5.0-1. You had to use the PROTON_USE_D9VK variable before. I was getting the same bug with 4.11-12 using D9VK.

https://github.com/Joshua-Ashton/d9vk/wiki/Making-a-Trace

Sorry, I forgot how I did this before with Proton because I didn't want to install the wine package for winecfg. I guess my last attempt was not the correct way. Anyways I remember now and the new apitrace is below

New apitrace
https://mega.nz/#!K1BEmAQT!0iYXnG2z80jUFD_vQEQ7DAESezUM5awLA1G8okSKatM

Mmisyltoad 2020-02-08 github

Thanks for the trace. Fixed! Enjoy :)

Rryester19 2020-02-09 github

Looking good now. Still some visual errors with the UI, but I'll create another ticket for those

Screenshot_20200209_005324

Ggoulvenclech 2020-02-14 github

Hi guys, I just have the exact same problem :/
The game work out of the box with Proton 4.11-15, but not with Proton 5.0-1.

Rryester19 2020-02-14 github

Hi guys, I just have the exact same problem :/
The game work out of the box with Proton 4.11-15, but not with Proton 5.0-1.

Commits have already been submitted to deal with this problem and others I reported. Either wait for the next DXVK point release & sequential Proton update, compile your own d3d9.dll from master & put it in the game directory, or use the PROTON_USE_WINED3D=1 command line option in Steam to go back to how Proton use to handle D3D9 before 5.0-1

Proton versions

Launch options

DLLs