odd collision detection in editor

[silent skies]

Hi,

While working on my latest map I came across an oddity. One of the objects from my large imported PNG looks like this:



(I pulled out the red wireframe from behind the image to show its shape)

The poly for the tree is one single object. The problem is, when testing in-game, planes will collide with the square-shaped outline of the object (what is seen highlighted as the orange/yellow line in the editor ... but this boundary doesn't show up as a red line in the editor.

... Help? :'(

[lamster]

Please save that map file and the image file used to create that collision box.

To fix it you can probably right click -> edit hull and remove some of the internal complexity. Alternatively you could delete the generated hull, then make a new (invisible) polygon, and trace the general outline of the tree.

[silent skies]

Please save that map file and the image file used to create that collision box.

I am assuming that is lam-speak for "I want to poke this problem with a stick."

Well, here ya go. ZIP file with map + png.

To fix it you can probably right click -> edit hull and remove some of the internal complexity. Alternatively you could delete the generated hull, then make a new (invisible) polygon, and trace the general outline of the tree.

Okay, will do.

[Mandrad]

I always erase all automaticaly generated poligons.

[mlopes]

Originally Posted by Mandrad

I always erase all automaticaly generated poligons.

Any special reason? I had problems with auto-generated polygons before (ex. a triangle on gymnasium where the ball would go through it but planes won't, in spite that the polygon was totally closed), but I always assumed that manually would be even worse...

[Mandrad]

Automatic polys are far from perfect and i prefer make'em from scratch than editing it. This is especialy important in ball cussions ofcourse.
I also like to have my files as clean as possible, reason why i usualy erase all unnecessary paths.

As an example, in underpark 1st version, i had all chains as separate objects, loads of small shapes were generated and i dont even wanted chains to be colidable.

*Erasing all these unnecessary paths its what takes the most time for me when editing

I had problems with collisions in maps like revpark. Not sure if it was due to the size of the shapes or the way they relate its position to eachother, but i had to break the initial inside and outside of the track shapes into several colision shapes.

EDIT:
Would be nice if Karlam checked EDIT 1 file in revpark thread to see the collision path bug i mentioned.

[Pieface]

Adding to this, I'm in the process of making a tbd map and the editor has trouble adding collision outlines to feathered objects such as ones using the Photoshop glow filter. Looks like I'm gonna have to add all them manually...