TGEA 1.7.0 Beta 1 Bug- GFXD3D9Device infinate reset loop
by metalliandy · in Torque Game Engine Advanced · 03/18/2008 (8:24 pm) · 6 replies
Hey,
I tried changing my resolution whilst in the Atlas demo and it gave me the usual warning about high textures and told me that the application needed to restart before the changes would take effect.
I clicked ok and the screen started to pulsate, almost like the Application focus was shifting between windows.
You can get the console log from here
http://metalliandy.com/TGEA/TGEA bugs.htm
Any Ideas?
I tried changing my resolution whilst in the Atlas demo and it gave me the usual warning about high textures and told me that the application needed to restart before the changes would take effect.
I clicked ok and the screen started to pulsate, almost like the Application focus was shifting between windows.
You can get the console log from here
http://metalliandy.com/TGEA/TGEA bugs.htm
Any Ideas?
#2
take
\TGEA_1_7_0_Beta_1\GameExamples\AtlasDemo\game\common\main.cs
and pop in
$pref::Video::forcePixVersion = true;
$pref::Video::forcedPixVersion = 1.4;
in the onStart() func
and she'll blow her top every time. This ones with a 6800GT, athlon 64 3500+, 1 gig of ram, 80 gig drive with 8 left (since we are talking paged from drive, after all).
03/18/2008 (9:13 pm)
Ouch. managed to consistently reproduce this one:take
\TGEA_1_7_0_Beta_1\GameExamples\AtlasDemo\game\common\main.cs
and pop in
$pref::Video::forcePixVersion = true;
$pref::Video::forcedPixVersion = 1.4;
in the onStart() func
and she'll blow her top every time. This ones with a 6800GT, athlon 64 3500+, 1 gig of ram, 80 gig drive with 8 left (since we are talking paged from drive, after all).
#3
Thanks for the reply :)
I recorded a video of the bug which you can get here
http://metalliandy.com/TGEA/bugs/TGEA_1.7.0_Beta_1/GFXD3D9Device infinate reset loop video.html
My PC is the following:-
Windows XP Home SP2 (with all current updates applied)
AMD Athlon 64 X2 5600+ @ 2800 MHz (Liquid cooled)
2GB DDR2 PC2-6400 (2 x 1024 @ 400 MHz with 4-4-4-12 timings)
NVIDIA GeForce 8800 GTX
Asus M2N32-SLI Deluxe ( nVidia nForce 590 SLI)
Maxtor Sata 2 HDD C:\ (250GB OS and Install)
Samsung Sata 2 HDD D:\ (400GB Data)
DirectX Version 9.0c (March 2008)
ViewSonic VX912 - 19 inches 1280x1024@60Hz
As for performance it performs very well
I can play Crysis with everything on High @1280x1024 with 30-40 FPS
Oblivion with everything on High @1280x1024 with 50-60 FPS
ET:QW with everything on High @1280x1024 with 50-60 FPS
With the following 3D Mark scores
3DMark06
10013 3DMarks
3DMark 05
15308 3DMarks
PCMark 05
6252 PCMarks
If i there is anything else you need mate, give me a shout and i will try my best to help you :)
03/18/2008 (9:21 pm)
Hey Stephen,Thanks for the reply :)
I recorded a video of the bug which you can get here
http://metalliandy.com/TGEA/bugs/TGEA_1.7.0_Beta_1/GFXD3D9Device infinate reset loop video.html
My PC is the following:-
Windows XP Home SP2 (with all current updates applied)
AMD Athlon 64 X2 5600+ @ 2800 MHz (Liquid cooled)
2GB DDR2 PC2-6400 (2 x 1024 @ 400 MHz with 4-4-4-12 timings)
NVIDIA GeForce 8800 GTX
Asus M2N32-SLI Deluxe ( nVidia nForce 590 SLI)
Maxtor Sata 2 HDD C:\ (250GB OS and Install)
Samsung Sata 2 HDD D:\ (400GB Data)
DirectX Version 9.0c (March 2008)
ViewSonic VX912 - 19 inches 1280x1024@60Hz
As for performance it performs very well
I can play Crysis with everything on High @1280x1024 with 30-40 FPS
Oblivion with everything on High @1280x1024 with 50-60 FPS
ET:QW with everything on High @1280x1024 with 50-60 FPS
With the following 3D Mark scores
3DMark06
10013 3DMarks
3DMark 05
15308 3DMarks
PCMark 05
6252 PCMarks
If i there is anything else you need mate, give me a shout and i will try my best to help you :)
#4
03/18/2008 (10:32 pm)
Thanks for the repro steps guys! I will get this bug logged.
#5
NVidia 8800 GTX Windows XP 169.21-driver
03/19/2008 (4:38 pm)
That happens also with the T3D demo NVidia 8800 GTX Windows XP 169.21-driver
#6
I encountered it after following the steps in my bug report and testing almost every resolution available. The resolution that did it for me was 400x300.
03/20/2008 (12:02 pm)
I can confirm this happened to me once while I was ferreting out that MessagBoxOk bug.I encountered it after following the steps in my bug report and testing almost every resolution available. The resolution that did it for me was 400x300.
Torque 3D Owner Stephen Zepp
Can you give some more detailed specifics of your machine, including:
OS, service packs
Graphics card
Hard drive
general performance (is the machine particularly slow to do anything, like large hard drive access, etc).
We'd love to nail this one down, but as I mentioned, I'm the only one to have ever seen it in 3+ months of internal testing, and even I couldn't duplicate it past the one time I saw it.