You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is not an issue on Linux I've found so far so this is more in regards to it maybe being a potential inconvenience for testing on Windows.
Another issue that seems to hit the same is #3865
When i wanted to test Everquest with dxvk on Windows i hit a problem with the game complaining none of my GPUs support feature level 11_0 after i hit the button to select a server. dxvk is running fine up until that point.
On this system i currently have both an Nvidia dGPU and a AMD iGPU with their respective drivers installed.
In the dxvk logs errors such as these can be seen
err: D3D11SwapChain: Failed to recreate swap chain: VK_ERROR_NATIVE_WINDOW_IN_USE_KHR
err: DXGI: CreateSwapChainForHwnd: Failed to create swap chain, hr -2147467259
Leaving the system as is then i can actually get ingame with dxvk up until commit 83a2942 (thank you @WinterSnowfall)
If i disable either of the GPUs in Device Manager so only one should be enabled then i will hit the issue even before that commit (1.10.3 and 2.1 tested).
A potential interesting thing to note is that with both GPUs enabled and using dxvk 2.1 on the server selection screen the game will use the Nvidia GPU but when i have selected the server it then switches to the AMD GPU. This is all with the same exe.
Using DXVK_FILTER_DEVICE_NAME to select my dGPU does not change anything in regards to the error.
Software information
Everquest
System information
GPU: RTX 4080 and 7950x iGPU
Driver: 551.61 and 24.40.19.01
Monitor: Single monitor plugged in to dGPU via Displayport
Wine version: Windows 11
Apitrace file(s)
3 apitraces made.
One with native d3d11 that makes it all the way through. One with dxvk 2.1 that makes it past server selection to character selection but then errors when going back to server selection again. One with dxvk master that errors already when trying to get to character selection from server selection. https://drive.proton.me/urls/NF6SY0DAA4#MPdTiASv82V4
A thing i noticed while replaying a apitrace is that it will have two windows open beyond the server selection screen
This is not an issue on Linux I've found so far so this is more in regards to it maybe being a potential inconvenience for testing on Windows.
Another issue that seems to hit the same is #3865
When i wanted to test Everquest with dxvk on Windows i hit a problem with the game complaining none of my GPUs support feature level 11_0 after i hit the button to select a server. dxvk is running fine up until that point.
On this system i currently have both an Nvidia dGPU and a AMD iGPU with their respective drivers installed.
In the dxvk logs errors such as these can be seen
Leaving the system as is then i can actually get ingame with dxvk up until commit 83a2942 (thank you @WinterSnowfall)
If i disable either of the GPUs in Device Manager so only one should be enabled then i will hit the issue even before that commit (1.10.3 and 2.1 tested).
A potential interesting thing to note is that with both GPUs enabled and using dxvk 2.1 on the server selection screen the game will use the Nvidia GPU but when i have selected the server it then switches to the AMD GPU. This is all with the same exe.
Using
DXVK_FILTER_DEVICE_NAME
to select my dGPU does not change anything in regards to the error.Software information
Everquest
System information
Apitrace file(s)
3 apitraces made.
One with native d3d11 that makes it all the way through. One with dxvk 2.1 that makes it past server selection to character selection but then errors when going back to server selection again. One with dxvk master that errors already when trying to get to character selection from server selection.
https://drive.proton.me/urls/NF6SY0DAA4#MPdTiASv82V4
A thing i noticed while replaying a apitrace is that it will have two windows open beyond the server selection screen
Log files
eqgame_dxgi.log
eqgame_d3d11.log
The text was updated successfully, but these errors were encountered: