Advanced mesh collision help.

..Hi,

I hate to ask such a common question but i have done everything i can think of and i was wondering if someone a little more familiar with torque 3D could lend me a hand. Basicly, my mesh won't collide with my vehicle and I'm going a bit mental trying to make it work.

What has been tried so far:

Visible mesh collision
Using a custom "collision mesh" which was set up with the correct hierarchy and displayed as working but did not actually do anything.
Making the model into a "shell" so it has 2 sides and is not a single plain.
quiting the level after changing collision settings then reloading.

Any ideas would be really really appreciated. Model attached is below (in .DAE form exported from 3DS max).

 

Re: Mesh Collision won't work (3DS max -> BeamNG)

It's because you don't respect the hierarchy. You must have a helper, parent of your object and a collmesh etc. I don't remember how much objects you need in your DAE, open an object like a beamng's tree to check what you need and the order.

 

Need help Setting up collision meshes

Ok, I have sorted out the hierarchy and am sure the collision mesh was working as it was displayed as a purple wireframe when i toggled visible collison meshes. Despite this my car still falls right through the mesh. Perhaps theres something wrong with the model? It is made from a single plane which has been edited however so are most mesh terrains. Any ideas?

 

If you've made a collision mesh for this object, you should be selecting "collision mesh" in the collision category, not "visible mesh". I'm not familiar with Blender, but make sure the all the objects are set to 0,0,0 pivot point and reset the transforms of all the objects.

 

Tried both collision mesh was selected whilst i was tryng with the custom one and vica versa. axis reset could'd be an idea though.
----update----
Axis reset did nothing either.

Heres how it looked with the collision mesh (ignore the polyflow, i had tried quadifying it aswell to see if it was something to do with the polycount)

 

That could be it, I'm trying it now. Thanks for your time

----------update-----------

ok, the hierarchy now looks like this:


still no luck

I reckon it will be something really simple that I've forgotten, could something like the normals or the way i've modelled it cause any problems?

Turns out it works on the normal torque 3D without BeamNG.


what is different about BeamNG collision to normal torque 3D collision i wonder.

 

Torque3d and BeamNG do collisions quiet differently i think. The only reason i say is because when i was using Torqe3d before BeamNG was launched to practice it automatically just used the visible mesh and everything worked perfectly. But it was absolute hell getting the mesh into BeamNG, thankfully some people on the forums helped out. I will have a play with the file and see if i can do anything.

EDIT:
Well, i tried importing the file but sadly my user account is not the same as yours and i do not have the correct files located in a folder on my desktop I also happen to lack the skills or patience to manually edit the textures out using notepad++ . Google leads me to believe this is just a 3dsmax and blender compatibility issue (not your fault). My general plan was to take a file that i know works and then delete my mesh's from it and put yours in its place so you could have a working file.

This may help you: Help-with-map-object-collisions
You should be able to download the file that NkosiKarbul posted and delete my objects from it and place your own in their place with the same object names.

Hopefully some of this unorganized rambling may have helped you.

 

Thanks for trying that idea, i was speaking to someone else having the problem and it seems that is probably the right way to do it. they got theirs to work by exporting it to sketchup then into torque and for some reason that made visible collison work. Ill have a read of that thread aswell
Id thank you but i hit the limit today lol.

 

Possibly the normals are flipped the wrong way. If they are wrong way, no collision. In poly select mode, select the polys in question and hit button "flip".

I've exported tons of models with no issues from max.

Also, what exporter are you using? the built in .dae exporter with max is no good.

You need to use this exporter (OpenCOLLADA): https://github.com/KhronosGroup/OpenCOLLADA/wiki/OpenCOLLADA-Tools

 

I actually solved this by creating a "helper" object then linking all the other objects to it with the correct names to make them collision meshes by default in torque 3D.if anyone comes accros iasues with this PM me as i have it figured out.

Sent from my HTC One X+ using Tapatalk