Page 1 of 1
Model that crashes XSI on export
Posted: Tue Jun 14, 2005 11:27 pm
by jemsio
Hi --
I have a model that continually crashes XSI when I try and export it. I have both frozen the modeling and triangulated it before export, but nothing helps. While I'm sure we will probably need to build this model differently, it would be helpful to know what the problem is. FYI -- the model is legal as far as XSI is concerned, and renders properly with both mental ray and OGL.
Sinbad -- I can email the model to you if you like, in order to help you debug the problem (it's a small file).
Posted: Wed Jun 15, 2005 5:30 pm
by sinbad
If you're using the 1.0.1c exporter, please download the 1.0.2 version, there was a bug in the material export in 1.0.1c which would cause a crash if the texture file couldn't be found.
Posted: Thu Jun 16, 2005 5:41 pm
by jemsio
I downloaded the 1.0.2 version as I was still running 1.0.1c, uninstalled the old version and installed the new one. However the behavior is the same.
I did notice that the Change Log in the newly-installed exporter doc does not mention 1.0.2, and that the OGREXSIExporter.log file generated still references 1.0.1c. I've included the log below, if that helps:
12:25:54: OGRE Exporter Version 1.0.1c
12:26:27: Creating resource group General
12:26:27: Registering ResourceManager for type Mesh
12:26:27: Registering ResourceManager for type Skeleton
12:26:27: Registering ResourceManager for type Material
12:26:27: ** Begin OGRE Mesh Export **
12:26:27: -- Traversing P1Dirt
12:26:27: -- Queueing P1Dirt
12:26:51: Unregistering ResourceManager for type Material
12:26:51: Unregistering ResourceManager for type Skeleton
12:26:51: Unregistering ResourceManager for type Mesh
The OgreXSIExporter.dll file that is placed into Softimage\XSI_4.2\Application\Plugins has a date of 6/2/2005 at 9:43pm -- is that the correct version?
Thanks.
Posted: Sat Jun 18, 2005 5:54 pm
by Baldrake
FWIW, we have the same behaviour with the version we use. It's definitely a change from the original 1.0.1c, so I assume Sinbad just forgot to update the version number.
Posted: Sat Jun 18, 2005 9:19 pm
by sinbad
The log looks like it's completed. I'll need an example, all the meshes I try work fine.
Posted: Wed Jun 22, 2005 10:01 pm
by sinbad
For the benefit of others, the problem with this mesh is that it had 13 UV sets. Reducing this solved the problem, but I'll try to figure out why it crashed rather than telling you nicely.
Posted: Wed Jun 29, 2005 6:00 am
by Slicky
I seem to have a simple model that crashes XSI on export. I think it might be the texture because it wasn't textured before. I applied a simple one pass texture. The log is:
18:13:15: OGRE Exporter Version 1.0.1
18:13:32: Creating resource group General
18:13:32: Registering ResourceManager for type Mesh
18:13:32: Registering ResourceManager for type Skeleton
18:13:32: ** Begin OGRE Mesh Export **
18:13:32: -- Traversing Mine
18:13:32: -- Queueing Mine
18:13:32: Calculating edge lists
18:13:32: MeshSerializer writing mesh data to C:\Files\VCNet\Tan Four\Media\Models\MineProx.mesh...
18:13:32: File header written.
18:13:32: Writing mesh data...
18:13:32: Writing submesh...
18:13:32: Submesh exported.
18:13:32: Exporting bounds information....
18:13:32: Bounds information exported.
18:13:32: Exporting submesh name table...
18:13:32: Submesh name table exported.
18:13:32: Exporting edge lists...
18:13:32: Edge lists exported
18:13:32: Mesh data exported.
18:13:32: MeshSerializer export successful.
18:13:32: ** OGRE Mesh Export Complete **
18:13:32: Unregistering ResourceManager for type Skeleton
18:13:32: Unregistering ResourceManager for type Mesh
That might not be enough info for you but like I said it might be the texture.
Posted: Wed Jun 29, 2005 1:29 pm
by sinbad
Check the number of UV sets (open the clusters section of the polymesh and open the Texture_Coords_AUTO section - if there are lots you need to sort it out), and make sure the texture you're referencing is there.
In the CVS version you get a friendlier error for the former, and the latter was fixed in the 1.0.1c version.