Wierd crash problems 1.01
by Bloodknight · in Torque 3D Professional · 03/23/2010 (7:49 am) · 6 replies
While i realise that 1.01 isnt the latest version it IS the current stable release version and the one some people are actually using. i also realise that this problem doesnt occur in 1.1 beta
Heres my rig - Win 7 Ultimate 64bit, Nvidia GTX260(driver 196.21 w7 x64), AMD Phenom II 965, 8GB Ram, using the Feb 2010 DX SDK
Here is where it gets wierd, i just bought the awesome CCK and was playing around with it, the next day i get up and start torque as usual and it just crashes out, did a full recompile on the debug and ran it from Visual Studio and it worked, so i close down visual studio and launch the project and it crashes out again. So as long as i launch 1.01 from visual studio it works fine, if i use the toolbox or torsion or even direct launch it crashes at startup.
Ive tried run as admin, ive tried multiple compatability options, all to no avail.
Ive searched for various win 7 problems in the forums here and couldnt find what i needed, so i figured id post, clearly there IS a fix because 1.1 beta works fine, so if anybody knows what particular issue fixes this that would be grand as for the moment i'm a but stuck with 1.0.1 and usuing visual studio as a launch mechanism is a bit cumbersome :p
this is where the console log ends when it crashes
this is the segment when it works
The answer is probably on the forum somewhere, but i sure couldnt find it, if you do know and could link that would be great
Heres my rig - Win 7 Ultimate 64bit, Nvidia GTX260(driver 196.21 w7 x64), AMD Phenom II 965, 8GB Ram, using the Feb 2010 DX SDK
Here is where it gets wierd, i just bought the awesome CCK and was playing around with it, the next day i get up and start torque as usual and it just crashes out, did a full recompile on the debug and ran it from Visual Studio and it worked, so i close down visual studio and launch the project and it crashes out again. So as long as i launch 1.01 from visual studio it works fine, if i use the toolbox or torsion or even direct launch it crashes at startup.
Ive tried run as admin, ive tried multiple compatability options, all to no avail.
Ive searched for various win 7 problems in the forums here and couldnt find what i needed, so i figured id post, clearly there IS a fix because 1.1 beta works fine, so if anybody knows what particular issue fixes this that would be grand as for the moment i'm a but stuck with 1.0.1 and usuing visual studio as a launch mechanism is a bit cumbersome :p
this is where the console log ends when it crashes
--------- Parsing Arguments --------- Binding server port to default IP UDP initialized on port 0 Attempting to create GFX device: NVIDIA GeForce GTX 260 (D3D9) Device created, setting adapter and enumerating modes Cur. D3DDevice ref count=1 Pix version detected: 3.000000 Vert version detected: 3.000000 Maximum number of simultaneous samplers: 16 Number of simultaneous render targets: 4 Hardware occlusion query detected: Yes
this is the segment when it works
--------- Parsing Arguments ---------
Binding server port to default IP
UDP initialized on port 0
Attempting to create GFX device: NVIDIA GeForce GTX 260 (D3D9)
Device created, setting adapter and enumerating modes
Cur. D3DDevice ref count=1
Pix version detected: 3.000000
Vert version detected: 3.000000
Maximum number of simultaneous samplers: 16
Number of simultaneous render targets: 4
Hardware occlusion query detected: Yes
WMIVideoInfo: DxDiag initialized
Initializing GFXCardProfiler (D3D9)
o Chipset : 'GeForce GTX 260'
o Card : 'GeForce GTX 260'
o Version : '8.17.0011.9621'
- Scanning card capabilities...
GFXCardProfiler (D3D9) - Setting capability 'autoMipMapLevel' to 1.
GFXCardProfiler (D3D9) - Setting capability 'maxTextureWidth' to 8192.
GFXCardProfiler (D3D9) - Setting capability 'maxTextureHeight' to 8192.
GFXCardProfiler (D3D9) - Setting capability 'maxTextureSize' to 8192.
GFXCardProfiler (D3D9) - Setting capability 'lerpDetailBlend' to 1.
GFXCardProfiler (D3D9) - Setting capability 'fourStageDetailBlend' to 1.
- Loading card profiles...
- Loaded card profile core/profile/D3D9.cs
- No card profile core/profile/D3D9.GeForceGTX260.cs exists
- No card profile core/profile/D3D9.GeForceGTX260.GeForceGTX260.cs exists
- No card profile core/profile/D3D9.GeForceGTX260.GeForceGTX260.81700119621.cs exists
% - Initialized CoreThe answer is probably on the forum somewhere, but i sure couldnt find it, if you do know and could link that would be great
About the author
#2
TGEA 1.7.1
TGEA 1.8.1
all fail on this system, this means any demos or packs (which annoyingly appears to be ALL demos and packs) that rely on these two version fail to run on this system.
1.8.1 suffers no such problems.
I posted here cause since the death of GG nobody at TP seemingly cares about anything but T3D or iGarbage or iJunk products and technology.
i'm beginning to miss GarageGames...
Post edited by moderator - Please keep it clean, thanks.
Post edited by OriginaPoster - Please replace words with something suitable, if you must excercise censorship.
04/28/2010 (5:49 pm)
ok, this is nucking futs...TGEA 1.7.1
TGEA 1.8.1
all fail on this system, this means any demos or packs (which annoyingly appears to be ALL demos and packs) that rely on these two version fail to run on this system.
1.8.1 suffers no such problems.
I posted here cause since the death of GG nobody at TP seemingly cares about anything but T3D or iGarbage or iJunk products and technology.
i'm beginning to miss GarageGames...
Post edited by moderator - Please keep it clean, thanks.
Post edited by OriginaPoster - Please replace words with something suitable, if you must excercise censorship.
#3
Isn't that the Nvidia driver I warned everyone to stay away from? Oh, no that was 196.75.
I would think this got to be a driver issue of some kind, especially if previous TGEA builds are failing. Though it's strange some builds are functioning and some aren't. Have you updated your DX vid drivers since the last time?
04/28/2010 (6:13 pm)
Not true at all. Just because they're no longer a product in the store doesn't mean we don't care about them. If that were the case I would have stopped answering questions about them a long time ago.Isn't that the Nvidia driver I warned everyone to stay away from? Oh, no that was 196.75.
I would think this got to be a driver issue of some kind, especially if previous TGEA builds are failing. Though it's strange some builds are functioning and some aren't. Have you updated your DX vid drivers since the last time?
#4
as for answering questions in the TGEA forums, i must be missing those... sorry but theres not exactly a hive of activity from the TP powers in there...
04/28/2010 (6:43 pm)
the Nvidia driver has changed about 3 times since the FryCardGate scandal (but 196.21 was the evile set i think), the fact that TGEA 1.8.1 fails when TGEA 1.8.2 doesnt and T3D 1.0.1 fails and T3D 1.1 doesnt... is kind of freaking me out. Whats even more odd is the fact that regardless what version it is, if i run it from inside Visual Studio it runs as if there was never a problem at all, now i know that VS and debuging provides some kind of annoying sandboxing, but it sure as heck makes it difficult to track down a problem when the problem wont occur when you try to debug it.as for answering questions in the TGEA forums, i must be missing those... sorry but theres not exactly a hive of activity from the TP powers in there...
#5
Faulting module name: MMDevApi.dll, version: 6.1.7600.16385, time stamp: 0x4a5bda29
Exception code: 0xc0000005
Fault offset: 0x00018c7d
Faulting process id: 0x1434
Faulting application start time: 0x01cae740916a9a71
Faulting application path: C:\Torque Demos\GMK\GameMechanicsKitDemo.exe
Faulting module path: C:\Windows\System32\MMDevApi.dll
Report Id: d63a35e1-5333-11df-a996-005056c00008
I guess i'm fubar'd, fixing windows DLLs is definately beyond my remit
04/28/2010 (7:09 pm)
Faulting application name: GameMechanicsKitDemo.exe, version: 0.0.0.0, time stamp: 0x4a16ba43Faulting module name: MMDevApi.dll, version: 6.1.7600.16385, time stamp: 0x4a5bda29
Exception code: 0xc0000005
Fault offset: 0x00018c7d
Faulting process id: 0x1434
Faulting application start time: 0x01cae740916a9a71
Faulting application path: C:\Torque Demos\GMK\GameMechanicsKitDemo.exe
Faulting module path: C:\Windows\System32\MMDevApi.dll
Report Id: d63a35e1-5333-11df-a996-005056c00008
I guess i'm fubar'd, fixing windows DLLs is definately beyond my remit
#6
http://www.torquepowered.com/community/forums/viewthread/96567
its not just me
04/28/2010 (7:22 pm)
woothttp://www.torquepowered.com/community/forums/viewthread/96567
its not just me
Torque 3D Owner Bloodknight
Bloodknight Studios