Crash when changing suns azimuth
by Faraz Ahmed · in · 05/30/2006 (3:13 am) · 1 replies
Hello,
This is related to TLK 1.4 (out of the box). I have run into an odd bug with a new player model that I'm placing into the mission. When I change the azimuth of the Sun to anything but 0 the engine crashes. I've triple checked the alignment of the new models bounding box and the mesh as compared to the orc player model. The shadow on the orc player model changes angle correctly. The crash only happens when my new model is in the mission (as a static shape or as an AIPlayer) and the azimuth of the sun is other than 0. At azimuth 0 the model appears correcly and also animates correctly. Also, the engine doesn't crash if I add the model as a TSStatic and change the azimuth.
Has anyone seen this before? Where should I be poking around to resolve this? Any pointers would be greatly appreciated.
Thanks.
This is related to TLK 1.4 (out of the box). I have run into an odd bug with a new player model that I'm placing into the mission. When I change the azimuth of the Sun to anything but 0 the engine crashes. I've triple checked the alignment of the new models bounding box and the mesh as compared to the orc player model. The shadow on the orc player model changes angle correctly. The crash only happens when my new model is in the mission (as a static shape or as an AIPlayer) and the azimuth of the sun is other than 0. At azimuth 0 the model appears correcly and also animates correctly. Also, the engine doesn't crash if I add the model as a TSStatic and change the azimuth.
Has anyone seen this before? Where should I be poking around to resolve this? Any pointers would be greatly appreciated.
Thanks.
Torque Owner John Kabus (BobTheCBuilder)
Make sure the player has an eye node. This is a common source of player related trouble in the Torque engines. The player code assumes that an eye node exists and references it frequently - this can cause weird results or random crashing.
If you've added the eye node make sure to check out the DTS object in the show tool to verify that the node was exported properly.
If this is not the problem try running TLK in the debugger to see where the problem occurs and post your results in the TLK Private forums so we can talk in more detail.