Objects not rendering sometimes
by Harley · in Torque Game Engine · 05/27/2005 (10:17 pm) · 6 replies
Hi,
I wasn't sure where to post this but I have been having a problem with Torque where sometimes it wont render objects when it starts. Sometimes it might just be missing .dts objects other times the only thing i can see is the terrain. To fix it I just quit the mission then reload the mission. Has anyone else had this problem? I thought that may it was my pc but I have since bought a new laptop with a nVidia 6800 vid 256mb and it does exactly the same thing. The old pc had a gf4 128mb vid ram. I haven't touched anything in the engine as far as rendering goes.
Thanks,
Harley.
I wasn't sure where to post this but I have been having a problem with Torque where sometimes it wont render objects when it starts. Sometimes it might just be missing .dts objects other times the only thing i can see is the terrain. To fix it I just quit the mission then reload the mission. Has anyone else had this problem? I thought that may it was my pc but I have since bought a new laptop with a nVidia 6800 vid 256mb and it does exactly the same thing. The old pc had a gf4 128mb vid ram. I haven't touched anything in the engine as far as rendering goes.
Thanks,
Harley.
#2
No console errors. Not sure what you mean by the objects being in scope, but why would they not render the first time the mission is loaded, but when I exit out of the mission, then reload it they are fine? Its not that they dissappear its that they dont render in the first place.
Thanks,
h
05/27/2005 (11:04 pm)
Hi Ben,No console errors. Not sure what you mean by the objects being in scope, but why would they not render the first time the mission is loaded, but when I exit out of the mission, then reload it they are fine? Its not that they dissappear its that they dont render in the first place.
Thanks,
h
#3
Thanks again,
Harley.
05/27/2005 (11:07 pm)
Also what is the best way to check that the renderObject is being called? Sorry I am a fairly amateur c++ coder..Thanks again,
Harley.
#4
When I tried to debug my problem, I found that when it failed it was because where it was checking trigger collision it was returning some whacky code like #IND.8/ or something like that, I guess I should have written it down, but thats pretty close if not exact. And of course, when there was no failure the correct figures were returned. I have no explanation fo this strange behavior. The only clue I have is "Something in missionlighting".
05/28/2005 (3:43 am)
I have seen a variation of this problem. Basicly, I load a mission with triggers, and if the mission lighting is being done, occasionally the triggers will not work even though they are in the tree, and render exactly where they should when the editor is active. But if I quit back to the main menu, then start the mission again, they work just fine. As long as the mission lighting file stays the same, they will always work, but 50% of the time they will fail when the missionlighting is done.When I tried to debug my problem, I found that when it failed it was because where it was checking trigger collision it was returning some whacky code like #IND.8/ or something like that, I guess I should have written it down, but thats pretty close if not exact. And of course, when there was no failure the correct figures were returned. I have no explanation fo this strange behavior. The only clue I have is "Something in missionlighting".
#5
05/28/2005 (7:09 am)
@GTC: hmm thats interesting. How did you go about debugging it? What was that #IND.8 code returned from?
#6
06/25/2005 (6:45 am)
For those interested I believe that the strange rendering problems I was having was because I didn't have en "eye" node in my player.dts mode, I only had a "cam" node. I figured that it had something to do with the player.dts that I had created because the problems only started occuring when I used my model and not the one that comes with the sdk. 
Associate Kyle Carter