Can't debug without an apitrace.
Sure thing but as a trace neophyte, i couldn't get to produce an apitrace..
I'm using Proton from the Steam client. Launching with DXVK disabled as mentionned on some posts.
I copy the DLLs in the game's folder as you indicated https://github.com/doitsujin/dxvk/wiki/Common-issues#apitrace but nothing gets generated. It didn't generate anything in the pfx/Desktop (which should be the place to produce the trace according to the doc).
So i tried a 2nd method. Renaming apitrace.exe to the game.exe and the game.exe to another. Steam launcher option: PROTON_USE_WINED3D=1 %command% trace -a dxgi BFBC2Game_o.exe (i also tried just with trace game.exe)
It required to have the lib/wrapper folder up the parent folder, which lead to this message (in verbose):
info: did not find Z:\$HOME\.steam\steam\steamapps\common\Battlefield Bad Company 2\..\wrappers\RelWithDebInfo\dxgitrace.dll
info: found Z:\$HOME\.steam\steam\steamapps\common\Battlefield Bad Company 2\..\lib\wrappers\dxgitrace.dll
inject -D "Z:\$HOME\.steam\steam\steamapps\common\Battlefield Bad Company 2\..\lib\wrappers\dxgitrace.dll" -- BFBC2Game_o.exe
error: failed to execute inject
0009:fixme:kernelbase:AppPolicyGetProcessTerminationMethod FFFFFFFA, 0034FEB4
Any hint on what i did wrong to produce the trace ?
Have you copied all the d3d11.dll, dxgi.dll and dxgitrace.dll files of the correct architecture next to the game exe? It's complaining about dxgitrace.dll not being available.
NB: the game is 32 bit d3d11.
EDIT: 205 41147.533:0032:0033:trace:loaddll:load_so_dll Loaded L"C:\\windows\\system32\\dxgi.dll" at 0xf4530000: builtin Seems like it loaded the one from system32 instead of the local first.
So for the 1st method mentionned yes, i did:
PROTON_USE_WINED3D=1 %command%find ~ -name *.trace. I suppose the trace should be output in ~/.steam/steam/steamapps/compatdata/24960/pfx/drive_c/users/steamuser/DesktopCan you try without PROTON_USE_WINED3D=1? Might be fine in this case, but that option also sets WINEDLLOVERRIDES to use built-in DXGI and D3D11 which is the problem you're running into.
Indeed. So i had to manually add dxgi and d3d11 DLLs through winecfg in the pfx, then it loaded the DLLs. But it crashed.
Now launching without DXVK (PROTON_USE_WINED3D=1): it starts. But black screen for 3mn and nothing impressive in proton log. Unresponsive window so i closed. Should have i kept it running for longer ?
Game crashed with DXVK + apitrace but it's supposed not to work according to some post
DO NOT use DXVK together with apitrace!
Been banging my head against the screen trying to install any driver below 470 on this setup. But i kinda gave up on that so this isn't a proper test to reproduce the original issue.
With a nvidia 960 with 470.103 driver i have not been able to reproduce this issue.
I tried with the dxvk version that came along with proton 4.11 and manually replacing with 1.3.3, 1.3.4 and 1.10.
I have tried going between servers and seeing if i could reproduce the issue on the specific maps and with all settings levels, but have not been able to.
Unless someone complains then i think this one can be closed. Have not been able to reproduce with the 470 driver and looking through protondb i haven't seen this graphical complaint.
proton 4.11x1 2022-03PROTON_USE_WINED3D=1`):x1 2019-08PROTON_USE_WINED3D=1`?x1 2019-08WINEDLLOVERRIDESx1 2019-08PROTON_USE_WINED3D=1x2 2019-08PROTON_USE_WINED3D=1 %command%x2 2019-08d3d11.dllx2 2019-08dxgi.dllx2 2019-08dxgitrace.dllx2 2019-08
Hi there !
I reported this issue on proton with log/screenshots:
https://github.com/ValveSoftware/Proton/issues/200#issuecomment-518643828
It's really specific. The game runs flawlessly at 140~200fps most of the time, kudos for the Vulkan layer mate.
But i get a weird blue sky on some maps (Atacama Desert and Laguna Presa) in "conquest mode" on EA servers only (where i could reproduce the issue).
It has not happened outside EA servers on those maps/modes with Punkbuster enabled.
I tried enabling/disabling feral's gamemode, fsync (running Valve kernel 5), and changing graphics settings from high to low, no changes for this issue.
Not tightly related but iirc, ENB on GTA V back in the day had a similar bug where the sky went blue.