Game Development Community

Possible bug with multiple T2DSceneGraphs

by Will O-Reagan · in Torque X 2D · 07/18/2010 (1:57 am) · 4 replies

I have a scene overlay I've been working on, and its been working fine for about one and a half months. But recently, I've decided to do more scene loading, and its been having some problems. It seems to every once in a while load the overlay into a different scenegraph then the one I'm using, which pretty much makes the overlay invisible, still there, just not sure where.

I've checked time and again, the times when it is visible (90%) objects are in same scene graph, its when they are not (10%), I dont see the overlay at all. Of course, I can unload and reload the overlay, and its back, in the right scene graph apparently.

Could this be a bug, because I notice that sometimes the Id's of the scene graphs themselves seem to change, and I'm not sure what I'm looking for in the source. Can you render out multiple scene graphs, etc, whats going on here? Is this different loading a mistake, because it didn't find the existing scenegraph?

-Will

About the author

I have a degree in dramatic art, and literature, from UC Santa Barbara. I've worked for a few studios, also at Animax Ent in 2008, and some smaller studios. Currently studying Computer Science at CSU Channel Islands.


#1
07/18/2010 (2:35 am)
This issue has been resolved by manually setting each T2DSceneObject's SceneGraph in the database via a loop, to my specific T2DSceneGraph.. but pretty sure this is a bug.. only I'm not sure how you would want to reproduce it, or if this is of any interest.
#2
07/18/2010 (10:12 pm)
What engine version are you using? Beta, 3.14, Pino's version?

If it is the Beta then you should use the bug submission format for your post.
#3
07/18/2010 (10:20 pm)
Thats the thing, I'm not really sure what version maybe a 3.15, just probing around to see if anyone knows what I'm talking about. I don't know how to reproduce this at all, so I don't want to turn it into an official issue on my part.
#4
07/19/2010 (10:44 am)
Wierd stuff can indeed happen with scenegraphs if you go beyond loading single scenes and are not familiar with what the underlying implementation is doing. If you can check what version you're using when you get the bug that would really help to track down the issue.