I’ve copied a project from UE 4.11 to UE 4.14 Preview 1, and the collisions happen to be all broken in one of the levels: I can’t even have the player standing on any mesh.
I cannot - nor I have the time to - pinpoint the exact cause of the problem, but:
When I open the level for the first time, the following message is shown:
“Some issues were detected with
BSP/Volume geomtry in the loaded level
or one of its sub-levels. This is due
to a fault in previous versions of the
editor which has now been fixed, not
user error: You can choose to correct
these issues by rebuilding the
geometry now if you wish.”
Whether I allow the rebuild of the geometry or not, the problem isn’t solved anyway. I don’t really know if this is related.
If I remove every actor from the level, then the collisions start working properly again. Considering point 1, I tried removing all the BSP’s only, but that din’t work out.
My team is willing to upgrade to UE 4.14 as soon as it is available, so I really care about this anomaly
Thank you for your time.
P.S. The same project copied into UE 4.13 didn’t show the issue.
I’m not sure right off why you are seeing this error. There wasn’t any changes to BSPs in 4.14 that I’m aware of.
I attempted to reproduce this but I couldn’t get the error. I tested it by creating a 3rd Person template project > adding all types of BSP geometry of various sizes > then converting the project to 4.14 P1.
When you say all geometry is broken, do you mean only BSP or is all static meshes affected as well?
I know you said you don’t have a ton of time to spend on this, but would you be able to send a small test project that has the issue? Upload it here if it’s smaller than 5 mbs or you can PM me a link to download it directly over the Forums.
Well, while building a project to send you I stumbled across the cause of the issue: a faulty mesh. It had an enormously low value of location z-axis, that someone in the team must’ve missed. I don’t know why, but this broke all the collisions in the level, including BSP’s, static meshes and skeletal meshes.
So it was unrelated to 4.14 P1, even if the issue didn’t show up in 4.11.
In any case, I’ve PM’ed you a 4.14 P1 project with the 3rd Person Template and that faulty mesh in a newly-created level.
Ah, yes. Thanks for sending the project, it’s good to see exactly what is causing the issue.
A -z value that is that enormously (140,000,000,000+) can cause major float point errors that can affect the entire level. This isn’t really intended behavior but it’s not exactly unexpected either. We have other systems in place (World Composition) that would keep these issues from happening in a level that is actually this large.
