   Weird errors: Program runs fine on my machine but not on other people's machines
  Hello again.Thanks for all the help so far. I have figured out how to assign materials to my triangles and light them up using a simple directional light. Thus far I have been successful.However, the program I compile on my machine isn't quite working on other people's machines. Each time I've tried with earlier versions that work fine on my machine, running my program elsewhere will just get me some kind of error message, or in my friend's case the graphics were way distorted.The below images are what me and my friend are seeing on our own computers. She has DirectX 8.0 and I have DirectX 9.0a. I'm using the SDK for DirectX 8.1 which i got from the microsoft website:My computer:Friend's computer:I'm guessing it has something to do with my compile options, which I have really no clue on what they mean. I'm trying to set them as close to what the book says to set them, since the book references Visual C++ 6.0, and I have Visual C++ .NET which rearranged some of the things spoken about in the book.If anyone has any suggestions, feel free to share them. I'll be looking it up on the net in the meantime.Thanks for your help,-TJ[edited by - PsychoGears on August 2, 2003 3:19:44 PM][edited by - PsychoGears on August 2, 2003 3:20:51 PM]
  Post the specs on yours and your friend''s computers.  It might be hardware-related. ;  Post the specs on yours and your friend''s computers.  It might be hardware-related. ;  You must be assuming something about the defaults which is one way on your machine, and another on others.I''d recommend you check your basic directX init commands. I once had distorted graphics like you''re seeing when I initialized the Z-buffer incorrectly, and also when I wasn''t clearing it right.That''s a good place to start I guess . Hope this helps.   Sirob Yes.»Footman, at large. ;  Looks like a Z buffering artifact of some form (see the sawtooth pattern)1) Make sure the desktop colour depth is the same on both machines2) Make sure you''re clearing the Z buffer3) Make sure the range specified by your near and far clip planes isn''t too huge. Increase "near" as much as possible - that should never be 0.4) As mentioned, don''t rely on a state to be set to its default. In an ideal world they would be. In the real world of broken drivers etc they aren''t always.5) Have you been playing with any states such as ZBIAS ?   --Simon O''Connorex  -Creative AsylumProgrammer &Microsoft MVP;quote:She has DirectX 8.0 and I have DirectX 9.0a. I''m using the SDK for DirectX 8.1 which i got from the microsoft website:Could this be the issue? If she only has DX8 and the app ix DX8.1?Neil   WHATCHA GONNA DO WHEN THE LARGEST ARMS IN THE WORLD RUN WILD ON YOU?!?! ;  3) Make sure the range specified by your near and far clip planes isn''t too huge. Increase "near" as much as possible - that should never be 0.This is it, i''m pretty sure.When setting projection matrix, set near plane to say 0.1 and far plane to 100,1000 or so. Setting near plane too close to zero will destroy z buffer precision ;  so will 0.1, i wouldn''t go less than 1. ;  Well, if it was written for 8.1 and she''s only running 8.0, then it could definitely be a problem, and any tech support person would tell you to upgrade to 8.1 before you even bother trying to troubleshoot it.Are you running in the development environment on both machines, or are you just running the .exe file on her machine?  What happens if you do just port the .exe file to her machine?  That might help to eliminate the possibility of any compiler switches.  Then I would say that you''re not enumerating her video adapter properly. 