Hard to debug a DirectX game when it runs flawlessly on my machine, but not on another.
I even have a logging system that writes to disk all the stages of the init and render code. But it seems that the writing to the disk is so slow that the code terminates before it writes the full error - I'm getting half written error messages.
Anyone have any ideas on how I can debug this??
Doesnt VC++ offer a remote debugging facility?......I have never tried to use it though....and I dont know its capabilites
Found this on an MSDN search....see if it helps
In general, you have to check HRESULT's returned by DirectX functions whenever failure is possible.
Use functions like DX8GetErrorString() & DX8GetErrorDescription() ( I think these are the correct function names ) whenever an HRESULT reports failure.
Display a message box containing the error string & the error description, and bail out.
By the way, when does it crash on the other PC? ( After/Before device initialization? )
If it crashes before device intialization then you've got some invalid D3DPRESENT_PARAMETERS member , i.e. you requested something the device does not support.
Make a debug build with error checking , and test it on the other PC.
By the way, it's useful to add a "Run in REF" option to all your demos in the testing phase, this helps you identify whether it's a problem with the display adapter or with your code ( if the REF runs, then it's the display adapter )
Muhammad Haggag
