It’s kind of hard to judge what’s going on in that video. Yes, I can see your player bouncing off things that aren’t there, but it doesn’t tell much about how your level geometry is laid out.
You can turn on a traverser debugger, and see if that might help you figure out where these collisions are coming from.
base.cTrav.showCollisions (base.render)
Another thing you might try is to distill the problem to its absolute simplest form. Instead of using the full version of your level, why not make a simpler one with a few boxes and a ground plane. Then, if you can re-create the problem there, you can just post that Egg and let someone take a look at it.
Is possible see the collisions on regions, but is possible too see the problem of “where” the collision exists, and see the problem (like the feets dissapear on objects with another angulation).
in the beginning of your movie you see yourself colliding with the window. to prevent that you should create a special collision geometry of your level (1 for the visuals, 1 for the collisions with as few as possible details). only add the “polyset descend” tags and leave out the “keep” for the collision model, dont add any tags to the visual model.
later in the video i think you collide with the terrain, which might not be connected or has a edge somewhere. to fix this i’d try to make your collision sphere smaller so it doesnt touch the ground. the collisionhandlerpusher has flaws when it comes to handling edges (for example a edge of a house), it keeps you stuck or pushes you back.
First, thanks for watch and have patience to try help.
So, I understood your advices, first I’ll change the tag removing keep tag for objects and define the tag to