Hello Luca,

I notice you have the box checked to override detection position. Have you moved the guideview to be out of view by chance?

Thanks,

Vuforia Support

Hi Strasza,

I tried with override detection position both checked and unchecked, but nothing happens. I didn't move anything. The only thing I can say is that the camera and the model target are placed in (0,0,0). 

Is there any problem with the Holotoolkit 2017.2.1.4 ?

Thanks

Luca

Hi!

Your Vuforia Configuration window is different from mine. Are you sure that your dataset is loaded AND activated ?

Try to activate just one first.

See picture.

Regards.

Hi,

I'm actualy experiencing the same thing in my project. Everything is well configured but I get the warning "Model Targets are not supported by Digital Eyewear."

In the project I only included the ModelTarget sample for Hololens from the Early Acces program.

What can I do to make Model Target work?

Regards,

lucabergonzi wrote:

Hi Strasza,

I tried with override detection position both checked and unchecked, but nothing happens. I didn't move anything. The only thing I can say is that the camera and the model target are placed in (0,0,0). 

Is there any problem with the Holotoolkit 2017.2.1.4 ?

Thanks

Luca

Sorry for missing your response Luca. When you run in playmode are you able to see the guideview object added to the scene? If so, can you try dragging it into the view to see if it's there at all?

Thanks,

Vuforia Support

Hi Strasza,

I think we all have the same problem as Lucas. The guideview is visible on the editor and working on play mod.

For me, it seems that the recognition work on Hololens but the guideview is still unvisible.

Regards,

Hi MParveau，

I have the same problem，The guideview  is not visible on Hololens with my own Model database， but it works well with the sample downloaded from the assetstore in Unity 。 you say that  your project can do the recongnition, so  i wonder how you can do the recongnition without the guidview to tell you the palce you should stand ,or

match the  shape and space of the real Model.

Try to position the overide detection position. That contains the camera where you can adjust your Hololens View..

Have you tried that ? 

Quote:

Sorry for missing your response Luca. When you run in playmode are you able to see the guideview object added to the scene? If so, can you try dragging it into the view to see if it's there at all?

Thanks,

Vuforia Support

Hi Strasza,

In playmode I'm able to see the guideview and it works perfectly. I tried also to activate the override detection position. The hololens does not track anything. I'm still struggling with that problem.

Best

Are you able to share a video and/or the dataset you are encountering this issue with? You can send it privately if preferred.

Thanks,

Vuforia Support

Hello Strasza,

I am having the same issues as guys here. I tried few Unity 2017 versions from .2 to .4. Now I am on latest non-beta 2018.



My data set doesnt get activated without doing that manual with load script you provided in some other thread. When I activate it manually I can see running object tracker with activated dataset inside it (runtime debug). I can even see the guide! 2D and even the 3D. But no object detection happens.

I can share the published dataset, it is attached.

Also, with the "Digital Eyewear doesn't support model target", I guess it doesn't apply for HoloLens? You would point that out already, right? Still it's not listed in supported devices for Model Targets.

The last thing to mention from my side is probably the error

"Failed to get spatial stage statics - can't retrieve or interact with boundaries! Error code: '0x80040154'"

But still the guide is shown. So the most important question is, if the guide is shown and tracker is running, is it my dataset that doesn't provide enough recognition quality?

Best regards, Miroslav

crankcz wrote:

Also, with the "Digital Eyewear doesn't support model target", I guess it doesn't apply for HoloLens? You would point that out already, right? Still it's not listed in supported devices for Model Targets.

Model Targets is supported on HoloLens, apologies for the confusion.

crankcz wrote:

But still the guide is shown. So the most important question is, if the guide is shown and tracker is running, is it my dataset that doesn't provide enough recognition quality?

Not all model targets are going to work. You'll need sufficient geometry and possibly some experimentation with the guideview. Looking at your model, it is fairly simple and doesn't have a lot of geometry. This likely is causing the main detection issues you are facing. I'd recommend attempting different guideviews that show it at more of an angle instead of a direct side view. Direct side views of many objects tend to have issues detecting the depth of the target and thus a lot of its geometry.

This article has additional information on what will make a good target: https://library.vuforia.com/articles/Solution/model-targets-user-guide.html

Thanks,

Vuforia Support

Hi everybody,

After few days of experimentation, I finally reached a solution for displaying the guideview in Hololens. Firstly, I set up the camera as the world center mode in the Vuforia Behaviour. Then, I reduced the size of my model target in order to keep the guideview within the Hololens FOV. The tracking is good but not perfect. I think that it's a matter of complexity of the model target and Hololens camera capabilities.

Thanks for the support and I hope that someone else will find this conversation useful.

Best 

Luca

Hi Luca,

  Thank you for sharing but I still can not find the guide view in Hololens, how did you fix the problem of Hololens FOV and could you please share the AR camera setting and Vuforia configuration to show us a correct workflow to set the model target?

Thank you so much for your help!

Mark

Hi,

we're having a similar problem with the Guide View in Vuforia 7.5.26.

2D Guide View appears in Unity editor, but not in the Hololens. When switching to 3D Guide View for some models it appears in the Hololens (but way to big) and not at all in the editor.

Could there be an issue with the format of the detection position in the model target generator. Does it matter whether one uses Landscape or Portrait for Hololens? 

Hello,

• Using the 3D guide view is highly recommended for HoloLens
• The HoloLens' RGB camera has an atypical field of view compared to typical mobile devices. Thus, a functioning guide view on a mobile device may be cropped on HoloLens. It is suggested that the guide view be repositioned to be "further away" (i.e. scaled down) due to this cropping.
• The HoloLens web camera is a landscape-oriented display. Thus, it is recommended to specify "Landscape" when creating a guide view in the Model Target Generator

Thanks,

Vuforia Engine Support