T2 problem/ v12 question
by Matthew Shapiro · in Torque Game Engine · 06/29/2001 (6:56 pm) · 6 replies
okay first of sorry about the t2 stuff but it is engine related (i think). I just tried it today and ouch. When it's loading the missions after it loads the mission (first load thing) it has a popup saying exception error: (enter number here) blah. i press enter and it continues loading. Now wit hthe training missions i get another popup after loading objects, and finally another one when it's done loading the trianing mission but this time it crashes. Now with lan games by myself i get god awful framerates! even when i'm on the ground. Major skipping with all the options set ot low. Also when I try to change from opengl to d3d it does the exception thing and crashes.
Now. Frankly i got this game from my friend to test out the engine, and it doesn't look good (especially sincei 'm doing the editing and such on the actual engine). I did upgrade online to the highest patch (as far as sierraupdate told me). and i have my system specs posted at the bottom of this post. The training mission crashing i'm suspecting isn't the engine but is this really what will happen with v12 on my computer?
Now there is one thing. I have windows 2000. I know at least in half-life opengl doesn't work on my computer in w2k for some reason, but d3d does, so that may be part of the problem but it doens't explain why it won't change to d3d.
system specs:
Custom built
AMD k6-II 450Mhz w/ 3dnow tech
3dfx voodoo 3 2000 updated with latest drivers
Windows 2000 SP 1
Sound blaster 16
128 megs of RAM
rockwell 56k modem.
CD-RW
Now. Frankly i got this game from my friend to test out the engine, and it doesn't look good (especially sincei 'm doing the editing and such on the actual engine). I did upgrade online to the highest patch (as far as sierraupdate told me). and i have my system specs posted at the bottom of this post. The training mission crashing i'm suspecting isn't the engine but is this really what will happen with v12 on my computer?
Now there is one thing. I have windows 2000. I know at least in half-life opengl doesn't work on my computer in w2k for some reason, but d3d does, so that may be part of the problem but it doens't explain why it won't change to d3d.
system specs:
Custom built
AMD k6-II 450Mhz w/ 3dnow tech
3dfx voodoo 3 2000 updated with latest drivers
Windows 2000 SP 1
Sound blaster 16
128 megs of RAM
rockwell 56k modem.
CD-RW
#2
06/29/2001 (7:32 pm)
Yes it's outdated but htere's nothing i can do about it though and i've always had an outdated computer (hell this computer i got a year last january. before that i had a 90mhz with no 3d card). Frankly i don't care that it's outdated because i'ts becomeing expensive for me to upgrade (since i'm saving a lot of money up for college) and i know a lot of people that will probably play the game on about my machine (give or take a few specs). Also I'm the programmer for the team and there are some essentials that need to go into the engine to make my game work, which means if my computer can't take the engine, i cna't make the game untill i can upgrade :(
#3
As things stand, your major problems are your CPU and video card. The WickedGL drivers could help allot, but if they don't there is something you could do hardware wise without breaking the bank: Upgrade your video card to a GeForce2 or Kyro2 (if you have an AGP slot). Or upgrade to a GeForce2 or Radeon (if you only have PCI slots). If you shopped around online you could find them for around $100 or less. Honestly, not to sound pro-Kyro (I'm a GeForce man actually), but the Kyro would be the best budget card for Tribes2 and the V12 engine.
Side note: Fairly decent new comps (700MHz Athlons and such) can be picked up these days without an OS installed for under $400. They come with pretty generic video cards though and your Voodoo would still be the problem child even in a faster system.
What would be interesting is if one of the developers here cooked up Glide support for the V12.....
06/29/2001 (8:07 pm)
Have you tried the WickedGL drivers for playing the game with your video card? They're out of beta now and I've heard they make a HUGE difference. I think www.planettribes.com has a link to them (can't remember exactly where to go to download them).As things stand, your major problems are your CPU and video card. The WickedGL drivers could help allot, but if they don't there is something you could do hardware wise without breaking the bank: Upgrade your video card to a GeForce2 or Kyro2 (if you have an AGP slot). Or upgrade to a GeForce2 or Radeon (if you only have PCI slots). If you shopped around online you could find them for around $100 or less. Honestly, not to sound pro-Kyro (I'm a GeForce man actually), but the Kyro would be the best budget card for Tribes2 and the V12 engine.
Side note: Fairly decent new comps (700MHz Athlons and such) can be picked up these days without an OS installed for under $400. They come with pretty generic video cards though and your Voodoo would still be the problem child even in a faster system.
What would be interesting is if one of the developers here cooked up Glide support for the V12.....
#4
well i found out one thing. i got this from planettribes faq:
anyways i'm installing wickedgl now i'll get back to you guys.
06/29/2001 (9:13 pm)
thanks i'm downloading the driver demo now.well i found out one thing. i got this from planettribes faq:
Quote:well the game was trying to run it in opengl and crashed when i tried to switch it.
Q. Which video drivers did Dynamix use for QA testing with Tribes 2?
A. Dynamix used the following drivers for their video cards. However, your performance may vary these may work better, but may not be as good as some of the newer versions, even if the newer ones are in beta. (Namely the 12.00 Nvidia drivers.)
blah some cards and drivers and then BAM
Voodoo 3 : 1.07.00 (ONLY runs in D3D)
anyways i'm installing wickedgl now i'll get back to you guys.
#5
06/29/2001 (9:21 pm)
IT WORKED. well seems like i'm buying the full version of those drivers. Tribes 2 is smooth as hell now!
#6
Great that it is working with the OpenGL drivers you located.
Actually the T2 readme file says to choose D3D *only* for the Voodoo cards. OpenGL on the Voodoo3 is only the "MiniGL" version.
The exception errors on the Voodoo3 occur when you have the desktop running at a color depth other than 16-bit with DirectX.
Setting the desktop to 16bpp should fix the errors.
Alternately, running in a Window (vs full screen) will also usually fix it.
Lastly, edit the Prefs\ClientPrefs.cs file in the T2 game folder and turn *off* the AllowOpenGL and PreferOpenGL lines near the bottom of the file when running DX.
David
08/19/2001 (3:05 am)
Hi,Great that it is working with the OpenGL drivers you located.
Actually the T2 readme file says to choose D3D *only* for the Voodoo cards. OpenGL on the Voodoo3 is only the "MiniGL" version.
The exception errors on the Voodoo3 occur when you have the desktop running at a color depth other than 16-bit with DirectX.
Setting the desktop to 16bpp should fix the errors.
Alternately, running in a Window (vs full screen) will also usually fix it.
Lastly, edit the Prefs\ClientPrefs.cs file in the T2 game folder and turn *off* the AllowOpenGL and PreferOpenGL lines near the bottom of the file when running DX.
David
Jeff Highsmith