I’m having trouble updating a project to 4.7. On first load, the landscape looks and works fine. If I save the map, then reopen it, the landscape is corrupted in a strange manner - it looks fine, but the collisions are in completely the wrong places. This is most immediately visible when regenerating and showing the navmesh.
Note the curious periodic behavior - it looks like it’s just using the wrong tiles in the wrong places. It’s also quite odd that it’s still rendering the landscape in the right place, it’s merely collision data that is corrupt.
I’ve tried resampling the terrain on first load, in the hopes that it will fix the collisions, but this merely corrupted the actual terrain data in a new and exciting way.
How can I fix this? Obviously this is unusable if I can’t save my level
Dysfunctional fix: I figured that the geometry was right but the collision wasn’t, so maybe if I could regenerate the collision from the geometry, it would work. I took a zero-strength huge brush and just waved it over the entire terrain. Fixed everything up like a charm.
. . . Aaand then broke again when I saved and reloaded. This turns out to not a functioning solution. Still need assistance
I have just a few questions to be able to better assist you with this:
Is the terrain generated in editor or was it a heightmap imported?
What are you using to regenerate the collision?
Is the terrain in the persistent level or in a sublevel, additionally are you using World Browser?
Generated in editor, persistent level, not using World Browser because I literally have exactly one level in this game so far :V
By “regenerate the collision” I mean “choose sculpt, set brush size to 8192, set brush strength to 0.0, wave brush over entire world, watch navmesh fix itself”.
I’m happy to send you the game files if you want, btw, just be aware it’s about half a gigabyte and I’d need to know where to upload it.
If you upload the project to a dedicated FTP server such as dropbox and either post here or pm the link to me I’ll be happy to pull it and see what may be occurring.
Try using the console command “RecreateLandscapeCollision”. I opened your project and did not experience any problems with the landscape collision or the navmesh. Do you have any steps I can take to reproduce what you are seeing on your end?
Sync to 4.7.1-release (I haven’t tried 4.7.2-release yet)
Build in DebugGame (others caused the same problem)
Open project
Hit P to show navmesh
Verify that navmesh looks correct (it was saved from the last execution)
Choose Build->Build Paths
Verify that navmesh now looks totally broken
Set the landscape Sculpt tool to maximum brush size and zero tool strength
Paint over the landscape; watch navmesh fix itself in the painted regions
Save map, quit
Return to “Open Project” step
“RecreateLandscapeCollision” actually breaks it even worse. Any tile with corrupted collision ends up with no collision, which means you can’t click on it with the zero-strength Sculpt tool to regenerate. You have to click on nearby tiles (which, thankfully, does work.)
Edit: Downloaded 4.7.2 through the launcher, same repro steps behave nearly identically. The only difference is that it’s now picking a different collision tile to duplicate in incorrect places.
As I said in the original post, second paragraph from the bottom, resampling the landscape trashes the data rather badly. It looks like some parts are offset by one entire tile and some parts aren’t. The result is not usable.
Have you been able to duplicate the bug, following my instructions exactly, on 4.7.2 downloaded from the patcher? I’d appreciate it if you tried - I’m going to ask a friend to do the same, to see if it’s a problem with UE4 or with my computer (though I think that’s doubtful).
Well, I’m not certain what changed between last week and this week, but I finally managed to reproduce it! I entered a bug report, UE-11583 to be assessed by the development staff.
Since I don’t believe I can see your bug tracker yet, please let me know if there’s any updates; I do most of my development through a slightly modified UE4 anyway, so I can easily patch code in if it fixes the issue. Right now working is a real pain.
Ive been having this issue as well. Im glad its been reproducible and someone posted about it. Its quite an annoying bug especially when i cant properly play test my levels.
Im sure there probably isnt any updates on the status of this bug report a couple of days after but i would really like to know when this would be fixed also.
