Urgent: Leap Interaction Engine not working in Build

[Tom_LeFx]

Hi there,

we have a huge issue here right now. We are using the Leap Interaction Engine Modules in Unity to build a VR Application.
In Editor, everything works as expected, but when we build it, there are no controllers/hands at all.
It's like something get's lost in the Build process, although this runs through without any complications.

Even the example scenes show the same issue. Working like a charm in Editor, no Hands/noInteractions in Build.

We run Unity 2017.3.1....it does not matter, if Orion SDK is installed on the PC we use to test or not...the issue remains the same.
We are only using the HTC Vive part of the assets...SteamVR is imported as assets as well, but in the scene there is no SteamVR component present.
Anyone else got this? Can someone point us into the right direction?

[Tom_LeFx]

Ok...we found the solution...and it's kinda ridiculous...so i leave it here:

Leap Interaction Engine has some issues on startUp, when it tries to locate controllers. If the Vive Controllers are off, for example, then it will never find them, after they are turned on, until you restart the level/app

Furthermore, Leap Interaction Engine seems to need some time/has a timing condition on startup...so it really likes to have a splash-screen or anything, that delays the app start a bit. If you directly jump into the VR-Level after starting the app, you will, most likely, end up like us, without active controllers.

Our quickfix was, to re-enable the unity splashscreen with its 5 second delay.
This should really get some attention or at least some documentation please....

[AlexColgan]

Thanks for posting a report on our GitHub -- a fix is in the works.

Issue: Interaction Engine: Controllers are not found, when app starts too fast