Log in or register to post comments

Digital Eyewear not working

December 20, 2018 - 3:06pm #1


Here is my setup:

  1. I'm using the latest version of the LTS Unity 2017.4.17f1.
  2. I've imported the Digital Eyewear Sample from the Asset Store.
  3. I've changed the Build Settings to Universal Windows Platform for Hololens.
  4. In Edit > Project Settings > Player Settings > XR Settings, both Virtual Reality Supported and "Vuforia Augmented Reality" boxes are checked.
  5. In the scene, if I open the ARCamera and look in the Inspector, the clear flags is set to solid color, background is 0,0,0,0, and the clipping plane is set to 0.85 as recommended by Microsoft.
  6. If I open the Vuforia configuration from within the ARCamera inspector, my Vuforia app license key has been added. All other settings have not been changed.
  7. I hit "build" from inside Unity, then open the .sln file with Visual Studio 2017.
  8. My build settings are "Debug" "x86, and "remote machine". 
  9. I select Debug>Start Without Debugging.
  10. Build and deploy both succeed. The app asks for permission to use my camera and microphone. I say yes.
  11. When I look at the Vuforia images (Drone, oxygen, Astronaut, etc., all printed without scaling), nothing happens.
  12. I can see the cursor at all times. No images ever pop up from the image targets.

This messages is printed out to Visual Studio:


Assertion failed on expression: 'IsMatrixValid(matrix)'

(Filename: C:\buildslave\unity\build\Runtime/Camera/Camera.cpp Line: 3484)

The program '[1280] HoloVuforia.exe' has exited with code -2147483645 (0x80000003).


Any idea what it means or how to get a successful demo? I just want to use Vuforia target tracking on my HoloLens.



Digital Eyewear not working

March 31, 2019 - 3:47pm #5

Thank you, i struggled for days and this was the solution!

Digital Eyewear not working

January 9, 2019 - 10:57am #4

Can you at least remove dead documentation? Or put a warning up at the top with a link to the correct latest version? And PLEASE don't release a new version of Vuforia until all the documentation has been updated.


This was very very painful and frustrating. 

Digital Eyewear not working

January 2, 2019 - 12:36pm #3


Apologies for any inconvenience you may have faced. We continue to work to improve our portal documentation and appreciate your feedback.


Vuforia Engine Support

[Solved] Digital Eyewear not working

December 21, 2018 - 1:26pm #2

I got this working. The settings for the AR Camera are incorrect in the provided Digital Eyewear files. Instead of the Clipping mask set to these incorrect values: Near: 0.85, Far: 5. They need to be set to the correct values of Near: 0.05, Far: 2000 (which is the default when you add a new AR Camera yourself by doing GameObject > Vuforia > ARCamera, which is how I figured this out).


Semi-useful documentation (it's all varying degrees of out of date. I'm honestly shocked at how badly this stuff is documented given that Vuforia claims to be the number one AR/VR Image tracking tool available):


  1. https://library.vuforia.com/articles/Solution/Working-with-the-HoloLens-sample-in-Unity
  2. https://library.vuforia.com/content/vuforia-library/en/articles/Solution/introduction-model-targets-unity.html
  3. http://www.appzinside.com/2017/06/22/how-to-integrate-the-vuforia-platform-with-your-hololens-projects/


Absolutely not useful documentation that is incomplete, confusing, out of date, and basically just a collection of dead or useless links:

  1. https://library.vuforia.com/articles/Training/Developing-Vuforia-Apps-for-HoloLens
  2. The screenshots here would be useful if they were at all up to date: https://library.vuforia.com/content/vuforia-library/en/articles/Solution/Working-with-Digital-Eyewear-in-Unity.html
  3. Worst one: https://library.vuforia.com/articles/Solution/Working-with-the-HoloLens-sample-in-Unity
  4. A nightmare: https://library.vuforia.com/articles/Training/getting-started-with-vuforia-in-unity.html

Why are there so many and why are they all out of date? Why do none of them specify when they were written, or have a pointer to the latest? Why do they link to each other in a never-ending labyrinth of incomplete documentation?


This really shouldn't be this badly done.

Log in or register to post comments