Important: Isaac Sim support
Note: For Isaac Sim support, the community is gradually transitioning from this forum to the Isaac Sim GitHub repository so that questions and issues can be tracked, searched, and resolved more efficiently in one place. Whenever possible, please create a GitHub Discussion or Issue there instead of starting a new forum topic.
Note: For any Isaac Lab topics, please submit your topic to its GitHub repo ( GitHub - isaac-sim/IsaacLab: Unified framework for robot learning built on NVIDIA Isaac Sim · GitHub ) following the instructions provided on Isaac Lab’s Contributing Guidelines ( Contribution Guidelines — Isaac Lab Documentation ).
Please provide all relevant details below before submitting your post. This will help the community provide more accurate and timely assistance. After submitting, you can check the appropriate boxes. Remember, you can always edit your post later to include additional information if needed.
6.0.0
[v ] 5.1.0
5.0.0
4.5.0
4.2.0
4.1.0
4.0.0
4.5.0
2023.1.1
2023.1.0-hotfix.1
Other (please specify):
Operating System
Ubuntu 24.04
Ubuntu 22.04
Ubuntu 20.04
[v] Windows 11
Windows 10
Other (please specify):
GPU Information
- Model: NVIDIA GeForce RTX 4090
- Driver Version: 581.08- Released
Topic Description
Detailed Description
We are currently testing LCC-based 3D reconstruction data exported as USDZ and imported into
NVIDIA Isaac Sim.
After internal engineering review, we confirmed:
- LCC reconstruction data is intact
- PLY export functions normally
- Distortion/blurriness occurs only in the USDZ export
- The issue becomes more severe as the geometry is farther from the world origin
This suggests that the problem may be related to USDZ conversion or the downstream interpretation within Isaac Sim rather than the core reconstruction data.
Error Messages
Screenshots or Videos
Additional Information
When the data was exported in the LCC format, no issues were observed.
However, after converting the same dataset to USDZ, the distortion/blurriness appeared as shown in the attached image.
The same dataset displays correctly when exported as LCC or PLY, and the issue only occurs when the data is converted to USDZ.
Therefore, it appears that the problem is not related to the original LCC reconstruction data but may be associated with the USDZ conversion process or the way the USDZ file is interpreted by the downstream platform.