-
Notifications
You must be signed in to change notification settings - Fork 49
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
Crash while attempting to use apitrace
#821
Comments
The crash dump provided is crashing in the same spot as we discussed before, you need to use the latest artifact for the project I linked earlier. |
Huh, you're right:
When loading the following minidump (predictably due to a crash):
Strange that |
It's the same crash as before, you'll have to mention in the issue that you can't get a dump as the game crashes without dxvk |
Another strange quirk: replacing the |
That's because it's a different account list for non-release dls |
Can I login using my same credentials using either the release or debug dll? |
After resetting my password, I got the following error: Insufficient PC Identification Your PC does not have sufficient unique identifiers available. Please contact an admin about linking this PC with another that you own that does have sufficient info. This is to ensure fair online play. |
No you cannot login with your account on developer/custom built dlls |
You'll have to use offline mode if you want to access the game on them |
So no online matches with a non-release dll. Out of curiosity, how would you or other developers debug issues related to online multiplayer then? |
We use developer accounts or the LAN functionality |
After following instructions from https://github.com/doitsujin/dxvk/wiki/Using-Apitrace#on-windows in order to file a bug report on dxvk, I tried loading the game; it predictably crashed (somewhere within the
xlive.dll
from the artifact. The apitrace zip file provided its version ofd3d9.dll
, so I moved dxvk'sd3d9.dll
elsewhere.Loading the dump on windbg yielded the following:
20250313-224843_crash_file_archive.zip
The text was updated successfully, but these errors were encountered: