HoloLens, Model Targets and Guide view issues

By shaddad on Thu, 02/01/2018 - 21:30

Hi,

I am experimenting with Model Targets and initially I was having some success, but now I am having 2 problems 1) Guide View not appearing and 2) Model not detected.

My first use case was to use a CAD model for my iPhone to create a model target and deploy to a Galaxy S8 and a HoloLens. With the Galaxy S8 the workflow was straight forward and worked fine using the recommended 2D Guide View. When I tried running it on the HoloLens, the 2D Guide view didn't appear. I switched 3D Guide View, and then the Guide View did appear and I was able to detect and track my iPhone. Yay!

Next I moved on to a CAD model of my car. I've created the model target, but when I deploy to the HoloLens, I do not get a Guide View to appear, whether 2d or 3D. Subsequently, I can't seem to get it to detect my car. I would think the car use case would actually be easier than the iPhone, given it has much more points that I would think could be used for detection. If I run the same scene on the S8, it will detect my car, but the car does not render in the proper location (it renders at an angle as seems gigantic). I've verified the measurements are accurate in the Vuforia Model Target Generator has the correct units and axis for up based on the model. In Unity, the Dataset has the correct measurements too.

Does anyone have any ideas what could be going on? Does anyone have any luck getting the Guide View working properly with HoloLens? Also, are there any links to an explanation between the 2D and 3D guide view?

Is there any way to rig the editor or the device to fake detection to more easily debug this?

Hello,

I have the same problem with Model Targets and HoloLens.

I tried the Viking Lander sample and other custom targets but when I deploy to HoloLens it does not show any Guide View.

I tried with Unity patch 2017

I tried with Unity patch 2017.3.0p4, ModelTargetGenerator-7-0-47. and it working. try that

Thanks

eswar

Hello,

I'm also having the exact

I'm also having the exact same issue @pflament. The guide view does appear but it's unsteady and it appears to glitch and certain angles. I can only see it from 85° to 40°. When I pan myself left or right I can sourd of make it to the target but this is not ideal.

Hello all,

A 3D guideview must be used when deployed on the HoloLens.

Thanks,

Vuforia Support

Strasza wrote:

[quote=Strasza]

Hello all,

A 3D guideview must be used when deployed on the HoloLens.

Thanks,

Vuforia Support

[/quote]

I tried both 2D guide view and 3D guide view But same issue

What do you mean by "it's

What do you mean by "it's unsteady"?

Apart from the angle disappearance problem my 2D guide view is fine (with me the guide view disappear at 0° 90° 180° and 270° on the Y axis )

Pierre

Hello,

As eswarkumar told me, I have installed Unity 2017.3.0p4 that comes with Vuforia 7.0.47 and I still can't see any guide view.

Hello,

It seems that they have solved the problem with the guide view and Hololens in the last Unity 2017.3.1p1 patch and the updated sample.

Note that it only works in a Hololens device, not in the emulator.

Hi all,

I have created a model target dataset using the ModelTargetGenerator software but have been unable to display the guide view on the HoloLens. Part of my problem is that I don't know what file to put in the 'Custom 3D GuideView model' field.

jpoffley wrote:

[quote=jpoffley]

Hi all,

Hi Strasza,

Thank you for your response. I have now downloaded Unity 2017.3.1p1 and am trying to simply get the HoloLens Sample working (found at https://developer.vuforia.com/downloads/beta).

Hi jpoffley,

I've seen this issue when using certain versions of Visual Studio when building for HoloLens with Unity. Can you tell me which version of VS you are using and I can compare it against mine?

Thanks,

Vuforia Support

Hi Strasza,

Apologies for not responding sooner. I have updated to the latest Visual Studio Community version (15.6) and am still seeing the same error message - attached.

Can you think of any other possible solutions to resolving this error message?

Many thanks