Closed farstarss closed 5 years ago
Scanning a room with the Hololens using the HoloToolKit for the whole purpose of getting a 3D scan seems to be something that's not intended to be done.
However, there is a solution to the described issue with the approach above, that I would like to share in case anyone else is facing this:
As mentioned in the original message, scanning a room divides it into multiple overlapping volumes of (2.5 m)³. Each of these volumes has its local (0,0,0) point in the center of that volume. Thus one can check if both vertices of a solitary edge have an absolute value for x, y or z that is larger than 1.25 (= 2.5/2). If that's the case, one can assume that this edge is in fact a volume border and simply ignore it in the further process.
Closing older HTK issue as we are no longer actively working on HTK.
Please upgrade to MRTK V2 for the latest fixes.
Does this affect the legacy HoloToolkit (master) or the Mixed Reality Toolkit (mrtk_release)? HoloToolkit
Is your feature request related to a problem? Please describe. I've got 2 related questions:
If there is a solution to question 1, question 2 can gracefully be omitted.
Describe the solution you'd like I'd like to show the user of my app where to scan / which parts of a room are unscanned before finalizing the scan.
Describe alternatives you've considered So far I couldn't find any easy solution for question 1 and the process is as follows:
The issue with this approach is: The room is separated into multiple volumes by the size of (2.5 m)³ and thus the above algorithm not only gives me the holes in the mesh but also the borders of a volume where it intersects with the environment.
Additional context The hololens will only be used to create a 3D model of a room which will then be stored and used with other VR headsets. The usual 'just look around until we have enough spatial understanding information' is not satisfactory.