I’m here because I am experiencing the exact same issue. My project was upgraded from UE5.2 → UE5.3.
In UE5.2 I was able to cook, package, and test without any issues. I NEVER experienced this before but then when I packaged in UE5.3, the landscape loaded without any collision. If I run the packaged game 10 times, one of those times, the landscape collision will work.
I have no idea why.
At first, I noticed that the landscape component my playerstart was closest to never actually loaded and would give me a weird graphical replacement on the landscape (I am unsure how to describe it) but, after repackaging the game, the landscape appears now but without any collision on this very specific component. (I’m unsure if this issue affects other landscape components in the level)
I followed all the guidelines by Epic regarding world partition and I am following them to the ‘T’.
I’ve had this problem for weeks now.
Today I initially had the issue but then I tried the below to try and force the collision to rebuild itself:
- I simply edited the landscape using the Landscape sculpting tool (On the specific component I was having issues with)
- Changed the Simple collision Mip Level and the Collision Mip Level to something other than ‘0’ then saved and changed it back
- Changed the collision settings to ‘NoCollision’ saving the landscape and then reverting the collision back to the default ‘BlockAll’
- I disabled ‘Generate Overlap Events’
As of right now, my landscape is using the default collision Mip level and works more, but every other time I load the packaged game, the collision still doesn’t work.
I hope this helps you. I will keep watching this forum and will update any other issues I find.