An apitrace crashes when using WINED3D: https://drive.google.com/file/d/1D5mGl0IOlNtWjKR9y-L6ENmMI0Og1hVT/view?usp=sharing
Is there another way to get a trace? Using DXVK causes the game to slow down and I figured that was useless since the wiki says use WINED3D only.
Is there another way to get a trace?
Yes, by doing it on Windows, which is probably necessary here. Recording traces with DXVK isn't useful when the game crashes due to a DXVK bug (although it's also not really obvious whether it is our bug at this point).
Is there another way to get a trace? Using DXVK causes the game to slow down and I figured that was useless since the wiki says use WINED3D only.
On Windows, the game slows down/has very poor framerate while using DXVK if Punkbuster is not properly installed. Took me a while to figure that one out.
apitrace v11.1 is here: https://drive.google.com/file/d/1yVfhW7ZWc72dAcf4HrGabdNVHyv3y4KH/view?usp=sharing
Trace plays fine.
But i can reproduce in the actual game both with dxvk and wined3d.
Doitsujin mentioned in discord it was likely hitting the memory limit since the game is 32bit. It is unfixable right?
Wouldn't say it's unfixable. Might be memory issues, but could be other stuff.
Black background in DX9 mode in campaign mode, only shows the HUD but the rest of elements of the game is a black background, tested with a GTX 1070, I can't play this game :(
And yes, DX11 mode crash in campaign mode too with NVIDIA graphics card.
Logs please.
Apitrace please.
I can't trace this game, when I extract the dlls in the same game exe's directory, the game not startup.
Tested with proton 7.0-4 and experimental
I used this guide: https://github.com/doitsujin/dxvk/wiki/Making-a-Trace
But the game not start...
Then some logs will have to do. Tho they probably wont tell much. They should appear in either the games root directory or next to the exe when you start the game with PROTON_LOG=1 %command%
Can try the game myself here later on the Nvidia setup when i have time
So i don't think the original issue is dxvk since i can start the campaign fine in dx11 mode on windows with 1.10.3.
But it also isn't d3dcompiler, d3dx11 or similar since i tried installing that with winetricks into the proton prefix and it's the same. Maybe some wine thing.
Hi @Blisto91,
Dx9 mode for this game is no longer working correctly. The UI renders but the game itself is black. I can see the cross hairs and team mate names but no 3d graphics. Just black. Anything you can suggest I try before I prepare an API trace?
@Alexithymia2014 Hello and thank you for the report. This seems to be an issue with the d3dcompiler_47 dll as it works when i install the windows version with winetricks. Did this used to work without having to do that?
It used to work fine without installing d3dcompiler_47, but I only remember it working probably around the time I filed this report. I'll give it a shot with that dll install. Thanks!
Hmm ok. The d3dcompiler_47 dll in Proton doesn't seem to have been updated since april 2022
Ah I see. Well either way it's working in DX9 mode again with that dll installed using proton tricks. Thanks for your assistance!
The d3dcompiler_47 dll in Proton doesn't seem to have been updated since april 2022
vkd3d, which implements the d3dcompiler stuff, was updated 2 month ago, in experimental at least.
Ah didn't realize it was dependent on the separate module.
It's also a issue with proton 7.0-6 so logically it points to a regression in 7.0-4 when the vkd3d module was updated in stable. Will compile 7.0-3 here later and check out. Thanks
DX9 seems to be working here on Steam Deck with either Valve's Proton (7.0-3 (own build), 7.0-6, 8.0-4, Proton Experimental as of 2023-11-09) or GE-Proton8-23 (own build). No manual overrides were needed, however the game's Steam installer does install numerous DirectX libraries into the prefix.
DX11 however does crash, on all Proton builds mentioned above, with or without d3dcompiler_47 override. After the prologue mission, the cutscene sequence does load with DX11, as well as the firing range. The actual mission after the cutscene sequence crashes as well.
Is this fixable, is there anything that I can help with?
There is not much pointing to this being a dxvk issue. It works fine with dxvk on Windows and it crashes the same with wined3d on Linux (reading what i wrote above at least, haven't tested right now)
This issue seems to be resolved in Proton 9.0.
Yep, I can confirm being able to do a complete playthrough on DX11 with GE-Proton9-5 (did not test upstream Proton, though).
ge-proton9-5x1 2024-05proton 9.0x1 2024-05proton experimentalx2 2023-11ge-proton8-23x1 2023-11proton 7.0-6x1 2023-04proton 7.0-4x1 2022-09proton 7.0-3x1 2022-07PROTON_LOG=1x1 2022-09
Ghost Recon Future Soldier crashes with a Yeti dump error when using DX11 for the Campaign. It seems to work fine in the main menu and even multiplayer but not in the campaign (which is probably the only thing that works nowadays).
I've tested this with Proton Experimental bleeding edge but occurs in other Proton versions. Additionally, you need to run protontricks uplay for Uplay to install. For whatever reason, Steam doesn't install Uplay for this game anymore. This game works fine in DX9 mode though!
Software information
Ghost Recon Future Soldier DX11 (default mode)
Proton Experimental and Proton 7.0-3
This also occurs on my Steam Deck.
System information
Log files
https://drive.google.com/file/d/1b3p4LRmyDiM8hu3xnNaiU8sRk9FJOBbL/view?usp=sharing
These contain the dxvk and proton logs.