I didn’t find a question in this forum about it or tutorial since this is, to my knowledge, something specific to the android version of the app. I don’t know if it’s a visual bug or if it’s intended.
Then I’m just gonna ask here:
What does it mean when, during the scan, the scan viewer progressively loses resolution as the scan gets bigger?
What I mean is that the scan process goes from this:
To this:
To this:
Until it reaches this:
As the resolution gets worse, the ability for me to identify how well something was scanned gets worse (any new area scanned past this point doesn’t have many splats after processing).
This is influenced mostly by the size of the area scanned not so much by how much I scan. I can scan all rooms in my house and not get the resolution to drop, but if I try to scan something outside, it very quickly drops the resolution after I do a few rotations around an object in an open area.
This affects both splat an mesh scanning, but since mesh limits how far it scans, it takes longer for it to be affected.
Is this behavior intended? To demonstrate the size of the scan area able to be processed in memory? Or is this just a misbehavior of the usual feature that reduces the resolution of objects still to be scanned on the scene?