Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
d3d9_debugging [2014/11/09 23:36] sarnex |
d3d9_debugging [2022/07/11 10:41] (current) |
||
|---|---|---|---|
| Line 15: | Line 15: | ||
| A problem can be located in either wine or Mesa. | A problem can be located in either wine or Mesa. | ||
| - | If it's in mesa, you'll need to use | + | If it's in mesa, you'll need to use [[https:// |
| - | * the **NINE_DEBUG** variable, to know what the D3D9 ST is doing. Pass **NINE_DEBUG=help** to get all options. | + | |
| - | * the **NINE_TGSI_DUMP=1** variable for dumping generated TGSI code. | + | |
| - | * the **NINE_FF_DUMP=1** variable for dumping shader generated by fixed function (ff) | + | |
| - | * the **TGSI_PRINT_SANITY=1** variable will precisely check TGSI and assert in case of errors | + | |
| - | * the **D3D_ALWAYS_SOFTWARE=1** will run it on CPU instead of GPU... //extremly slow// | + | |
| when you comparing logs from ALWAYS_SOFTWARE, | when you comparing logs from ALWAYS_SOFTWARE, | ||
| Line 33: | Line 28: | ||
| == APITrace == | == APITrace == | ||
| {{ : | {{ : | ||
| + | * **For apitrace to work, you need to use the no_external_dll branch of iXit/ | ||
| * For debugging Windows applications you'll need to use APITrace compiled for Windows | * For debugging Windows applications you'll need to use APITrace compiled for Windows | ||
| * The Windows version is almost always required for replaying | * The Windows version is almost always required for replaying | ||
| - | When uploading APITrace .trace file, please | + | When uploading APITrace .trace file, please |
| - | ** * We have dedicated server space for APITrace files, contact sarnex or okias on IRC for the information.** | + | |
| * [[https:// | * [[https:// | ||
| - | * [[http:// | + | * [[http:// |