-
Notifications
You must be signed in to change notification settings - Fork 887
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
D3D9: Call of Duty: Modern Warfare 2 (2009) / Excessive Shader Compilation #4594
Comments
Could you please make an apitrace? Just download the apitrace binaries, grab the 32bit d3d9.dll wrapper file and drop that right next to the exe file of the game. |
Hi K0bin, the iw4x.trace file is already over 400MB and the game still hasn't loaded to the main menu! |
It's normal for those files to get quite large depending on the game. However, 400MB before the main menu in a D3D9 game is a bit odd. |
Mh definitely weird then, I've already reached a 1.2GB file, and still not booted into the main menu. edit: finally done! The file is now 1.7GB. Trace: https://mega.nz/file/TGpFSCxK#3L6jXgAdlVUaXhk3UMv9tWGXctgHlNiEKQcKMAFqz5w |
The game takes around 20 seconds to boot into the main menu (whether it's the initial boot, or going back to the main menu after leaving a session). It also takes between 20s and a whole minute to join a server.
I can see in my terminal hundreds of
Compiling shader FS_XXXXXXX
whenever this freeze happens.Software information
I'm playing Call of Duty: Mw2 using the iw4x client (https://github.com/iw4x/iw4x-client). My issue happens on both wine & proton. It does NOT happen if I use wined3d instead of dxvk.
System information
Apitrace file(s)
Log files
Proton logs:
steam-default.log
The text was updated successfully, but these errors were encountered: