Yes, that’s the one - it will return the first hit point. You can also use the Multi variant, which returns all points intersected by the ray.
And yes, it doesn’t rely on any built colliders. Instead, it uses a few intersection algorithms to identify the hit points.
The returned point’s location will be relative to its containing asset’s center point (typically, the actor’s pivot), so you’ll need to account for any actor / component transformations.
If you still get incorrect results, even when the transforms are accounted for, let me know!
Hi @
Thanks for your support! The lidar point trace still gives me inaccurate result. This inaccuracy might be caused by the big distance (appr 500km) of the points from 0,0,0, but I’m not sure if this is correct. So, as a test, I’ve moved the pointcloud actor to be close to 0,0,0 as possible, but I still get inaccurate results. Even a trace besides the points will return a result (even if there are no points):
In a next test I’ve translated the points close to 0,0,0 in an external application first before importing the pointcloud into Unreal. See the image below. The pivotpoint of the pointcloud is at 0,0,0. The red sphere shows the hit location (and a printscreen text). It still hits somewhere below the actual points:
I’ve no clue what to do now. Can you help me to test my pointcloud? I can send it to you in las/pts format, I can provide the UE project as well if needed.
Hi
I’m learning Unreal and I’m having problems rendering a point cloud fly-through. While the point cloud shows very dense in the viewport, when I render it using movie render queue, the point cloud starts reasonably dense but as the camera moves it starts the density begins to get lower until it sometimes disappears. I’ve tried a few things that I read in here but nothing seems to work. I’ve set density to 100m and I’ve also tried to render at different resolutions. I’ve also tried rendering a sequence with a static camera and I get the same results. I have a RTX 2080 Super and 128 GB of ram. I don’t think its a hardware issue because the point cloud shows nicely in the viewport. THANKS!
Hi!
I’m trying to build the collision of a point cloud using a Python script. I’ve found the build_collision() function in the PythonAPI documentation but I couldn’t make it work yet.
Has anyone done this before?
Thanks!
“The returned point’s location will be relative to its containing asset’s center point (typically, the actor’s pivot), so you’ll need to account for any actor / component transformations.”
When I open my map with point cloud from UE 4 in UE 5.1, I will get warning in output:
LogClass: Warning: SerializeFromMismatchedTag failed: Type mismatch in OriginalCoordinates of OriginalCoordinates - Previous (StructProperty) Current(StructProperty) for package: /Game/Map/Main/1_0009_pc
LogClass: Warning: SerializeFromMismatchedTag failed: Type mismatch in LocationOffset of LocationOffset - Previous (StructProperty) Current(StructProperty) for package: /Game/Map/Main/1_0009_pc
And a position of the point cloud is wrong (different location). Can I solve it somehow?
I solved the errors by reimporting all point clouds + align function. Everything jumped back to correct places.
But there is a problem with world partition.
The GREEN area are all aligned point clouds on the correct places.
The BLUE area are all point clouds on the world partition window (on same place) - wrong, they are really not there, I see them on correct places, this are only their pivot points.
The RED area is currently visible area in world partition.
The problem is that ALL point clouds are displayed when I will enter the red area and ALL are hidden when I leave the red area. Which is wrong. I want to load only point clouds around me, not all when I will go near all their pivot points.
I found that the wrongly aligned pointclouds was those that was edited in UE. So I have to reimport original ones and then aligning works ok (I used aligning function directly from the plugin, no external blueprint).
Hello everyone!
When importing a pointcloud (.laz format) everything works.
However when saving the project, closing it and reopening I get the wierd result below.
Anyone knows why?
Similar here. In editor with UE 5.2 everything is fine but when playing in standalone or packaged, I also have this weird cross. It’s not the point cloud itself because in other applications and UE 5.0.3 for example it displays correctly.
Unfortunately I also haven’t found a solution yet.
We are trying to open a very large .e57 (713GB). The ReadPoints Callback in LidarPointCloudFileIO_E57.cpp is not being called by the DLL function ReadPoints. So the rusult is an empty pointcloud. Any ideas how to fix or debug that? Thank you.
That happened to me too. I did default the render settings and it kind of worked again. Even though this does not solve the non visible in deployment problem I deal with too. Is this the initial state?!
