I have problems when importing a new object mesh using the MS3DASCII importer.

I have v 48c, but this same problem has been happening with the earlier versions, ever since the bounding-box feature was added.

The mesh imports fine, all seems to be working - but the game will crash as soon as I go to the catalog section that my new object is in.

If I now export this mesh as .obj, and use the MeshTool to turn it into a GMDC file and replace it in SimPE, the object will work correctly - no crash in the game. Also the filesize of the whole .package becomes a little smaller.

These are all non-boned objects.

Here is what I am doing, maybe I am not doing this right?

MilkShape version is 1.7.5
Simpe v .48c - I am using Classic Interface for this.

1} Export original mesh as .MS3DASCII, set to scale = 1, Order XZY
2} Import into MilkShape, create new mesh keeping all original group names and in the same order as they were originally
3} Export finished mesh as MS3DASCII file
4} In Simpe, go to GMDC - plugin view and checkmark all mesh groups
5} Make sure Order is still XZY
6} Import the new MS3DASCII file
7} Change all groups from "Add" to "Replace", and make sure they are all target to the same named group - other settings I leave alone
8} Import, Commit, and save the file

I also tried using "Update" instead of "Replace" for all the groups but that produces nothing in the preview window in SimPE...

I can provide a non-working object if you want to look

The solution might be simple. After the import, go to the "Model" Tab of the GMDC Plugin, and clear the "Bounding Mesh" Section.

Now i don't know why this is happening, since the importer is clearing the BoundingMesh, when it detects that a Joint was defined for that Mesh.

Yes, I know I could export/import objects with no bones using the .obj format, or Wes H's plugins.

I would prefer using the .ms3dascii format though because it has advantages over either of the alternative methods, even with non-boned objects.

Also I think it is important to test, and try to "break", new features in SimPE to help out with the development of this excellent tool.

I didn't try checking the "Remove All Groups" checkbox, I'm not really sure what that does? Maybe I should checkmark that box, and leave all groups set to "Add" ?

I haven't found an explaination anywhere what all these import options mean, so I am just guessing at the proper use of them.

I did do an experiment, I cloned a simple Maxis end table (no bones) with Object Workshop, and found that the MS3D ASCII exporter produces a very much different file than MilkShape does.

You can download here the files:

http://theblarneystone.org/TableTest.htm

I exported the GMDC as an .obj file, and also as a .MS3D ASCII file.

I then imported the .MS3D ASCII file into MilkShape (MilkShape reports errors when opening, but does import the mesh)

I immediately exported this as a .MS3DASCII file, no editing at all.

If you compare both the MS3D ASCII files, you will find them very different.

The one exported by SimPE lists 3 bones even though there are none in the object, plus the overall format of the file is different.

Also, SimPE is unable to import this MS3D ASCII file it exported, only if I run it through MilkShape first will SimPE import it.

Perhaps the problem lies in these differences, maybe it is causing MilkShape to do something strange to the file because of the import errors?

Did you try the bit with deleting the Bounding Mesh Section on the Model Tab?

Yes, I forgot to say that I did try that.

I imported the .ms3dascii file that had gone through MilkShape, then went to the Model tab and clicked on "Clear" in the Bounding Mesh Control section.

All the information disappeared, I saved the file and tested in the game.

Still the game crashed when going to that catalog section.

Then I exported this new GMDC as .obj, and used the MeshTool to make it into a new GMDC with bounding box. Now there is again information in the Bounding Mesh Control section. I left this alone.

I replaced this into SimPE, and saved again. This time the .package file becomes a little bit larger.

And now it works in the game, no crashing problem.

I don't really know if this is caused by the bounding box at all, I mean that I found this to happen at the same time that the bounding mesh feature was added to the import. It may not be related at all.

It was just a guess, since the bounding Box caused a similar problem some days ago.