ReCap SDK v21.0.0 is now available on ADN

[karthik.nathan]

We are pleased to release a new version of ReCap SDK (v21.0.0). It is available to download on Autodesk Developer Network (ADN). This version will be binary compatible with AutoCAD 2021 and verticals, Revit 2021 and Maya 2021. Here are some of the improvements and fixes in v21.0.0:

ReCap SDK Release Notes

Version 21.0.0

New features

• AutoCAD plug-ins built with ObjectARX 2021 will now have access to all ReCap SDK 21.0.0 APIs to query and manipulate ReCap scan projects. Entry into ReCap SDK from ObjectARX is via the AcDbPointCloudEx::getReCapProject() method which returns an RCProject* object. ReCap SDK APIs can then be used on the RCProject* object to iterate through the points, query the point cloud, etc. Please refer to ObjectARX 2021 AdDbPointCloudEx documentation.

Enhancements

• Namespaces are changed by regrouping into three main namespaces: Foundation, Data, and ImportExport. The namespace changes are as follows:
  • Autodesk::RealityComputing::Common -> Autodesk::RealityComputing::Foundation
  • Autodesk::RealityComputing::Utility -> Autodesk::RealtityComputing::Foundation
  • Autodesk::RealityComputing::Common::Math -> replaced by RCMath static class in Autodesk::RealityComputing::Foundation
  • Autodesk::RealityComputing::Project -> Autodesk::RealityComputing::Data
• Header folder structure and names have changed (based on the new namespaces). There are now only four main folders under '\include': foundation, data, importexport, and realdwg. The folder name changes under '\include' are as follows:
  
  • common -> foundation (i.e. \include\common has been changed to \include\foundation)
  • utility -> foundation o data -> data
  • project -> data
  • import -> importexport

• RCCode is changed from an enum to a strong-typed enum class.

• Use coordinate system set by user as the source coordinate system for the raw scan file

• Argument of RCImportProgressCallbackPtr is changed from (RCIOStatus& status) to (const RCIOStatus& status)

• pointsPerMM3 in class RCScanImportOptions has been renamed to pointDistanceInMM to better reflect the meaning of the variable

Fixes

• RCBuffer(unsigned int num) constructor, which would set the buffer capacity to num but leave the buffer size as zero, has been removed. Client apps will now get a compile error, and will have to replace old code with the default RCBuffer constructor variant followed by a call to reserve(). For eg. RCBuffer<int> buffer(8); will have to be replaced with RCBuffer<int> buffer; followed by buffer.reserve(8);

Deprecated functions

• None

Thanks.

Reality Solutions Team

[simonjones-uk]

Thanks I'll persevere along those lines...

[martin.graner]

TBH I don't think that you will be able to circumvent creating the RCP / RCS files.

Either Autocad needs to understand your own point cloud format to render it with its internal functions (which will be adapted for RCP), or you write your own renderer (which sounds like a hassle) in the Autocad plugin.

But would be great to hear if somebody can disabuse me.

[simonjones-uk]

Unfortunately that is what my customer was hoping to avoid and hoping that the AutoCAD Point Cloud object could be written directly. Presumably an AutoCAD Point Cloud is really just a link to an RCP/RCS file and the point data isn't actually saved with the drawing? In which case, the necessity to have an intermediate RCP/RCS file makes sense.

[miroC8S4H]

It works perfectly with E57 Point cloud format, I will try LAS in next days. Those two codecs are part of SDK and you can include them using parameter"-c". After RCP is created, you need to set Visual Style to "3dWireframe" and then attach created RCP File.

That approach works.