Game Development Community

Meshes & prefabs invisible when added to level

by Nils Eikelenboom · in Torque 3D Professional · 02/16/2013 (11:19 pm) · 5 replies

Since a few days my meshes and prefabs stay invisible when added to the level until I reload the game. Collision works and the bounds appear when hovering over the invisible object. Creating a prefab from a mesh results in turning it 'invisible'. Adding the same objects can be done in an other or new level without any problems. Level file is growing: 266KB; but not a enourmous level I think. Anybody a clue what might be wrong?
NextNext Thread
PrevPrevious Thread
More from Torque 3D Professional


Torque Owner Nils Eikelenboom
Studio DimSum
#1
02/16/2013 (11:54 pm)
Forgot to add the details:
- T3D 1.2
- Win7 64bit / 8GB
- Open Collada Meshes
- Level file: 266KB
- 654 objects in level

Torque Owner Richard Ranft
Roostertail Games
#2
02/17/2013 (7:51 am)
I would go and undo whatever it was that I did right before this started happening. Might point you to the problem.

Associate Ron Kapaun
3tdstudios.com
#3
02/17/2013 (10:56 am)
Without looking at the models, it sounds like a hierarchy issue. Your objects are getting sorted incorrectly when torque displays them. Check out each model in the shape editor and see what is going on with the levels and lods. Double check the naming conventions as well. For example: if box1 is named, and you import another 'box1' it can cause issues.

Ron

Torque Owner Nils Eikelenboom
Studio DimSum
#4
02/17/2013 (8:37 pm)
Thanks! An hierarchy issue it was!

I'm relying heavily on modular design, so making use of prefabs pretty extensively. I had a gut feeling before that maybe nesting prefabs within prefabs might not be a good idea. After redoing (exploding) all the prefabs -> with now only meshes; the issue was solved.

Torque Owner Nils Eikelenboom
Studio DimSum
#5
02/24/2013 (11:33 pm)
I guess I judged the situation too quick as the same issues returned.

After opening all the meshes in the editor (thanks @Ron) I noticed some detail meshes were not made as a child of start01. After fixing those everything seems to be working fine again. Hopefully fixed for good this time!