Recap Ideas
Share ideas for future product features directly with the Recap team and collaborate on existing suggestions with your peers.
New Idea

3D Photographs to Model Ability to Embed PDF's

Status: Accepted
by Advocate bd5cents on ‎12-30-2015 09:29 AM

It would be immensely beneficial for us to be able to tag the model, attach specification data, submittal data, warranty information, and hyperlinks to the 3D model that is generated, and then to be able to send that data to an interface that allows our customers, service department, and others to view the attached information. Without the need for ReCap. I'm thinking through A360 Team!


Attached is our current workflow, and from there you can see why it would be beneficial. We currently use A360 Collaboration for Revit to push this information out to our contractors. It would help a lot to get the software to allow for this capability. It would streamline our deliverable process and make us more efficient as well.


The ability to host this data in the cloud through A360 would allow us to provide a customer deliverable that is easy and functional!

Status: Accepted


Status: Gathering Support
by Contributor brianlee on ‎04-19-2016 11:29 AM - last edited on ‎04-19-2016 11:38 AM |

I would like to see a 'bundled' format for RCS files which can be extracted with programs like 7ZIP (such as a DOCX or DWFX). If I ONLY copy over the RCS files, I cannot re-register them again in ReCap as it loses the thumbnail and other functionality I'm not yet aware of. I would like to have the .DIFF, .LLT, .RCC, and .THUMBNAIL 'bundled together' with the .RCS with some .XML file which also stores scanner setting information and locational data (from the original RAW scan data of the device). Correct me if I'm wrong, the RCS is the RAW unfiltered data with the deltas carried inside the other dependency files.


The primary reason I'm trying to do this is so that I can organize my files better. My folder usually is exploding with scan files. I use ReCap by distributing the import point process onto multiple computers manually (I'm impatient, I don't like waiting and I don't drink coffee). For example, I would divide the set of scans between (eg. 3 computers) and run import from .FLS simultaneously. I would then reimport the .RCS files into a new project and re-register them together as a 'master' file.

[This is a cross posting from the a360 idea station]


i have folders from using SiteScan (3DR) and they include a zip file for certain recap created types. Currently, if i browse to the a360 drive, i cannot extract

that zip file in that location.


I have 2 choices, either copy that zip to my desktop (or other local location), extract and then copy back the extracted files OR browse to the physical location of the a360 files (C:\Users\Kevin.Spear\AppData\Local\Autodesk\Autodesk Sync\Cloud\...) and exctract it there.


So, i would like to extract ZIP files in a360 where they live.


Secondarily, it would be great if Recap didn't deliver the results as ZIP files though.




0 Kudos

Currently in V4, we don't have the ability to upload the RealView elevation slices that were created on the desktop version.  This means that we have to create a recap project for each level, and upload separate projects.  This may be more of a bug than an idea.  



I love to have the ability to export each scan into separate PTX files from ReCap. 


This format is so mutch better than a flat xyz-file format. 

With PTX file you can preserv the transformation information from the laserscanner.

And each point is in its local coordinate system (smaller file size), and the global coordinate relation is in the header (matrix). 

So by multiplying each point whit the global matrix you get the worldspace point.

Its easy to calculate each points normal by compute its closest neighbors (and each point is targeted from the scanner position).

Its easy to compute a image from each point useing grid cells to pick pixelcollors.

And best of all, PTX Ascii format is future proof! If you storage your scans, thay will always have all the requered information to recapture the scaned data, as long as you can read Ascii files (forevere) (as far as we know). 


Here follows a format description of the begining of a ptx-file. 

// I have added some comments after each line

12565 //lattitude grid cells, sphereic relation to the scanners position and rotation angel between cells
4700 //longitude grid cells (Cells are like engine steps for the laserscanner beam to catch each point)
752.639056999993 625.250815000385 42.085689 // x,y,z of scanner position.
-0.157309 0.987549 0 //3X3 matrix (this and the folowing 2 lines)
-0.987549 -0.157309 0 // -||-
0 0 1 // -||-
-0.157309 0.987549 0 0 // complete 4X4 matrix (this and the folowing 3 lines)
-0.987549 -0.157309 0 0 // -||-
0 0 1 0 // -||-
752.639056999993 625.250815000385 42.085689 1 // -||-
-1.300339 -1.056778 -1.678848 0.205203 116 129 101 // here starts messured coordinates 
-1.302322 -1.058395 -1.679733 0.203494 129 143 108 // each line is a point. To get the world coordinate, multiply point with the 4X4 matrix. 
-1.301895 -1.058060 -1.677505 0.215702 118 138 101 // each point is x, y, z, intensity, red, green, blue. The color is a int 0-255

0 0 0 0.5000 0 0 0 // missing points in dataset is made up like this to fill the empty cells in the format. maby laser beam hit the sky, or points removed on in editing software 

... // here follows millions of lines exluded in this example


Here follows the same ptx header whitout comments:

752.639056999993 625.250815000385 42.085689
-0.157309 0.987549 0
-0.987549 -0.157309 0
0 0 1
-0.157309 0.987549 0 0
-0.987549 -0.157309 0 0
0 0 1 0
752.639056999993 625.250815000385 42.085689 1
-1.300339 -1.056778 -1.678848 0.205203 116 129 101
-1.302322 -1.058395 -1.679733 0.203494 129 143 108
-1.301895 -1.058060 -1.677505 0.215702 118 138 101




Best Regards


First:  you have a good product.  I use it daily and it is a critical component of our business workflow.  Accordingly, I do beta tests and am first to try out new updates and features.


I keep getting requests for new services and features.  This is great!  However, I would suggest you do some housekeeping around the Recap platform before confusing the customer with new editions, models, features, subscriptions, names, brands, SDKs, DLLs, GUIs, web-portals, etc.


To elaborate:  If everry there is someone who should understand the Recap system it is me.  I follow and subscribe to most anything I can get my hands on.  Yet even I am confused with versions and releases and features and cloud credits and A360 and Recap360 vs. Ultimate vs. Pro vs 2.2 vs. Recap2017 vs Cloud, vs subscription.  Can you make 2 (or at most 3) "Levels" of program and stop it there, with clear delinineation between what is included with each?


Furthermore, I don't think that Photogrammetry and Lidar shoudl be mixed into one program.  They are entirely different at the moment. Lidar is destktop, while Photogrammetry is just a link to your Recap 360 website (againn, very confusing).  


Uploading a Lidar scan project to the Recap360 (or is it A360?!?!) site to share with a client is clunky and confusing. Equally as confusing with Photogrammetry projects and creating Meshes from Lidar data.  Argghhh!!


You should run a dead-link check with ALL of your portals, sites, hubs, blogs, newsletters, etc.  It is quite frequent that I encounter a dead link.  And this is not exclusively when browsing an obscure post or site.  Some top level links from the Recap interface are dead links (404 errors).  And some of the top posts on the forum provide answers to questions for Recap 1.x that was replaced and made obsolete year(s) ago.   Keep current/relevant posts and suggestions top and archive the others.  Things move fast in your world.  Unlike a Microsoft Excel forum, posts on Recap are obsolete after 12 months.  Maybe less.  Many of your "News" postings are from 2014. Purge them.


Lastly, you should consider one streamlined place for Recap users.  Currently there is Autodesk product pages, Recap360, user groups, hubs, forums, etc.  And there is little consistency to content across them, or reciprocity in links between them.


Also lastly, how about disabling the upsell links for subscriptions if the user is signed in already?  I'm currently a "Pro" subscriber and yet on the Recap program main welcome screen, it pitches me to "Upgrade to Pro to unlock features".  I could overlook this except that I have litte confidence in the Adesk system knowing I already AM a Pro subscriber.  Or so I thought.  Have I done something wrong?  


Shake some things up at Recap, make them consistent, create a single brand/product, and don't look back.  I'd be all in.  Your customers would flock to the product. Right now even our Authorized resellers don't understand it.


Far too long of a rant, but I mean it constructively,


Status: Accepted
Submit Your Ideas

Share and shape product ideas.

Submit an idea
Idea Guidelines

Please review our Idea guidelines and best practices before posting a new idea, or voting on an existing one!


For more info about ReCap visit the ReCap product page