-= Gametoast.com =-

i have the terraincutter named terraincutter, it is a child to my mesh underbunk. Which is a child to ms3dsceenroot and the terrain cutter works in zeroeditor, but not in game.

can someone plz help, i exported via meshex

hmm, are ypou shure, that mshex can handle terraincutters?#
everything seems to be ok

Ok, MshEx will NOT support anything other then your visual mesh, and nulls.

Not Collision, Shadowvolume, Lowres, or terrain cutters.

maby if i give the terraincutter 100% clear texture?

do u think that will work?

No, it can't be helped, you see the way MshEx works at the moment is it merges all visible meshes, so nothing's going to fix that. You'll just have to get your model exported the old fasioned way, by asking someone else to do it.

Which is a child to ms3dsceenroot and the terrain cutter works in zeroeditor, but not in game.

How do you know it works in ZE, did you see the pink box? Terraincutters btw do not have to get hidden before export as a matter of fact it is better if it isn't, hiding it prevents it from being seen in ZE.

But as Caleb says if meshex doesn't support it and you can't find anyone to export your model you could try and use the terraincutters I made that are in the released assets topic, just scale an appropriate on to your needs.

MshEx DOES support terrain cutters, I've used it for 6 models so far (with terrain cutters..). Although, with all of mine, I had it as a child of dummyroot, or whatever your parent of all parent nulls is. I'd try that, because unless there's something else wrong with your model, I'm 100 percent sure MshEx works with terrain cutters.

Oh also, I've found (at least with MshEx) the terrain cutter should NOT be hidden. One tut I read said it should be, and it crashed my game... it shouldn't matter what the texture is, I never gave mine textures.

Funny that people say that collision and all that don't work with the tool. It sure works for me...

YouJediJunkie wrote:Funny that people say that collision and all that don't work with the tool. It sure works for me...

We say that because it doesn't. The game munges its own collision geometry and is ignoring any sort of collision primitives/meshes you gave.

PROOF that collision works in mshex and also terraincutter, but terraincutter isnt working in my other obj for some reson

here u see my collision geometry in my obj that i made for my jouney to the center of the earth map(not finished). this obj is the thin rock formed in the magma tube that u could fall through, note: not put to gether exacly as exported properly aranged: working in zeroeditor: and me falling through ingame:

The game automatically makes collision geometry, its just like a huge box, not much detail to it

mshex will do anything that is not hidden, a terraincutter works best if it is not hidden as then you can see it in ZE.
A collision that is unhidden and is just the result of a merge of all meshes (including merge UVs) or a duplicate of a mesh but still having textures may show up in game as a collision. Easy way to tell is remove all textures and UVs from the collision mesh, don't hide it and then try exporting it. If you model shows up in game or ZE with an apparent lack of texture then mshex may have exported it. If it shows up textured then mshex ignored the collision and munge created whatever collison you have.

if it had merged all objects, i wouldent have a terraincutter on that object and i also wouldent have been a ble to fall through, it is in fact that it worked as my above post shows, i think rep would know best, after all, he created the program

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

I see it, take a look at the screen shot with the highlighted mesh named collision. The mesh shown has sections missing from the middle. If MeshEx didnt export collisions, he wouldnt be able to fall through the areas where there are no collision as he is doing in the las pic where he's under the map. If the collision he made wasn't exported, the engine would just make a cylindrical collision. The only other explanation for falling through would be a mesh option command.

exactly!!!
my option is -donotmergecollisions
but i dont get why my terrain cutter dosnt work in my other object