-
Notifications
You must be signed in to change notification settings - Fork 23
apitrace
David Heidelberg edited this page Jul 11, 2022
·
5 revisions
If you encounter a problem with a game you might get asked to upload a trace file captured with apitrace.
To do that with this Standalone version:
- Download and extract a Windows binary release to a directory which is exposed via WINE (like
$HOME/.wine/drive_c
) - Set the envvar
WINEDLLOVERRIDES
tod3d9.dll=n,b
- Set the envvar
TRACE_FILE
to the trace filename - Copy apitrace's
d3d9.dll
(x86/lib/wrappers/d3d9.dll
for 32bit games andx64/lib/wrappers/d3d9.dll
for 64bit ones) to the directory where the main game executable resides - Run the game, showcase the problematic spot, exit it again (keep it short, traces can get huge)
- Remove apitrace's
d3d9.dll
again - Compress the trace file (preferably with
apitrace repack -b original.trace compressed.trace
) and upload to your favorite file hosting service
Example:
export WINEDLLOVERRIDES=d3d9.dll=n,b
export WINEDEBUG=fixme-all,+debugstr
export TRACE_FILE=d3d9.trace
cd ~/.wine/drive_c/Fallout
cp ../apitrace-msvc/x86/lib/wrappers/d3d9.dll .
wine falloutwHR.exe
rm d3d9.dll
wine ../apitrace-msvc/x86/bin/apitrace.exe repack -b d3d9.trace d3d9_repack.trace
Upon starting the game you'll get:
apitrace: loaded into C:\Fallout\falloutwHR.exe
apitrace: tracing to d3d9.trace
And afterwards you can replay that trace:
wine ../apitrace-msvc/x86/bin/apitrace.exe replay d3d9.trace