D3D seems not to work on all machines
by Stefan Beffy Moises · in Torque Game Engine · 02/12/2002 (6:57 am) · 16 replies
QUOTE: "I bought the SDK last week and jumped right into the demo. The openGL version worked fine, but when I tried to display in D3D, it completely crapped out with polys everywhere but nothing in the game discernible other than the menus. Any suggestions or comments to make it work in both modes?"
There are some people (including me ;-)) having problems with D3D in Torque - actually there is a thread in "Getting Started" (http://www.garagegames.com/index.php?sec=mg&mod=forums&page=result.thread&qt=3437), but I think it should be here in the "Bugs" thread instead...
Some guys running Torque in Win2K or WIN XP aren't able to run the demo in D3D mode - but Tribes2 is running fine, though... So basically the point is to find out if GG changed any code concering the DirectX rendering stuff for the latest release. Could some employee try to answer this, please? Maybe we can track down the problem ...
I've already tried different drivers (Nvidia Detonator), at the moment I'm running the latest one available (27.42 I think) and DirectX 8.1 under Win2k AS. My PC is a COMPAQ Pressario 866, 384MB, VIA Board (latest 4-in-1 drivers) with a Leadtek Geforce 2 GTS Pro 64 MB.
Maybe all the other guys having these problems could post their exact "equipment"?
Thanks for any help or participation!
There are some people (including me ;-)) having problems with D3D in Torque - actually there is a thread in "Getting Started" (http://www.garagegames.com/index.php?sec=mg&mod=forums&page=result.thread&qt=3437), but I think it should be here in the "Bugs" thread instead...
Some guys running Torque in Win2K or WIN XP aren't able to run the demo in D3D mode - but Tribes2 is running fine, though... So basically the point is to find out if GG changed any code concering the DirectX rendering stuff for the latest release. Could some employee try to answer this, please? Maybe we can track down the problem ...
I've already tried different drivers (Nvidia Detonator), at the moment I'm running the latest one available (27.42 I think) and DirectX 8.1 under Win2k AS. My PC is a COMPAQ Pressario 866, 384MB, VIA Board (latest 4-in-1 drivers) with a Leadtek Geforce 2 GTS Pro 64 MB.
Maybe all the other guys having these problems could post their exact "equipment"?
Thanks for any help or participation!
About the author
#2
I have P3 500 / Voodoo 3 / Win 98 / and I have the same problem with D3D rendering. It definately sounds like a bug that has entered the engine in the last release, but I've only ever had 1_1_1 so I can't say whether it would have worked for me in older releases.
02/12/2002 (12:24 pm)
Hi,I have P3 500 / Voodoo 3 / Win 98 / and I have the same problem with D3D rendering. It definately sounds like a bug that has entered the engine in the last release, but I've only ever had 1_1_1 so I can't say whether it would have worked for me in older releases.
#3
Unfortunately, the Torque sample still doesn't render in D3D properly. :(
02/12/2002 (4:29 pm)
I have just installed a really good demo app called Crime Force and D3D rendering works! I get much improved frame rates in D3D which is great news.Unfortunately, the Torque sample still doesn't render in D3D properly. :(
#4
02/12/2002 (9:48 pm)
Crime Force is 1.0.0 or 1.1.0
#6
02/13/2002 (10:54 pm)
Exactly! Crimeforce works in OGL and D3D!
#7
I suppose the ultimate question is: does anyone have a program working in D3D that was compiled using v1.1.1 ? If not, then there's obviously something wrong with the latest release.
02/14/2002 (5:02 am)
Being a new user I had only ever used v1.1.1. However, I downloaded the files necessary to run v1.1.0 and the sample app runs fine now in D3D. As Kenneth said, Crime Force must have been compiled used v1.1.0 (or earlier).I suppose the ultimate question is: does anyone have a program working in D3D that was compiled using v1.1.1 ? If not, then there's obviously something wrong with the latest release.
#8
02/14/2002 (9:34 am)
Ok, this is strange... as far as I know, there haven't been any changes to the D3D "driver" code. ? I'll add it to my list of things to look into.
#9
02/14/2002 (11:34 am)
I just tried the D3D driver and it's definitely doing something wierd, looks like the terrain engine is totally messed up... It did work fine for me in 1.0, so something has changed, we'll try and track it down.
#10
02/14/2002 (12:11 pm)
Cool! Just keep us informed :-) It would be interesting if there is anyone out there who has a working D3D app with release 1.1.1?
#11
www.garagegames.com/index.php?sec=mg&mod=forums&page=result.thread&qt=3656
02/19/2002 (5:24 pm)
Tim, see this thread, about disabling TERRAIN_STORE_NORMALS when NPATCH is enabled...:www.garagegames.com/index.php?sec=mg&mod=forums&page=result.thread&qt=3656
#12
02/19/2002 (11:44 pm)
Hm, that didn't help for me ... D3D is still messed up :-(
#13
Setting TERRAIN_STORE_NORMALS to 0 in "terrain/terrRender.h" solves the D3D problem!!
Check out the above mentioned thread - and thanks again, Frank!
02/20/2002 (12:14 am)
YES!! It DID work for me!!Setting TERRAIN_STORE_NORMALS to 0 in "terrain/terrRender.h" solves the D3D problem!!
Check out the above mentioned thread - and thanks again, Frank!
#14
02/20/2002 (7:51 am)
Worked like a charm for me too! Thanks!
#15
-d
02/20/2002 (6:22 pm)
Disable the store_normals flag locally. It will have no impact on the engine at the moment. See my comment in the other thread for more details.-d
Torque Owner Ken Finney
Tubetti World