Hello,

We are looking to verify that you've actually placed an anchor from a hit-test result.

With Vuforia VISLAM in 8.0 (and Vuforia VIO in 7.5) hit-tests are done against the assumed height. There is no hit-test against any real geometry.

Only for an anchor created from a hit-test result scale that estimation is actually applied.

Thanks,

Vuforia Engine Support

Any updates on this? I'm running into the same problem where the scale of the Plane Indicator is super small on the device. The object scales to the correct size only after I place it and move the camera around a bit. If I move the camera around before placing it, the indicator remains small. This happens even with the basic tutorial setup (see attachment).

Is there a way to scale the Plane Indicator before placing it according to the "confidence" level or something or is there another way to fix this problem?

I'm using Vuforia 7.5.26 and running Ground Plane on an iPhone 6.

Hello,

tompainter wrote:

but the height is just a hint to set the starting point anyway? if I move my phone a lot this should be eventually discarded once good spacial data is available?

Correct on both respects. Per engineering feedback, I will open the issue for further investigation.

Please see this thread for any relevant updates.

Thanks,

Vuforia Engine Support

Hi

it was iphone 6+ and iphone X 

I think i set the height to like 40cm or something. because our app is meant to be used to place small products on a desk (the floor in our case is the desk) . I think the 1.4m or whatever the default is for standing people putting cars/humans etc. on the floor

but the height is just a hint to set the starting point anyway? if I move my phone a lot this should be eventually discarded once good spacial data is available?

best

Tom

Hello,

Thanks very much for the feedback. A couple of questions:

• Which devices were used for this comparison?
• What "height" value are you using in Plane Finder Behavior Inspector? In your scene, PlaneManager->PlaneFinder->Advanced

-Vuforia Engine Support

Hi 

I saw the vuforia 8.0 announcment today with VISLAM so I tried it out. great to see a focus on old phones instead of the new shiny tech. 

AR as an industry needs AR to 'just work' for all phones, we're not there yet and part of me wonders if that day will only come in 2-3 years when all phones are ARcore/kit

the UX is way better now, seems more similar to ARkit. hopefully I can get a more unified UX across all devices now. (see screenshots currently I have treated them differently)

stability seems better too.

still I have scale problems, even if I spend 1 minute moving the phone around the environment the scale estimation doesnt improve. my object is 50% the scale it is on ARkit capable phones

just wondering if VISLAM has any tricks I can use to improve? is the 'scale confidence' exposed anywhere? i.e. if its low I can tell user to keep moving phone around, if its high I can assume the correct scale.

thanks

Tom

hi thanks for your help

I thought I already tried all this, but I'm going to double check if the VIO device is showing status = limited before the scale is looking like it is more accurate.

hopefully it is and then I can add some hints for the user

I will report back soon

best

Tom

Hello,

Let me try and provide you with some additional information about the Ground Plane feature that *may* help.

• https://library.vuforia.com/articles/Training/ground-plane-guide.html
  • Provides a good overview of the feature, including performance expectations
  • There is a section for "UX Concepts and their application" at the bottom of the page
• https://library.vuforia.com/content/vuforia-library/en/articles/Solution/tracking-state.html
  • Provides an excellent overview of the return values of the tracking state APIs
  • At this time our samples and coding examples may not be exactly consider "best practices" - we'll look to improve them
• The Height attribute of Vuforia.PlaneFinderBehaviour() represents the real world height of the camera in meters.
  • You can adjust the height programmatically via PlaneFinder Height property in the Unity Vuforia Core Samples. This is just a "seed" value for Vuforia VIO, and it will not change or rescale the height values returned by Vuforia Fusion (ARKit, ARCore or Vuforia VIO).
  • Vuforia APIs do not provide the ability to scale the augmentation. This must be done programatically.

Thanks,

Vuforia Engine Support

BUMP!

would really appreciate some help from support. Im running low on ideas now.  my first post was over a month ago.

best

Tom

Hi

i still haven’t solved this.

can anyone help please?

best

tom

Ok last one from me...

 

'height' is a bit misleading here as i doubt most people are placing augmentations directly below the camera? in my school maths class we'd normally use pythagoras theory to work out what in this case would be the hypotenuse? 

'approximate distance to augmentation' is my suggestion for renaming that parameter.

but better still exposing a 'distance to augmentation confidence' value would be best as it would allow me to give extra hints to the user

in the PlaneFinder object in unity I found there is a 'height' we can set

https://developer.vuforia.com/forum/ground-plane/set-planefinder-heigth-runtime

so this gives me a better starting point, our augmentations are typically about 20cm tall products, so I can assume that the user is an average of 70cm away from the augmentation

but when I do my dev at my desk for example, Im more like 30cm away from my augmentation, and until I get the VIO algorithm enough scanning data the object is about 2x too small, I'd guess the algortithm at this point is pretty uncertain about the distance to augmentation.

At a certain threshold the camera will 'pop' and at this point I'd guess vuforia is pretty certain about distance to augmentation?

if you guys could let me know if this could be exposed in a future version, or if Im missing some vital piece of knowledge, that would be great.

many thanks!

Tom

This person asking a similar but slightly different thing a while back...

https://developer.vuforia.com/forum/qcar-api/exposing-confidence-particularly-unity

Ive been digging in further and displaying some diagnostics to my screen to get a better idea under the hood,  but I could still do with some expert help if anyone can help?

in VIO mode, before I tap to place the object, status=LIMITED and statusinfo=INITIALIZING, if I move my phone to scan at this point, nothing happens to improve the eventual track

after i tap the object I see that I get status=TRACKED and statusinfo=NORMAL, but these dont change as I scan the room and the object suddenly 'pops' to the correct scale

would be great if there is like a 'accuracyCertainty' score or something which can be exposed?, so once we get to a certain confidence level we can be pretty sure the object is at least 90% accurate scale? at that sort of threshold I would hide my 'keep scanning the room' UX instruction.

best

Tom

Im still struggling with this.

if you check the vuforia sample scene's groundplane demo, its almost like there needs to be another message for phones running in VIO fusion provider mode

something like "Move your phone around to make the object the right size"

I'd implement this in my app, but Im not sure how to know when we can turn it off again.

best

Tom

Hi

just to help explain what I mean, Heres a screen shot of my current UX flowchart

it seems ARcore / kit has a well structured, scan then see lovely AR workflow

but VIO has a progressively better tracking, which I think will confuse the average non technical user.

is there a way we can query if VIO is confident about the object scale? it seems to reach a point where things are pretty good, we could use that to turn off hints at that point.

hope that makes sense

best

Tom