UE5 problem with door frame collision and player

[moohamad]

hello everyone,
i have been working on a door frame using the geometry panel and i have encountered this problem and it frustrated me because i don’t know what its called in english as english is my second language. so this video can explain better

now i have 2 box collision for the frame

as you can see the collision can’t effect the movement of the player.

and i checked the capsule component radius and its at normal size and cant effect the movement

i am using UE5.0.3

so at last, any help would be appreciated

[ClockworkOcean]

Are you talking about that ‘jittery’ movement?

You don’t need any collision on the door, the wall will be fine, I think you’ll find

[moohamad]

yeah thats what i mean, and i removed the collision but the problem isn’t fixed.

[ClockworkOcean]

Try looking at the scene in ‘player collision’ mode

[moohamad]

i added collision to the wall because i convert it to a static mesh and removed the collision from the door frame
but the problem isn’t fixed as u can see the collision looks fine to me

[ClockworkOcean]

If you actually take an instance of the pawn and put it in the doorway, does the collision capsule fit?

It looks a little narrow to me…

[moohamad]

i already reduced the size of the capsule radius and it didn’t work.

[ClockworkOcean]

I really can’t tell from here.

Just take the walls away, can you walk across that piece of floor?

Then put just one wall back, etc.

That’s all I can say…

[SupportiveEntity]

Hey there @moohamad! Welcome back to the community! I agree with Clockwork, if you remove the side walls and if the player still stumbles on that spot it’s likely clipping the geometry under the ground there.

[moohamad]

i will try to remove the side walls
thanks for your help anyway, i appreciate it

[moohamad]

after 2 days of looking for a fix for the problem i finally found out what is causing the problem and fixed it.

i simply unticked the use pawn control rotation from the camera properties and ticked it from the spring arm properties instead and the problem got fixed

[ClockworkOcean]

Ah, it looked like first person…