Okay, this time I got a warning I get a lot and two errors.
Mungelog: 1: How do I fix the warning
2: What do my errors mean?

Fluffy_the_ic wrote:WARNING[PC_modelmunge msh\parking garage.msh]:parking garage has 3770 vertices and NO COLLISION GEOMETRY (WILL BE SLOW)!
0 Errors 1 Warnings
1: How do I fix the warning

You can't and you don't need to. Just ignore that warning, it means nothing.

What about the errors? Besides, my model doesn't show up in-game.

Did you save your TGA using RLE compression? You need to turn it off when saving.

Those textures are from FragMe! and Caleb's house pack.

And you didn't edit them? If you didn't, try making a tga.option file for it with this code:

okay, how? I've never really tried.

Make a new file with the name m_brickwall1.tga.option
and put in it

To get rid of the error, open the tga file in whatever paint program you use and just do a save as using the same file name, ie just over write it.

It is a weird thing with some textures but doing this will get rid of the error.

As for the warnings, since there is no collision mesh for the model it is building one using normal gemometry as it stated.
The only way to get rid of those is to make a collision msh in XSI for the model.
But since I don't think mshex supports collision geometry the only way is to use XSI version 5 to do the export.

How do you make collisionmesh?

Easiest way, if it is a one object model, duplicate it and rename it collision. Then hide it (H key)
If there is more than one object select all the objects and merge them. Then rename it collision and then hide it.
Don't forget to move the merged mesh bach under the dummyroot cause when it gets created it is outside the dummy.

Okay, there's no more mungelog, but now when I play the map, there's no building.

FragMe! wrote:But since I don't think mshex supports collision geometry the only way is to use XSI version 5 to do the export.

It does, it just won't be able to use primitive collision because of the Crosswalk export. Make sure it has a texture and you're fine. The easiest thing to do is just to duplicate your final mesh, call it collision_polymeshname, put it under the dummyroot and hide it.

MshEx doesn't export collision, it has the game's engine make it for you, which doesn't always work well. That's what the first error is, it's telling you the object has no built in collision mesh, and that the game will have to make it itself, while ingame. Which (I think) will slow things down alittle, seeing as the game must then render the collision in realtime. So it is fixable, but you'd just need to export it through a full version of XSI, one way or another

On some things, the engine can do a good job, and it will work fine, but sometimes not, and you can't really fix it, unless you maybe subdivide your mesh. Cause the engine makes the collision based upon the original model, so the more edges, in general, the better the collision.