   [HELP] Direct3D
  Hi all,So, time ago i tested an d3d9 wrapper downloaded from http://www.mikoweb.eu/index.php?node=28 and compiled by me and it worked.Now if i download same wrapper and compile it by me no longer work's... why this?I have Visual C++ 2008 Express Edition and i use Microsoft DirectX SDK (March 2009)   
  Because something has changed between then and now.   ;Quote:Original post by Evil SteveBecause something has changed between then and now.No no no the dll is same...   ;Quote:Original post by CosmyQuote:Original post by Evil SteveBecause something has changed between then and now.No no no the dll is same...Well, something has changed, or it would work.What exactly is the error? Is it a compile error? Does the game crash? Do you get a blue screen of death? Does the computer burst into flames?If it's a compile error, what are the errors? Can you compile any other (non-DirectX) apps? Can you compile any other DirectX apps? Do the debug runtimes say anything?If the game crashes, where does it crash? What is the error? What does the debugger tell you? Are you checking your return values?Saying it "no longer works" means absolutely nothing...   ;Quote:Original post by Evil SteveQuote:Original post by CosmyQuote:Original post by Evil SteveBecause something has changed between then and now.No no no the dll is same...Well, something has changed, or it would work.What exactly is the error? Is it a compile error? Does the game crash? Do you get a blue screen of death? Does the computer burst into flames?If it's a compile error, what are the errors? Can you compile any other (non-DirectX) apps? Can you compile any other DirectX apps? Do the debug runtimes say anything?If the game crashes, where does it crash? What is the error? What does the debugger tell you? Are you checking your return values?Saying it "no longer works" means absolutely nothing...The game crash i tested it with 4-5 DirectX apps and all crashes.So, now it work... But yesterday the dll compiled by me doesn't worked... and now it work... WHY THIS??? Maybe because i open windows update and i updated some applications, is this possible?;Quote:Original post by CosmyThe game crash i tested it with 4-5 DirectX apps and all crashes.So, now it work... But yesterday the dll compiled by me doesn't worked... and now it work... WHY THIS???Quote:Original post by Evil Steve...Can you compile any other DirectX apps? Do the debug runtimes say anything?If the game crashes, where does it crash? What is the error? What does the debugger tell you? Are you checking your return values?Quote:Original post by CosmyMaybe because i open windows update and i updated some applications, is this possible?It's possible, but it's quite unlikely.You need to give us more information. Saying "This code crashes" doesn't give us anything to go on. Using your debugger, you can find out at least which line it crashes on. You can also find out what the exact error is (E.g. access violation reading 0x00000000), and you can use the debug runtimes to see if any DirectX call is failing which you're not correctly checking for.Do all of the apps you're compiling crash in the same way? How about the SDK samples?   ;Quote:Original post by Evil SteveQuote:Original post by CosmyThe game crash i tested it with 4-5 DirectX apps and all crashes.So, now it work... But yesterday the dll compiled by me doesn't worked... and now it work... WHY THIS???Quote:Original post by Evil Steve...Can you compile any other DirectX apps? Do the debug runtimes say anything?If the game crashes, where does it crash? What is the error? What does the debugger tell you? Are you checking your return values?Quote:Original post by CosmyMaybe because i open windows update and i updated some applications, is this possible?It's possible, but it's quite unlikely.You need to give us more information. Saying "This code crashes" doesn't give us anything to go on. Using your debugger, you can find out at least which line it crashes on. You can also find out what the exact error is (E.g. access violation reading 0x00000000), and you can use the debug runtimes to see if any DirectX call is failing which you're not correctly checking for.Do all of the apps you're compiling crash in the same way? How about the SDK samples?Quote:Original post by CosmyThe game crash i tested it with 4-5 DirectX apps and all crashes.So, now it work... But yesterday the dll compiled by me doesn't worked... and now it work... WHY THIS???I meant the DLL crash i tested it with 4-5 DirectX apps and all crashes.So, now it work... But yesterday the dll compiled by me doesn't worked...But if the dll returning to crash i will debug runtimes.   ;  Are you running the DLL through visual studio? It's much easier to debug that way, than just putting the DLL in the directory with the app you want to proxy with (Since you can step through the code and so on).   ;Quote:Original post by Evil SteveAre you running the DLL through visual studio? It's much easier to debug that way, than just putting the DLL in the directory with the app you want to proxy with (Since you can step through the code and so on).No.. i put the dll in the same directory of the app :)   ;  Now the dll crash again with an Direct3D application...D3DX: (INFO) Using SSE2 optimizationsD3DX: Detected mixed device: faceClampHW = 4Eccezione first-chance a 0x5e3d179f in SkinnedMesh.exe: 0xC0000005: Violazione di accesso nella lettura del percorso 0xfeeefeee.Eccezione non gestita a 0x5e3d179f in SkinnedMesh.exe: 0xC0000005: Violazione di accesso nella lettura del percorso 0xfeeefeee.Il programma '[1868] SkinnedMesh.exe: Nativo' è terminato con il codice -1073741819 (0xc0000005).:(   