Hello! I’ve looked into the state of UE-174155. It was temporarily marked as “Can’t repro”, but opened again because we have been able to repro it internally. The bug hasn’t been fixed yet. “Target Fix 5.8” is just indicating that the fix might come with UE 5.8, but the bug hasn’t been addressed yet. It’s also not an indication of priority. I’ll add to the internal info of UE-174155 that you are impacted by the bug.
“Do you have any idea where to llok in the code to fix the issue?”
My colleague has narrowed the issue down to a loss in Scale precision in the shader function DecodeTransform in SceneData.ush. That’s what we know so far.
Are you guys not using Nanite landscape? It shouldn’t suffer from that precision issue because of the “skirts” polygon strips that are generated on the edges of landscape proxies to cover the potential gaps. If so, then you shouldn’t need to disable compressed transforms, which seems like the nuclear option as it will leave a certain amount of performance off the table across all primitive types, not just landscape.
No, it’s just that in the editor, Nanite landscape can be not up-to-date, if a change was made to landscape for example. But the Nanite mesh gets recomputed when saving or cooking, so the problem should not be present in the final game (or when Nanite landscape is up-to-date in the editor, which you can verify by clicking on Build/Build Landscape, which updates all the outdated Nanite meshes). Just make sure that Nanite skirts are enabled in the landscape properties but that should be the case by default.