Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Fix compatibility issues with Vuforia: GazeTransform initialization.

See original GitHub issue

What I’m doing

I’m using Vuforia framework in combination with Hololens Toolkit and for some reason the DefaultCursor.prefab that I’m using (or any other cursors) the position is set somewhere else.

How did I found/investigated

At first I thought that Cursor.cs would be the main cause of setting the position different but after further investigations I found out that in the GazeManager.cs the GazeTransform receives Camera.MainTransform at protected override void Awake() and this sets the position a bit different (moves from center)

The fix

The fix is easy, I’ve moved GazeTransform from Awake to Start method and everything is working correctly right now.

I would like to know if i can make a pull request regarding to issue.

Issue Analytics

State:
Created 7 years ago
Comments:9 (4 by maintainers)

Top GitHub Comments

1reaction

moisoiucommented, Feb 21, 2017

Have fun !

For the moment it’s a bit challenging, but in time (as more and more people start to use hololens) it’s going to get much more easier.

P.S If you want to play with Vumarks from Vuforia, before anything don’t forget to refill your coffee cup 😃

Regards

1reaction

moisoiucommented, Feb 21, 2017

Yes, and everything was working fine.

Regarding to any other scripts, I’m almost sure that Vuforia framework with ARCamera.prefab or VuMark.prefab might have an impact on changing the position, because If I don’t use it (at all, removing the .dll so it doesn’t load at startup) the position is staying in the middle (correctly)

I’ve did the PR here