All Static Objects losing skins?
by Chris · in Torque Game Engine · 04/11/2004 (7:35 am) · 10 replies
Been playing around for the last few days and I load up my demo this morning and all static objects seem to have lost their skins. If you walk up right next to the object the skin seems to load, otherwise everything just has a plain white skin.
Any thoughts?
Another thing I noticed in my logging is the following:
Error: shape game/data/shapes/weapons/crossbow/ammo.dts-collision detail 0 (Collision-3) bounds box invalid!
Not sure if tis has anything to do with it, but it's the only major error I see in mission startup.
Thanks in advance!
Any thoughts?
Another thing I noticed in my logging is the following:
Error: shape game/data/shapes/weapons/crossbow/ammo.dts-collision detail 0 (Collision-3) bounds box invalid!
Not sure if tis has anything to do with it, but it's the only major error I see in mission startup.
Thanks in advance!
About the author
#2
04/11/2004 (9:34 am)
Yeah, it looks like they are getting null values. Not sure why though.
#3
Also, switching to D3D cleared up any problems. So now I'm wondering. Anyone else having issues with a GF 5900? I tried the 56.64 and the latest 56.72's and both had the same problem.
04/11/2004 (9:40 am)
Alright, I _partially_ figured this out. Turning off the "Application controlled" setting on antialiasing and anisotropic filtering seemed to clear up part of the issues. (Trees would occasional have visible trunk textures but not foliage until I got close.) I also have filtering turned completely off.Also, switching to D3D cleared up any problems. So now I'm wondering. Anyone else having issues with a GF 5900? I tried the 56.64 and the latest 56.72's and both had the same problem.
#4
On a unrelated note, my work machine has a GF TI4200 with the 56.64 drivers and it works fine.
- C
04/12/2004 (6:45 am)
Update: Definitely a drivers issue. I switched back to the latest WHQL NVidia drivers available through WinUpdate and everything showed up fine. Version that worked on the 5900 was v52.16. 56.64 and 56.72 were flaky.On a unrelated note, my work machine has a GF TI4200 with the 56.64 drivers and it works fine.
- C
#5
04/12/2004 (9:54 am)
Ah, driver problems... how grand they are.
#6
04/13/2004 (6:25 am)
Note: I've seen this sort of thing with a GF 5950 (56.72 drivers) but it only seems to happen when I alt-tab during the mission load. All DTS objects are skinned plain black until I restart.
#7
I'm pretty sure the problem is that the light map is missing; once it's like this, it doesn't come back, even when we relight.
10/31/2005 (2:44 pm)
I have this problem as well when I alt-tab out of the app while a mission is loading. I have a GF 5700VE with forceware 77.72, but I think we've seen it with RocketBowl on ATI cards as well -- I'm not sure that this is a driver issue.I'm pretty sure the problem is that the light map is missing; once it's like this, it doesn't come back, even when we relight.
#8
Sorry... just had to ask.
10/31/2005 (7:29 pm)
Just curious... do the objects you are loading happen to be snakes?Sorry... just had to ask.
#9
10/31/2005 (7:34 pm)
Cute. Cute joke.
#10
11/10/2005 (8:22 am)
So, does anybody have any ideas about how to keep the light map from going away when you ALT-TAB out during loading? This seems to happen on all machines. 
Associate Kyle Carter