Importing whole scene objects through one collada file
by Ilusis · in Torque 3D Professional · 01/21/2010 (2:47 pm) · 0 replies
Hi everyone!
I'm testing the collada .dae file as a way to import a whole scene directly to Torque. I know that there are some cases where using multiple dts or dae files is more flexible, but what the art we are making come entirely from a 3d modelling program and it would be the pipeline would be much faster if all the hundred of objects where exported by only one file.
Fortunately (I guess) it worked, even with the collision meshes and with the right materials. Our team is planning to use this method from now on, but first I have some questions:
The collada importing system from torque 3D was designed to imported whole scenes throught a dae file?
This method would cause some loss in performarce or the engine was already made to work with this system (like having some scene managing system, or managing the objects and subobjects separately)?
Thanks in advance
I'm testing the collada .dae file as a way to import a whole scene directly to Torque. I know that there are some cases where using multiple dts or dae files is more flexible, but what the art we are making come entirely from a 3d modelling program and it would be the pipeline would be much faster if all the hundred of objects where exported by only one file.
Fortunately (I guess) it worked, even with the collision meshes and with the right materials. Our team is planning to use this method from now on, but first I have some questions:
The collada importing system from torque 3D was designed to imported whole scenes throught a dae file?
This method would cause some loss in performarce or the engine was already made to work with this system (like having some scene managing system, or managing the objects and subobjects separately)?
Thanks in advance
