PolySoup for ALL collision??

#1 Yes you can. You have to be careful with how you place your buildings tho. If their bounding boxes touch, you'll have problems.

#2 Use collision meshes, works just fine. I don't really see the benefit from using accurate/expensive collision - especially if some of the models are likely to be close to each other and polysoup won't like that.

#3 What are the consequences of having objects with polysoup collision on intersect?

I plan to use some models like this, and the player will have to walk upon them. If this does not work as it should, would having the exact same geometry as a collision box in the dts object help? (I'm talking 200-300 polys here, so nothing really complicated, though they do have both concave and convex parts.)

#4 @ Apparatus

I have 200+ models that need collision made. So I was wondering if Polysoup could expedite this process.

None of the buildings will intersect, though the walls and fences that connect them will. Btw, how does Polysoup act with regular collision? Would I have any problems here??

#5 Well, if you want performance you ought to keep the collision calculation as low as possible.

#6 I wonder if there is a constant collision when two stationary objects are colliding. Maybe things could be made faster by checking velocities before checking collision...

#7 What happens when 2 polysoup objects are "close", (not necessarily touching) you will get horrendous lag when you look at those objects. I tend to use collision boxes for things that don't need complicated collisions. For the fence...I'd use a box. For my buildings that people won't get on the roof of, I use a collision box around the parimeter and floor. Otherwise, I use polysoup. It will depend on your buildings and how you want to place them. My biggest suggestion is to use polysoup as spareingly as possible. It's great, but with a lot of polysoup objects in your game, playability may lag.

#8 Speaking of collision;

Would I have to place a box collision over a window or door, in order to see glass or wood shatter FX? I want all statics to give of these kinds of FX when shot at.

Also, can someone point me to a tutorial for adding FX tagging to collision?

Thanks

#9 Depends on what you mean by FX tagging; if you want debris and sound on collision and / or breakable stuff, check the Kaboom pack features.

And that's not something you can do in torque by importing the dts model and add a 'tag' to it. It requires a bit more than that. Even simple box collision needs action from you at modeling time. Only dif/interiors have collision 'out of the box'.

If you are planning to add 200 plus models in your mission / level, LOD is something you should also look at.

#10 @ Apparatus

Yup, already modeled the LODs. I have three LODs per static. Most of my statics are around 500 to 1200 polygons (mostly around 500)

Thanks for that link.

#11

Quote:Would I have to place a box collision over a window or door, in order to see glass or wood shatter FX? I want all statics to give of these kinds of FX when shot at.

That's all controlled in script when the projectile impacts a shape and invokes a script callback and/or causes damage. The Kaboom scripts do that, and more -- I call it damageFX.