Log in or register to post comments

Image Target recognizing in play mode but not in HoloLens

October 9, 2018 - 11:53pm #1

Hey all , im trying to develop an app for Hololens . The problem i'm facing here now is , when i try to test this app in unity playmode , its working well and good . But when the same app when deployed to HoloLens, the image targets are not being recognized . I have enabled my database , Internet and Webcam options in Build settings , Selected virtual reality SDK  as windows mixed reality but i dont know whats wrong with this . Any fix for this ? I need this to be fixed ASAP

 

 

Image Target recognizing in play mode but not in HoloLens

April 20, 2020 - 5:07pm #9

Hello, Have you find a soltuion to this?

Image Target recognizing in play mode but not in HoloLens

October 12, 2018 - 2:04am #8

TStb wrote:

Your ARCamera needs to be tagged as MainCamera

Tried it and still its not working . I tried hololens sample and its asking me camera permission but again its not detecting . On the other hand , my app isnt even asking me a camera permission . Wierd :(

Image Target recognizing in play mode but not in HoloLens

October 12, 2018 - 12:40am #7

Tried it and still its not working . I tried hololens sample and its asking me camera permission but again its not detecting . On the other hand , my app isnt even asking me a camera permission . Wierd :(

 

Image Target recognizing in play mode but not in HoloLens

October 11, 2018 - 10:23pm #6

Your ARCamera needs to be tagged as MainCamera

Image Target recognizing in play mode but not in HoloLens

October 11, 2018 - 10:58am #5

MiriamPadberg wrote:

Hello,

I use the Unity 2018.2.11f1 with Vuforia 7.5.20. If I delete Main Camera I couldn't reconize images.



 

 

Anything am i missing , The main camera didnt work for me man , Maybe i will try it again tomorrow .

AttachmentSize
Image icon Capture.PNG408.02 KB
Image icon Capture 2.PNG345.39 KB
Image icon Capture23.PNG361.46 KB
Image icon Captured.PNG314.04 KB
Image icon cAzsrza.PNG179.01 KB
Image icon dsa.PNG206.72 KB
Image icon eacC.PNG336.18 KB

Image Target recognizing in play mode but not in HoloLens

October 11, 2018 - 12:18am #4

Hello,

I use the Unity 2018.2.11f1 with Vuforia 7.5.20. If I delete Main Camera I couldn't reconize images.



 

Image Target recognizing in play mode but not in HoloLens

October 10, 2018 - 11:50pm #3

Hey man thanks for the reply

 

For new vuforia sdk we will not be needing Main camera as AR camera has inbuilt holo support .

I could see my canvas but when image target is shown its not getting recognised . :( 

Im on a deadline now and this occurs :(

Image Target recognizing in play mode but not in HoloLens

October 10, 2018 - 7:56am #2

Hello,

the last days I tried to overlay an image target by an image... and need a lots of try-and-error-steps.

At least these settings works for me:

1. Main Camera: Tagged as main camera, Pos: 0-0-0, Rotation 0-0-0 and Scale 1-1-1; Clipping 0.85;

2. AR Camera: untagged; Child of Main Camera, Position, Rotation and Scale like Main Camera

3. Project Settings: Quality: all levels to "very low"

   Player: Windows: Scripting Backend: .NET; Publishing Settings: Internet Client, InternetClientServer, Pictures Library, Webcam, Microphone, Spartial Perception and Low  Level Devices

   XR-Settings: Virtual Reality Support with Windows Mixed Reality and Vuforia Support

4. Vuforia Configuration: Camera direction: Default; Digital Eyewear: Device Type: Digital Eyewear; Device Configuration: Hololens

5. Build Settings: Universal Windows Platform with Target Device Hololens, Build Type D3D, and activated Unity C#-Project



After building via Unity and opening in VB it is possible that you get some errors because of missing textmeshpro-scripts.

Then I had to close VB and create a new folder named "com.unity.textmesh" in the Package directory of your Unity project folder. After that I had to copy all elements of c:\Users\<Username>\AppData\Local\Unity\cache\packages\packages.unity.com\com.unity.textmesh@1.3.0 in this new folder and restart VB again like descriped.



Hope it helps.

Log in or register to post comments