[Bug] Recap 2026 25.1.2.377 - RCS export fails when exporting large RCP project without optimizing project or saving in same folder as previous export

[Bug] Recap 2026 25.1.2.377 - RCS export fails when exporting large RCP project without optimizing project or saving in same folder as previous export

rrogersRM
Advocate Advocate
312 Views
4 Replies
Message 1 of 5

[Bug] Recap 2026 25.1.2.377 - RCS export fails when exporting large RCP project without optimizing project or saving in same folder as previous export

rrogersRM
Advocate
Advocate
  • Version: Recap 2026 25.1.2.377
  • Source file: e57 (embedded panoramas, 15.3 gb) from Navvis Ivion


Steps to replicate:

  1. I imported an e57P (what Ivion calls embedded panorama e57 files) into Recap
  2. Delete several points from point cloud
  3. Save file without optimizing
  4. Export as RCS (5mm) into same folder as a separate previous export doing the same steps above
    1. I also deleted the temp folder that is created by Recap prior to doing this and even restarted my PC afterwards
  5. Export window will stay stuck on 0% for 10+ minutes


Steps to resolve:

  1. Save as optimized point cloud (3D point cloud only, keep RealView as-is)
  2. Export as RCS into different folder than previous export
  3. Export will begin as normal and will successfully export


I'm not sure if it's trying to export without optimizing or saving into the same folder and deleting the temp folder that has caused the bug.

0 Likes
313 Views
4 Replies
Replies (4)
Message 2 of 5

barmanr
Community Manager
Community Manager

Hi @rrogersRM ,

 

Thanks for letting us know about the issue. We will take a look.

 

A couple of questions:

 

1) Are you trying to overwrite an existing exported file in the same directory?

2) Which temp folder are you referring to?

 

Thanking You.

 

Warmest Regards,

 



Rishov Barman
Reality Capture
0 Likes
Message 3 of 5

rrogersRM
Advocate
Advocate

I'll try to replicate again on my end today to ensure it wasn't just an issue with the progress bar not updating.

 

  1. I was not overwriting an existing file.
  2. It's the temp folder that is created in the target export folder where it stores all the temporary files for the RCS before it converts them into .rcs

 

Thanks,

Ryan

0 Likes
Message 4 of 5

kubitTilo
Advocate
Advocate

What’s the target application you’re focusing on with your workflow? I ask because we’ve developed a solution that integrates NavVis Ivion data directly into Revit, and we’re considering expanding to other BIM/CAD applications. Would love to hear more about the tools you're working with!

 




Tilo Pfliegner
0 Likes
Message 5 of 5

rrogersRM
Advocate
Advocate

Revit and Navisworks. We don't typically do geo-located coordinates for alignment since we're a building construction company. Instead, we use project internal coordinates of the architectural Revit model for alignment. I import a DXF (vector map) from the Revit model of the area that I scanned into Ivion (you need to use Meters as the export units and import as site coordinations) and use that for doing my X&Y + rotation alignment within Ivion.

 

Then I export the point cloud from Ivion as an .e57P and import that into Recap to do any fine alignment and set the elevation of the point cloud. Once everything is where I want it and I do any clean up, I export the final point cloud as .rcs to use within Revit and Navisworks.

 

If I rescan the same area at a different date, I'll export that same .rcp as an e57, bring it back into Ivion, then do an automatic alignment of my new scan to my aligned scan. It usually works pretty good unless the difference between the two scans are large.

 

rrogersRM_0-1751286080605.pngrrogersRM_1-1751286128825.png