Crash with ATI Rage 128/Fury
by Mike Stoddart · in Torque Game Engine · 08/09/2002 (1:09 pm) · 7 replies
Has anyone successfully run the Torque engine on a machine with an ATI Rage 128/Fury? I think the card has 32Mb of AGP memory, and runs at 2X AGP so I thought that it was decent enough to run. I'm still tracking this down, but the -console option shows the last line to read:
and the path to the player.dts is correct.
I'm running this on a Celeron 500 with 256Mb, under Win2k with Service Pack 2. Unfortunately this machine doesn't have Visual Studio on. Oh before I forget, I tried it both under OpenGL and DirectX running in a 640x480 window at 16bit.
Thanks
Quote:Validation required for shape ......
and the path to the player.dts is correct.
I'm running this on a Celeron 500 with 256Mb, under Win2k with Service Pack 2. Unfortunately this machine doesn't have Visual Studio on. Oh before I forget, I tried it both under OpenGL and DirectX running in a 640x480 window at 16bit.
Thanks
#2
08/09/2002 (3:36 pm)
It happens while the mission is being downloaded to the client. I can get into the main menu ok, then when I select my mission it happens during that before the main game screen appears. I'm trying to track it down further, to see if it's something stupid in my game, but it works on four other PCs.
#3
I gave up after endless hours of trying to figure our and understand that assembly crud ;)
08/09/2002 (3:56 pm)
I had a similar issue with my laptop, try the test mission. Does that produce the crash? When I started to track it the path lead me to assembly code that pointed to the ATI driver. I think TGE is using something that ATI does nopt have or has but is older and not supported the way TGE uses it *shrug*I gave up after endless hours of trying to figure our and understand that assembly crud ;)
#4
08/09/2002 (6:44 pm)
I've tested the Torque demo game on an ATI Rage 128 (16megs); worked like a charm.
#6
I've run against a variety of ATI chips (on mac and win) without crashes, so I'd be interested to see what the issue turns out to be.
Also try fullscreen (if you haven't) and 32 bit (if you haven't) just to round out things.
I seem to recall you can write the log to disk -- you should do that, and see if there are any errors earlier on.
d
08/09/2002 (7:52 pm)
And not to sound stupid but make sure you have recent drivers for the card.I've run against a variety of ATI chips (on mac and win) without crashes, so I'd be interested to see what the issue turns out to be.
Also try fullscreen (if you haven't) and 32 bit (if you haven't) just to round out things.
I seem to recall you can write the log to disk -- you should do that, and see if there are any errors earlier on.
d
#7
Thanks
08/09/2002 (9:53 pm)
I haven't tried the latest drivers; it's the missus' PC and she's not keen on me messing around with it. So I'm not sure I can do that, although I'm fairly sure that that is the problem.Thanks
Torque Owner Tim Gift