Hi there, please watch the clip below to see the example. It’s an unlisted video, it’s not for views or anything, this is a genuine and serious problem I just cannot figure out.
I’ve tried turning lumen off, changing every kind of anti-aliasing type, I’ve increased DLSS resolution and turned it off altogether.
Nothing seems to stop these slightly glowy little points from being extremely fuzzy and flickering in-game mode.
Basically the video shows in-editor footage. I hit G to hide all the gizmos and icons. Essentially showing ‘game render’ view. This causes the dots to go fuzzy. But once I hit G again to bring back gizmos n stuff, the dots are perfectly crisp.
When I preview the game itself by hitting ‘play’ to test it, they’re fuzzy again.
Oh sorry I forgot to mention that. I changed them for every setting to see if any would affect this and non of them had any affect whatsoever.
Just to add, I’ve also increase screen percentage a lot too. I thought at first it was just lumen being awkward but I turned that off and nothing changed except for slightly different lighting
edit: also just to confirm, removing emissive colour or emissive power does not change it either.
It’s a point cloud. I have a niagara system that replicated a point cloud effect and they don’t do this weird fuzziness issue. But the real point clouds imported as a .las file created from photogrammetry, they have the fuzz issue. They’re not billboards or particles. The LiDAR plugin documentation says that each point is made up of two triangular polygons to represent the data from the point cloud index itself.
So technically, maybe they are billboards but they’re being drawn up in the back end by the LiDAR plugin.
Just to update: I tested the same setup in unreal engine 2.26 and the same fuzziness issue doesn’t happen there at all. Each point is absolutely crisp.
Having the exact same problem here on Unreal 5.1, at least good to know it exists for others. Turning off anti-aliasing fixes it in editor but once I hit play, the points have the same fuzziness as in your video.
We found, however, that with UE 5.0.3 this doesn’t happen. So for projects with .las Lidar point clouds we’re using 5.0.3 for now, hoping that 5.2 maybe fixes it.
Hi i have similar problem. I have complex scene made out of milions of points. Everyting is ok for few minutes, but afther that some of the point clouds are dissappearing for few seconds. I have the same problem with rendering. Version 5.2 is also broken with point clouds. Every time I reopen the projects I have to reimport point clouds becouse every point changed it position…
Hey Hubert . Ive been encountering the same issue re points needing to be reimported on every restart in 5.2. Have you raised a bug/ ticket with Epic for this? Just checking before I do so.
I discovered the source of the bug. Maybe it’s not a bug but just an unintended issue when using something the devs didn’t expect us to use.
If you simply just plug anything into the ‘world position offset’ pin in the (custom) material for the LiDAR point cloud asset, it will cause this fuzzing effect. Doesn’t matter what value you use, a simple float or the grasswind node, results are all the same. If you leave that pin untouched then this fuzzy issue doesn’t occur.
All I want is to be able to manipulate the position of these points and I’ve read the code for it and there is a section on point position specifically and yet I can’t access this at all.
The solution to fixing this issue is to turn off motion blur altogether. The source of the bug isn’t anything to do with what I mentioned previously but more to do with just having a custom material applied to the point cloud. It doesn’t matter if the new material is identical to the default one being used, it will create this flickering, glaring effect.
Just turn off motion blur. I discovered this from learning that the 3D gaussian splat plugin on marketplace is hijacking the point cloud plugin and the creators solution to the flickering issue was to remove motion blur.
I went into another project of mine that uses this point cloud plugin and turned off motion blur and it fixed my issue which caused me to start this thread in the first place.
