Collision bug on trees

#1 Uncheck allow player step in the editor. This will disable the 'tree climbing' thing.

Ron

#2 Thanks. It was a little confusing, cause the tree was in the forest editor and not in a static shape, where you can make this setting.

#3 Yep, I know it's something that will get fixed....I will add it to my list of 'sorta bugs'

Ron

#4 Ah, but the trees are all shapes before they are added to the forest....

And they should not have allow player step enabled by default. Funny, though.

#5 Just discovered some trees where this still works, even "allow player step" is unchecked also reimported the trees as shapes and unchecked again and deleted chached files and loaded again, but still it is there.

#6 Is anyone working on this or should I commit this as a bug? First the uncheck allow player step seemed to work, but now, maybe since the new version of Torque I cannot disable the tree climb thing. I have no idea where this information is stored, already tried reimporting the dae-files, unchecked player step and reloading the chached filesm, but no result.

#7 Are you using the stock tree? I'm not seen this in stock MIT 2.0 master with stock tree or my own models. Climbing up objects is based on player datablock RunSurfaceAngle value.

Also if you're getting stuck on something it's generally down to a bad collision mesh. (eg: ending in a point - that can skewer your player)

#8 It is on every tree and there is nothing changed in the player data, even 90 degrees you can run up. Maybe most people never notice, that you can run up trees, but if you try carefully it works.

#9 If you can run up a 90 degree tree then you can run up a wall.

Doesn't happen on my box, never has since that time in beta when it did.

#10 Here is a picture story:

Setup: default Torque and default tree

Player facing the tree from the y-axis (on the default tree it works only on the y-axis, it is different on every shape, some work better some not):

Running up:

And finally on top of the tree (could be used as a exploit I would also recommend to never use cylinders as collision-mesh on trees, since you always can stand on the top, I prefer to use spikes):

#11

Quote:
on the default tree it works only on the y-axis

A-ha! Yep, got it. That is ... odd.

Looking at the collision mesh it appears that the Y-axis is at an edge of the octagonal shape of the mesh - though not sure if that has anything to do with it or not.

#12 Not new at all. Seen this here in my game since last year. From Torque 3D 1.2 and untill now this has been a issue.

Just cancel any collision with the tree or make bounding boxes should solve this issue.

#13 Just to point out, on my own custom models I can find that the player attempts the step-up from one angle but fails - unlike in the stock tree. Happens on the edge of hexagon collision mesh like with the stock tree colmesh, doesn't seem to happen on colBox quadragon colmesh.

#14 I also have some trees where the player can't step up, but this can't be the solution to build every tree so this error does not occur, since some trees need more detailed collision and not a box or no collision at all.

More polygons also help. On the default tree, the edge where you can step up goes from ground to top, if you split it into more, then the player will more likely fail, but also increases polygon count.

#15 i can't find this player step option

#16 In shape properties, under where you can chose collision type.

#17 Hmm you mean in forest editor? (please tell me i don't have to place all my trees manually to use this step option)

#18 Yeah that happens; even if the playerdata is setup that you can't walk on a steep slope like that. Changing stepheight also doesn't change it; you can run op to trees of 10m high -like a Chinese warrior in a Bamboo forest- if you don't fix it...

- make the collision mesh conical, with the wider end on top
- make it high enough to the player can't jump on it
(or make the shape like a bullet so the player glides off)
- use at least 5 sides so the player can run smooth when colliding
- for thin trunks; use a wider mesh, at least 0,30 units (30 cm)
- when using wider mesh, you might want to turn off the decals

Example:

#19 If you're using trees via the ForestEditor/Painter I'd suggest a straight sided box (eg: colBox-1) - keeps collision simple but not pixel perfect, prevents run/climb up and forests can't have decals on them.

Even on my own custom hexagon colMesh collision (with straight sides) I don't actually get run/climb up, but I do see the step attempt in the player model - it just fails. Always from Y axis only on a leading edge.

Still, annoying.

#20 test