XSI exporter question
Posted: Fri Jun 10, 2005 7:51 pm
My first post.....
And as a long-time user of various 3D tools and APIs (but not a strong C++ programmer), I just want to say that I'm very impressed with how quickly I was able to get up and running with OGRE in general, create an XSI to OGRE pipeline, and get tangible results. A testimonial to OGRE's O-O design and how well you guys have abstracted the low-level details. Fantastic job!
However...
It appears as if the XSI exporter does not support exporting instances (I don't see anything in the documentation to say that it does, but nothing to say that it doesn't either).
If I have a mesh object in XSI and create a row of them using instancing, then export, I only get the original object in OGRE.
So I'm assuming that the design intent is for us to do the instancing in OGRE, by creating additional entities through functions to build rows, grids etc.
IWBNI instancing was supported, as the tools to create reasonably complex arrays of objects already exist in the modeling packages. We are working with some complex arrays of scaffolding, ibeams, etc. in a construction scenario, and will probably have numerous combinations of these. These typically use instancing since every "unit" is identical except for location. So it would be a bit of a pain to have to create these on the fly, as opposed to bringing in "library" objects.
Thanks.
And as a long-time user of various 3D tools and APIs (but not a strong C++ programmer), I just want to say that I'm very impressed with how quickly I was able to get up and running with OGRE in general, create an XSI to OGRE pipeline, and get tangible results. A testimonial to OGRE's O-O design and how well you guys have abstracted the low-level details. Fantastic job!
However...
It appears as if the XSI exporter does not support exporting instances (I don't see anything in the documentation to say that it does, but nothing to say that it doesn't either).
If I have a mesh object in XSI and create a row of them using instancing, then export, I only get the original object in OGRE.
So I'm assuming that the design intent is for us to do the instancing in OGRE, by creating additional entities through functions to build rows, grids etc.
IWBNI instancing was supported, as the tools to create reasonably complex arrays of objects already exist in the modeling packages. We are working with some complex arrays of scaffolding, ibeams, etc. in a construction scenario, and will probably have numerous combinations of these. These typically use instancing since every "unit" is identical except for location. So it would be a bit of a pain to have to create these on the fly, as opposed to bringing in "library" objects.
Thanks.