-= Gametoast.com =-

I've just completed my first BF2 flyer but there is one problem:
What have I done wrong with the collision?

I followed the tutorial in my last topic
•ANDEWEGET's basic video tutorials
But the collision part doesn't seem to be working.
Does anyone know what I could have done to cause this?
It might also be something I didn't change in the odf (I used the
tiefighter odf and changed the geometry and other
random lines I thought might make it work):

How do you have your collision set up? Are you using collision polymshs or collision primitives? Could you post images of your flyer's hierarchy?

I'm using a collision polymsh here's the hierarchy:

Ah, I see the issue. You're using collision polymshs; anything that moves, i.e., vehicles, turrets, etc., have to use collision primitives. Refer to this thread: http://www.gametoast.com/forums/viewtop ... 02#p478702

This is precisely why I recommended you examine the TIE Fighter hierarchy in U3D or XSI. You can see directly how objects are named and how they were used, then you apply that knowledge to your own project.

Unfortunately I still can't get it to work but I don't know why.
Here's the new hierarchy and a picture of the collision primitives: If you watched the video you might have noticed that the center (for some reason)
actually has collision which just confuses me even more.
Also here's the .OPTION of the msh (Copied and renamed tie bomber .OPTION): I'm also wondering if I forgot something in the odf or set it up wrong
(because I didn't really set it up).

If you're using the ZETools exporter you have to name your models according to the type of primitive they are.
Example:
cube primitive: p_-svbot-cube_body1
cylinder primitive: p_-svb-cyl_body2
sphere primitive: p_-bot-sphere_body3

Tried it but it seems as if the collision primitives are pushing against each other
(or the q-wing itself) resulting in a floating vehicle and unorganized primitives.
I have no idea what could cause this (do I have to freeze transforms?). Iv'e also
tried no collision primitives and removed "-nocollision" from the OPTION file which
worked but I could push my way into the cockpit. Any ideas?

in the .option file try adding -donotmergecollisions
it may or may not have an s on the end

also if you run bfmodtools and go into the menus you can turn on "render collisions" then if you do free cam you can see what the collision meshes look like on your model.

Thanks I'll try it out.
Do I need this line in the .OPTION as well: -nocollsion ?

Marth8880 wrote:Ah, I see the issue. You're using collision polymshs; anything that moves, i.e., vehicles, turrets, etc., have to use collision primitives. Refer to this thread: http://www.gametoast.com/forums/viewtop ... 02#p478702

thats wrong. i named the collision mesh like this collision_-svbotf-anyname

works fine

Not according to Pandemic, the game's developers, but whatever you say...

LEO wrote:

Marth8880 wrote:Ah, I see the issue. You're using collision polymshs; anything that moves, i.e., vehicles, turrets, etc., have to use collision primitives. Refer to this thread: http://www.gametoast.com/forums/viewtop ... 02#p478702

thats wrong. i named the collision mesh like this collision_-svbotf-anyname

works fine

Before saying that "its wrong" make sure you read the whole topic and
see if it has already been corrected:

ANDEWEGET wrote:If you're using the ZETools exporter you have to name your models according to the type of primitive they are.
Example:
cube primitive: p_-svbot-cube_body1
cylinder primitive: p_-svb-cyl_body2
sphere primitive: p_-bot-sphere_body3

same as yours.

no thats not the same as mine. this is using primitves. but its correct because my way is not workin (to err is humanly)

Did you scale any of the primitives? It explains it quite simply in the docs about collision primitives, if you need to change their size you can only scale cubes and leave the size at 8. Spheres and cylinders cannot be scaled, size must be changed via the primitive pop up box, you cannot change the subdivisions in U or V, you cannot edit any secondary shape components, i.e. vertex's, edges or polygons and you cannot freeze the operator stack essentially the geometry operator must be the ONLY node under the primitive.

Lastly the collision primitive should be child to the mesh that it affects and not under the root node (dummyroot).

Read

https://sites.google.com/site/swbf2modt ... Primitives

I wish I didn't have to revive this but.......... Its happening all over again but I don't understand why. Here's a video showing that there's no collision geometry:
Click

Here's the set up in XSI:

Any ideas?

I've never ever gotten cube collision primitives to work properly - I think it's a problem with the ZETools. Use cylinders or something else instead.

Cylinders worked, thanks Marth. Why don't the cubes?

Because of Zero Logic™!
For all your Zero engine needs, it's Zero Logic™!

We don't really know.

Nedarb7 wrote:Cylinders worked, thanks Marth. Why don't the cubes?

Pretty sure you used the scale tool on that cube. Any scaling that's done on an object through its properties works fine, but once you use the sidebar things get wonky. It's been a while since I've done a hover, though, so I could just be making this up.