Edit: I’m moving this post to Bug Reports since I didn’t get a clear answer from the General Discussions.
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:
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?
I have the same issues! So glad you were able to get some screenshots and put into words what happened. The issue is still present on current version of scaniverse for android
Just saw this. I believe it’s an indication of memory usage as you noted. It doesn’t seem to affect the resulting scan other than the users ability to tell where they’re at.
I also suspected it was memory usage, but it still keeps capturing even as it gets blurry. And, like I said, it seems to be greatly influenced by the size of the scan rather than how much I scanned (scanning a long hallway vs scanning the interior of an entire house with several nooks).
Just saw this. I believe it’s an indication of memory usage as you noted. It doesn’t seem to affect the resulting scan other than the users ability to tell where they’re at.
I have a Motorola Edge 40 with A14.
Found some screenshots with the same issue on one of the older app versions, I have to yet try it out on the newest 5.0.0
The screens are of this scan in the making: Napoleon iii. - @Lupask on Scaniverse
though the scan itself turned out quite nice, upon closer inspection you will see mistakes on his shoes, hat, bench railings, etc. that are a result of not being able to see the (un)scanned areas properly due to the resolution loss.
When viewed on a large computer screen, it is not that nice to look at.
Now I got an idea: how about a user-selectable overlay with some system data? There is ample space in the lower screen portion. We could see CPU usage, RAM utilisation, GPU payload etc.
