ULidarPointCloudSettings

If enabled, the assets will automatically build collision upon their successful import.

If enabled, the assets will automatically calculate normals upon their successful import.

Automatically centers the cloud on import.

Enabling this will allocate larger portion of the available point budget to the viewport with focus.

Enabling this will automatically release memory used by the asset once it's cooked Helpful when dealing with very large data sets to avoid memory blocking

Enabling this will automatically release memory used by the asset once it's saved Helpful when dealing with very large data sets to avoid memory blocking

Enabling this will allow editor to import the point clouds in the background, without blocking the main thread.

Enabling this will greatly improve runtime performance at a cost of quadrupling VRAM use

If enabled, the render data generation will be spread across multiple frames to avoid freezes

Sets how long the nodes wil be kept in RAM after they are no longer visible.

Determines how to handle duplicate points (distance < 0.0001).

Scale to apply during export. In most cases, this should be equal to an inverted ImportScale

Scale to apply during import

Maximum number of unallocated points to keep inside the node before they need to be converted in to a full child node.

Maximum distance between points, within which they are considered to be duplicates

Affects the size of per-thread data for the meshing algorithm.

Determines the maximum amount of points to process in a single batch when using multi-threading.

Virtual grid resolution to divide the node into.

If UseRenderDataSmoothing is enabled, this will determine how much of the frame time can be spent on render data generation.