Urgent: XR Tour Optimization Pipeline Broken – Request for .ply Import Functionality


Hello D5 Render Team,

I am currently developing a large-scale XR Tour for a Farm. My goal is to deliver two optimized versions: one for PC and one for Mobile. It’s a customer requirements.

When generating the initial .ply file, it contains around 3 million vertices. Your built-in cropping tools allow me to cut about 500k–800k vertices. However, the critical limit for mobile devices is 1 million vertices; anything above this causes a significant FPS drop.

The core issue:

  1. A month ago, after generating the .ply file, cropping was handled via a redirect to the third-party service SuperSplat, which included both import and export functions. Redirection was inside your interface.
  2. I built a working pipeline: I downloaded the file, ran it through a custom decimation script, and reduced the vertex count from 2 million down to the target 1 million.
  3. I would then upload this optimized .ply file back to SuperSplat. After saving, the optimized XR Tour displayed perfectly in the D5 Render “My Space” section and ran smoothly on mobile devices.
  4. With your recent update, you removed the SuperSplat integration and moved cropping into your native interface. However, there is no import function. I can download the file, but I can no longer upload the optimized version back to your platform. The native cropping tools are insufficient to reach the strict mobile vertex limits.
  5. Consequently, this UI update has completely broken my working optimization pipeline.
  6. I kindly request that you either restore the import/export functionality for .ply files within your native Edit section, or add a built-in decimation/reduction tool with percentage-based settings.
  7. This is a critical blocker for my project, which has been in development for over two months and is now in its final stages.

Please provide a hotfix or workaround at your earliest convenience.

Best regards, Alex


Hi @thefairytailgamemail

We have optimized this workflow by introducing the SOG format. The primary reason is performance: PLY files are typically very large, resulting in slow loading times on both PCs and mobile devices. On mobile devices in particular, large PLY files significantly increase the risk of performance issues, lag, or crashes.

In contrast, SOG files are generally under 100 MB, load much faster, and provide a smoother, more stable experience on both desktop and mobile platforms.

I will forward your request to our team to see whether it’s necessary to add it back.