First of all, I am very happy with ReCap and have been using it every day since Beta.
There have always been some interface issues that are productivity speed bumps.
1. The Limit Box. Goal: Make it work simply from any viewing angle.
I just jumped from version 7.x to 2026.x. I don't tend to upgrade for this very reason; Cleaning up road pointlcouds involves isolating about 50ish feet of road, looking from the side in non-perspective view, erasing errant data from passing cars, then moving the limit box to isolate the next segment, repeat to the other end of the road. In 7.x, I could be in a topish view and hover on the limit boxes edges to move both sides of the box further down the road. In 2026.x, the limit box will only let the user move an edge if that edge is facing the viewport. So now I cannot be in a top view at all. I have to rotate around to see one side of the box and move that, then rotate around to the other side of the box and move it. Newer software version = more steps to do the exact same thing. Urgh! Make the limit box move any edge from any view. Allow you to rotate it from a top view where you can see clearly the limit box's angle to the scene (never been able to do that).
2. Stop having your interface and scan display go haywire when moving between 3D and Realview.
This has always been sketchy. And before you ask, you don't need a sample project from me to try it out. Load up any project with a set of scans and observe the behaviour for yourself. Many things will go south. If you have fence set for selection (which you almost always do), if you take a trip to Realview for a scan and back to 3D, you are back to window selection. That is annoying, but worse is if you have some scans not visible and go between modes, mirror balls for hidden scans may never come back. The scans themselves may never come back. I always get a little anxious moving between modes. I've had AutoDesk techs try to solve this with clearing caches (years ago). At any rate, put combinations of scans on / off, display and selection modes thru a trip to Realview and see the errant behaviour for yourself. The goal would be to make the software return exactly where you left off with no interface changes and scan state issues.
Love the local meshing in 2026.x. Most welcome addition!
Thanks.
Best Regards,
Buck Wyckoff
