Controller not showing as connected with new Orion VR beta installed

[pizzy00]

Just wanna say I had the same issue, gonna try fixes

[swoo]

No worries, glad to hear you got it straightened out!

[sbiegun]

I was having a similar issue yesterday after installing Orion. I contacted Michael in support and he ran me through the troubleshooting to figure out what the issue was. We determined that the device was dead and that it may be a hardware issue. This morning, I turned my PC back on, plugged the device in, and it worked. Not sure if it helps, but the only change between now and then is that I left my PC off for an extended period of time. Hopefully the problem doesn't reoccur, because I still don't know what the cause or solution is.

[sdemar]

By the way, the new build is amazing. Great work guys! Was cool before, now its just, well, amazing

[KookyBone]

is

hi,

i just installed orion and it worked perfectly fine in the beginning. All Demos were working correct but after starting the 6th demo or so again the hands were up-side-down. So i restarted the pc. After that i had the same problems you were writing. First it shows connected and i can calibrate it, but all demos say it is disconnected and no hands were shown. the lights went off after af few secounds. so while calibration works everything other doesn´t. after a restart now it shows disconnected... seems there is problem with the software for me!

But in the 30 mins it works fine it was really great by the way

[KookyBone]

Maybe i found the solution!!!

When i restarted the pc for the 5th time or so the motion leap started working again. it some fingerprints on it so it reminded me that maybe now it works. And it did... normally as before BUT when i started a VR-Demo what now didn´t work was the oculus DK2. It says device is not detected. So i cheked the usb ports and detected that they both connected on the only two usb 3.0 ports of the pc. I thaught when one device worked and the other stops and if the other works then the other stops, than maybe it is problem with the usb controller. So i swiched the oculus onto the usb 2.0 port and voila... both works fine now. So maybe there are conflicts with some USB-Controllers

[doomep]

I had exactly the same problems with the message "Device Status Offline", but quickly resolved by these steps:

1: Open task manager.
2: Go to Tab Services
3: Right click on Leap Motion Service.
4: Click on option "Open Service".
5: In the new window "Services", locate "Leap Service" and click right.
6: In Recovery Tab, select first and second failure to restart the service, and third option not to take action.
7: In the General tab, select "Automatic" startup type.
8: Click Start in the "Service status" button, and click OK.

TESTING:
Notes: Close or minimize windows, and verify that the icon leap in motion has changed to green, otherwise restart the PC.

Notes: Right-click on the icon leap motion, select setting, and check the tab "Troubleshooting" all status "Device Status" are green. Close the window.

Notes: Right-click on the icon leap motion, and select "Visualizer" option. Place your HMD in your head and move your hands in front of you.

I hope these steps help up fast and try!

---

SPANISH:
Tuve exactamente los mismos problemas con el mensaje de "Estatus Dispositivo Desconectado", pero lo solucione rápidamente haciendo estos pasos:

1- : Abrir task manager.
2: Ir al Tab Servicios
3: Click derecho sobre Leap Motion Service.
4: Click en opción "Open Service".
5: En la nueva ventana de "Services", localizar "Leap Service" y hacer click derecho.
6: En Recovery Tab, seleccionar primera y segunda falla para que reinicie el servicio, y en tercera opción que no tome accion.
7: En el tab general, seleccionar "Automatico" en tipo de inicio.
8: Click inicio en el boton "Service status", y click en Ok.

PRUEBAS:
Notas: Cerrar o minimizar las ventanas, y verificar que el icono de leap motion en el ha cambiado a verde, en caso contrario reiniciar la PC.

Notas: Click derecho en el icono de leap motion, seleccionar setting, y verificar en el tab "Troubleshooting" que todos los status de "Device Status" están en color verde. Cerrar ventana.

Notas: Click derecho en el icono de leap motion, y seleccionar opción "Visualizer". Colocar tu HMD en tu cabeza, y mover tus manos frente a ti.

Espero que estos pasos ayuden a subir rapido y probar!

[iko79]

Baesik's solution did the trick for me (thanks!). Tried to restart the LeapService and all the suggested solutions here, even tried re-installing the SDK and all, wouldn't work. Manually reinstalling the drivers, however, made it work.

[agudmund]

I am having the same issue with connecting it after upgrading to the latest Windows 10 Creator version (Insider version). the device works fine on my iMac but I just tried setting it up on my ultrabook and although the service is fine (have tried restarting it both the machine and the service explicitly)
The software log is empty apart from a single line saying the service is connected and the settings UI shows the green banner on the service and a red banner on device connection.
The windows event logs themselves show a clear COM Service error

The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
{D63B10C5-BB46-4990-A94F-E40B9D520160}
and APPID
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
to the user {omittted} SID ({omitted}) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
After having tried digging in the component service manager I'm afraid how to enable this permission is a bit out of the range of my skillset so any advice is greatly appreciated, it sounds like a simple permission error asking for elevated privileges, running the visualiser directly as administrator shows the same effect and error.

[msitarzewski]

This worked for me! Thank you so very much. Note, to get to this point, I also tried an installation on my MacBook Pro with V2 and it worked flawlessly. That gave me the data I needed to pursue the drivers option.

[agudmund]

Thanks! That worked a charm, The software is installed in ./Program Files x86 but inside the drivers directory there is a 64 bit driver, once I clicked the 64bit .inf file and installed the certificate next to it the device started working quite nicely.