Troubleshooting

Common DXR issues

• You might not have a DXR compatible card.
• You have a compatible card but DX12 is not enabled/used by your project.
• You have a compatible card but not a recent driver that supports DXR.
• You have a DXR compatible card on an old windows 10 version (version before 1809).
• DXR has been disabled by windows due to the current power level of your computer. Some configurations require that you manually enable unity.exe to use high performance in the control panel.

Graphics issues

• Make sure your graphics card meets the system requirements.
• Review the installation instructions.

Photosensor issues

No visible point cloud

If your lidar doesn't display anything, the following check will help you to get through the common problem encountered.

• Make sure you have the requirements.

• Look at the properties pointCloudCount on your lidar's point cloud viewer. You will find it on the main camera.

• If you have pointCount > 1, then there is a problem with the sensor set up.

• If you do have more than 1 point but you still don't see any dots, after completing the getting started, it's most likely a problem with the configuration of the graphics card.

Warning messages

Photosensor is capturing more than a full frame in a single update. Discarding extra samples.

This message is displayed when the Photosensor v2 node receives a sampling request for too many samples, and the Frame Bundler node does not have enough space to store all the samples, as it would require more than two frames. Here are some possible causes:

• High sensor frame rate. Sensor frame rate is higher than the simulation update rate. In that case, either decrease the sensor frame rate or slow down the simulation by using a smaller maximum time step.
• Slow simulation start. When entering play mode, the first few frames usually take more time to render because of initial allocations and computations in the Unity Editor, in HDRP and in SensorSDK. For some sensors like the ToF camera, this is enough to cause the above message to be printed a few times. Use a smaller maximum time step to temporarily slow down the simulation for the first few frames, or add a script to enable the sensor GameObject after the first few frames.

To set the maximum time step:

1. Select Edit > Project Settings....
2. Select Time.
3. Set Maximum Allowed Timestep to a smaller value.

Sensor configuration

• Check for any warning or error related to your sensor in the console.
• Make sure that all sampling rate on nodes are > 0.
• Make sure there is no node or edge missing.
• Make sure that the synchronized nodes have a clock in the Scheduler.

Visualization issues

Point cloud visual effects are sometimes not visible in a new project. To work around this, find the file PointCloudViewerVFX.vfx in the project, open the graph and select Compile.