https://bugs.winehq.org/show_bug.cgi?id=46360
Bug ID: 46360 Summary: wine+dxvk black game window switch back to vtx from vt7 Product: Wine Version: 3.21 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: gamiljydcome@gmail.com Distribution: ---
OS: debian9 stable kernel 4.18 GPU: intel+nvdia Driver: mesa 18.2 + intel modesetting + nvidia driver Wine version: x86_64 bit wine-staging 3.21 precompiled binary DXVK version: 0.94
i start another xserver from another tty such as vt2 but not default vt7 so can use nvidia as primary video card, launch dx11 game with wine+dxvk then switch back to vt7 and switch back again, the game window totally black never restore.
from vtx run glxgeas or wine dx11 game with buildin dlls, or wine dx9 game with native or buildin d3dx9_xx.dll, switch between vtx-vt7 the glxgeas or game window restore quickly without any errors.
if from vt7 run DISPLAY=:1 glxgeas or wine dx11 game.exe with buildin dlls, its fine, switch vts fine. if run DISPLAY=:1 with wine+dxvk failed to launch game exe with dxvk error: D3D11CoreCreateDevice: Failed to create D3D11 device.
its not dxvk bug like the author said. so maybe its about wine (vulkan part)?
https://bugs.winehq.org/show_bug.cgi?id=46360
Fabian Maurer dark.shadow4@web.de changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |dark.shadow4@web.de
--- Comment #1 from Fabian Maurer dark.shadow4@web.de --- When it works with win builtin dlls, but not dxvk, this sounds like a dxvk issue. What makes you say it's not, mind linking the response from the dxvk author?
https://bugs.winehq.org/show_bug.cgi?id=46360
Paul Gofman gofmanp@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |gofmanp@gmail.com
--- Comment #2 from Paul Gofman gofmanp@gmail.com --- It looks like native Vulkan configuration issue, something not related to Wine or dxvk. Can you install vulkan tools and run vulkaninfo (with the same environment variables as you run wine) in both cases when it starts ok with dxvk and when it does not? I would expect you will miss Nvidia device in the failure case.
https://bugs.winehq.org/show_bug.cgi?id=46360
--- Comment #3 from gamiljydcome@gmail.com --- i dont think its about dxvk dlls because its window native dlls just like dx9 native dlls.
i installed nvidia-vulkan-icd libvulkan1 vulkan-utils without any custom settings(do they have?).
i posted vulkaninfo output to https://github.com/doitsujin/dxvk/issues/826 if you please to review.
maybe it's about wine vulkan calls part?
about nvidia driver my x config only enabled Option AllowEmptyInitialConfiguration" "Yes" and Option "UseDisplayDevice" "none".
https://bugs.winehq.org/show_bug.cgi?id=46360
--- Comment #4 from gamiljydcome@gmail.com --- running vulkan-smoketest present the same problem, so its not wine bug, please close this report.
https://bugs.winehq.org/show_bug.cgi?id=46360
Fabian Maurer dark.shadow4@web.de changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID
--- Comment #5 from Fabian Maurer dark.shadow4@web.de --- Marking invalid as of comment #4.
https://bugs.winehq.org/show_bug.cgi?id=46360
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #6 from Austin English austinenglish@gmail.com --- Closing.
-
wine-bugs＠winehq.org