Ingame, I can go/fall through my building model at some parts of the model. After I saw this, I went back to XSI and added collision. No change. Is there an explaination for this?
Also, I don't see my model being munged In Visual Munge for some reason...would this add to the problem?
I have never seen this happen before for my building models, which I've made about three of.
I'll post a picture If needed.
Thanks.

Odd question I know: Is your model triangulated? If not then do so and test.

Triangulated with the export?

Uhm. I mean triangulate the model before exporting it yes. You don't want any quads. Quads can mess up collision.

Hmm..I don't get It still. Do you mean," Convert Meshes To Triangles" In the export box? Because I already selected that option..

Check to see if everything was named right. The method in which you triangulate doesn't matter, as long as you do it.

EDIT: In fact, post the name of the collision model, unless you have already changed it.

Quads are fine. What are you exporting to msh with, Pandemic Tools or MshEx?
When changes don't take effect usually a clean(auto or manual) is needed.
You may need a msh.option file with -donotmergecollision to preserve your accurate collision during the munge process.

AceMastermind wrote:Quads are fine. What are you exporting to msh with, Pandemic Tools or MshEx?
When changes don't take effect usually a clean(auto or manual) is needed.
You may need a msh.option file with -donotmergecollision to preserve your accurate collision during the munge process.

MshEx. Also, I tried -donotmergecollision. Also, I tried a clean, nothing worked.
@The Nasal Abyss: The name of the collision model was just "collision" According to "How to get your mesh into SWBF2" By Vyse.
One more thing, I'm using this prop for the distroyed part of a distructable building. Does this matter?

Cerfon Rournes wrote:

AceMastermind wrote:... What are you exporting to msh with, Pandemic Tools or MshEx? ...

MshEx...

You should have mentioned this in your first post, the setup procedure is different than if you were using the Pandemic Tools to export, you're also limited to what MshEx was programmed to handle. I do remember there being a topic discussing collision exported with MshEx though.

AceMastermind wrote:

Cerfon Rournes wrote:

AceMastermind wrote:... What are you exporting to msh with, Pandemic Tools or MshEx? ...

MshEx...

You should have mentioned this in your first post, the setup procedure is different than if you were using the Pandemic Tools to export, you're also limited to what MshEx was programmed to handle. I do remember there being a topic discussing collision exported with MshEx though.

The thing Is, as I said In the first post, I have been doing everything the same for about 3 models now, with no problems.
Anyway, I'll try to find this topic you are talking about.

AceMastermind wrote:Quads are fine.

Not to argue with the expert, but I have had issues with quads and collision, the solution was to convert to tris. But I guess it isn't his issue anyway.

I've been searching for an answer, and I have a question. How do you name your collision? Vyse's Tut says name It this: collision. In some topics I found, some people named It: collision_.
Which way Is correct?

Cerfon Rournes wrote:

AceMastermind wrote:...I do remember there being a topic discussing collision exported with MshEx though.

...I'll try to find this topic you are talking about.

forums/viewtopic.php?f=36&t=15278&hilit=collision+mshex


EDIT

Cerfon Rournes wrote:...How do you name your collision?...

Read Appendix C in the art_guide.doc of the BF2_modtools documentation, that section will tell you everything you need to know about collision in SWBF2.

Hmm. I'll try what you said..

AceMastermind wrote:Ah, so as long as you keep the collision unhidden(?) on export then it'll work.

EDIT
Did not work. Even tried It with -donotmergecollision. I'll try a manual clean.
EDIT2 Ok, I did name the collision correctly then.
EDIT3
.....Aaand the manual clean didn't work. What am I missing here?..
EDIT4..
Wow, can't believe I missed this.. I'll try this now.
And that did not work. Anyone have ideas?

If you don't mind, you could PM me the XSI scene and I could check it out.

MshEx isn't capable of preserving primitive properties as far as I know which means you can't use collision primitives with this exporting method, but collision meshes will export according to the link I posted earlier.
If all else fails you can always use Foundation & the Pandemic Tools, they are free and available to everyone.

AceMastermind wrote:MshEx isn't capable of preserving primitive properties as far as I know which means you can't use collision primitives with this exporting method, but collision meshes will export according to the link I posted earlier.
If all else fails you can always use Foundation & the Pandemic Tools, they are free and available to everyone.

I can't use those, because I used up my trials already.
About that topic, what exactly do I change? It's not that clear...
@The Nasal Abyss: I might just take you up on that.

if you are asking what the difference between primtiives and collisionmeshs is:

Primitives work perfect because battlefront doesnt use the actual model of them as collision but the real primitive, that makes the collision easier to calculate. they are called"p_-types-whatever" its optional to specify the collisiontypes.

Collisionmeshes are handlyed as normal polymeshes. because battlefront has to calculate if something touches a polygon/edges/point of the collisionmesh, the calculation is more complex and "not always"correct. as far as i know games have problems especially with concave surfaces and holes. collisionmehes are called "collision_-types-whatever" types are optional.

when visualmunge/battlefront doesnt recognize the collision properly, make it more primitive. use more seperate parts.
collisionmeshes that have simple shapes like primitives should work nearly as well as real primitives.

i hope that clears up up any tentative questions about collisions

Cerfon Rournes wrote:I can't use those, because I used up my trials already.
...

You should get into the habit of monitoring software installations so you can remove all traces of the software when uninstalling. I don't like traces of uninstalled software remaining on my machine, when I uninstall something I expect it to be completely gone which is why I monitor the installation of any software I install.

AceMastermind wrote:

Cerfon Rournes wrote:I can't use those, because I used up my trials already.
...

You should get into the habit of monitoring software installations so you can remove all traces of the software when uninstalling. I don't like traces of uninstalled software remaining on my machine, when I uninstall something I expect it to be completely gone which is why I monitor the installation of any software I install.

Yeah, I should look into that more..
Do you know how to remove the traces after you uninstall it?
Backontopic
Solved. Darth D.U.C.K explained some things over xfire, and the problem has been fixed.
I think one of the problems I had was I did not correctly name my collision. Before, I named it,'collision'. This time, I made a lower poly version of the model, and named It "collision_(name here)". After that, it worked.