Reduce size and keep RealViews in ReCap

Reduce size and keep RealViews in ReCap

Anonymous
Not applicable
1,158 Views
6 Replies
Message 1 of 7

Reduce size and keep RealViews in ReCap

Anonymous
Not applicable

Hi there!

 

I used your faq to reduce size and keep realviews and it is working until you want to reproduce the procedure after updated origin.

 

So steps to reproduce bug:

 

1) update origin

2) unify project to rcs

3) add original point cloud data to a region

4) import the unified rcs with skip registration (for me it should be to keep original x,y,z coordinates)

5) realize that the unified rcs is translated twice, because it is already translated in rcs (good) and recap translate again after import (wrong), so it means that the imported point cloud is not on the right position.

 

To solve that now you cannot change origin before reduce. Because if you use register scan than it will be inaccurate on a big 200+ scan location project and also very slow. I do not understand why it is translated after import that is not normal.

0 Likes
1,159 Views
6 Replies
Replies (6)
Message 2 of 7

anil_mistry
Autodesk Support
Autodesk Support

Hi @Anonymous,

 

Thank you for participating in our Community! I will forward this to development team and see if they have any suggestions or feedback. I will give you an update soon.

 

Thank you and have a great day!



Anil Mistry
Technical Support Specialist
0 Likes
Message 3 of 7

yan.fu
Alumni
Alumni

I think there is a bug in the unification after upating origin and it causes the translation of the unified scan to be wrong.

 

We will fix it in future releases.

 

 

0 Likes
Message 4 of 7

Anonymous
Not applicable

I used e57 export as well and reduce e57 with other software and the result is same. If it helps. Thats why i though it is import problem. The result same with both method...

 

And of course the exported e57, unified rcs seems fine in other product such as revit, archicad (keeps modified x/y/z coordinate system).

0 Likes
Message 5 of 7

anil_mistry
Autodesk Support
Autodesk Support

Hi @Anonymous,

 

Thank you for your reply. As @yan.fu mention in her post saying that development team is aware of this behavior and it will be implemented in feature release. Either @yan.fu or I will give you an update via forum post once we have more information.

 

Thank you and have a great day!

 

Please select the Accept as Solution button if my post solves your issue or answers your question.

 



Anil Mistry
Technical Support Specialist
0 Likes
Message 6 of 7

anil_mistry
Autodesk Support
Autodesk Support

Hi @Anonymous,

 

I'm just checking in again to see if you need more help with this. Did the suggestion @yan.fu provided yesterday work for you?

If so, please click Accept as Solution on the posts that helped you so others in the community can find them easily.

 

Thank you and have a great day!



Anil Mistry
Technical Support Specialist
0 Likes
Message 7 of 7

DonHenley
Contributor
Contributor

I believe I have found a temporary solution for you until Autodesk fixes this workflow (which I'm almost certain I've done in the past with projects that had updated origins, as long as the origin was the same in both the .rcs and the RealView project)

 

When importing the .rcs, simply select "Resume Registration" and you can register your rcs to the original scans before deleting them. I don't care for registering in Recap, much too slow to do a whole project, but for this purpose it works fine. It doesn't even have to be super precise; all you're doing is getting the RealView Mirror Balls back into a place that makes sense with your new, smaller point cloud.

 

I realize it's been months since you asked, but this is a major pain and I hope this helps someone else who is having the same issue.

----------------------------
64-Bit Windows 10
Intel Xeon E5-1620 v3 @ 3.50GHz
NVIDIA Quadro M4000
32GB RAM
0 Likes