Green light on device and good device status in control panel but tracking not working

[alicelhjoens]

Recently bought a leap motion and ran through the installation setup and the device shows a green light on the side and the control panel reports that it's working fine but nothing shows in the visualizer and when trying to calibrate the device it won't paint the screen even when pointed at a mirror.

If it's any help, the visualizer reports that the render fps is around 20 (which is weird since it should be running on a 970), and that the data and device fps are both 0. The logs also show nothing except "firmware is up to date", "leap motion controller detected" and "tracking resumed" so there aren't any errors being reported.

Attached some relevant screenshots

[dankirby]

Hi Alice, which version of our hand tracking SDK are you using?

Please can you try restarting the Leap Service by opening the Services App scrolling down to LeapService and then stopping and restarting this.

In the diagnostic visualiser are you able to see the direct camera feeds or are these not visible?

Within the Leap Motion Control Panel please can you also check that Robust Mode is not enabled under the General Tab and let me know the outcome of these tests?

[alicelhjoens]

^^The services thing worked to fix it thank you!! I'd read about it being a common issue and tried right click -> restarting the service which did nothing. Right click stop then starting it instead fixes it!!

[dankirby]

Great to hear, thank you for letting me know!

[Klaskak]

Hello,

I’m running into a very similar issue. I’m using Gemini V5.2 and the icon is green and control panel states that the device is connected and the tracking service is idle. When I run the visualizer the screen is gray and the device fps is zero(no video feed from the device). Stoping and starting the service does not work I tried reinstalling but that didn’t help either.

One thing I do know is that I tried the V2 installer and I was running into the same issue with the visualizer. But after running the driver installer from the LeapMotion/drivers folder the visualizer worked flawlessly.

Any help resolving this issue would be greatly appreciated.

[dankirby]

Hi @Klaskak, thank you for reporting this. To confirm, is the Ultraleap tracking Service currently showing that is is running?

Please can you stop the service and then try to start the service manually from the location below and let me know if you see any errors?

C:\Program Files\Ultraleap\TrackingService\bin\LeapSvc

[Klaskak]

Hello dankirby,
Yes the tracking service is reporting that it is tracking. I tried to stop the tracking service and restart It per your instructions. But sadly this did not resolve the issue. I have attached some screen shots and the output from the service loge.

.

OUTPUT FROM THE LOG:

[14:04:11.304980500] [3216] [console] leap::fake::DeviceManager::DeviceManager()#113: missing default_device.json
[14:04:11.317173500] [3216] [console] leap::server::Server::Server()#56: Starting broadcast server host at 127.0.0.1:1024
[14:04:11.317826900] [3216] [user] leap::uvc::DeviceManager::initialise()#116: Doing UVC tracking initialisation
[14:04:11.319507700] [7984] [console] BroadcastServerHost::StartHost()#60: Running telemetry server on 127.0.0.1:1024
[14:04:11.319655200] [3216] [console] ServerListenerImpl::ServerListenerImpl()#305: ServerListener started (5.2.0.0 - 1165930e)
[2021-10-29 14:04:11] [application]
[2021-10-29 14:04:11] [connect] WebSocket Connection 127.0.0.1:49858 v13 "WebSocket++/0.8.2" / 101
[2021-10-29 14:04:11] [connect] WebSocket Connection 127.0.0.1:49862 v13 "WebSocket++/0.8.2" / 101
[14:04:11.642241200] [7064] [console] leap::SingleLeapC::make_connection()#86: make_connection() ...
[14:04:11.692436500] [7064] [console] leap::SingleLeapC::make_device()#256: start tracking runner ...
[14:04:11.693160300] [7064] [console] `anonymous-namespace'::SingleLeapCConfig::SingleLeapCConfig()#114: Loaded config, allow images true camera orientation fixed-normal
[14:04:11.693413700] [7064] [console] leap::TrackingRunner::TrackingRunner()#32: Created TrackingRunner, default mode 1
[14:04:11.693610400] [7064] [console] leap::TrackingRunner::start()#63: Attempting to create tracker: 1
[14:04:11.735173600] [7064] [console] leap::ModelManager::getCandidateModels::::operator ()()#122: tflite is an available engine
[14:04:11.735430300] [7064] [console] leap::ModelManager::getCandidateModels::::operator ()()#122: aot is an available engine
[14:04:11.736474600] [7064] [console] leap::ModelManager::getCandidateModels()#134: Archive ldat-39154.ldat does not support tracking mode Hmd
[14:04:11.736655900] [7064] [console] leap::ModelManager::getCandidateModels()#134: Archive ldat-38290.ldat does not support tracking mode Hmd
[14:04:11.737581700] [7064] [console] leap::ModelManager::getCandidateModels()#150: Model windows_aot1 does not support resolution 640x240 (any: false)
[14:04:11.738376500] [7064] [console] leap::ModelManager::getCandidateModels()#176: Archive ldat-37931.ldat does not support os Windows os_api_ver vc142 or arch x86_64
[14:04:11.739077700] [7064] [console] leap::Evaluator::create()#806: No models. Throwing..
[14:04:11.740049500] [7064] [console] leap::Evaluator::create()#855: An exception occurred creating the Evaluator: No candidate models found for this environment.
Capture device = LMC
Tracking mode = Hmd
Available engines: tflite aot
[14:04:11.741155400] [7064] [console] leap::TrackingRunner::start()#63: Attempting to create tracker: 2
[14:04:11.749715500] [7064] [console] leap::ModelManager::getCandidateModels::::operator ()()#122: tflite is an available engine
[14:04:11.750055900] [7064] [console] leap::ModelManager::getCandidateModels::::operator ()()#122: aot is an available engine
[14:04:11.750805300] [7064] [console] leap::ModelManager::getCandidateModels()#134: Archive ldat-39154.ldat does not support tracking mode Hmd
[14:04:11.751634100] [7064] [console] leap::ModelManager::getCandidateModels()#134: Archive ldat-38290.ldat does not support tracking mode Hmd
[14:04:11.752265900] [7064] [console] leap::ModelManager::getCandidateModels()#150: Model windows_aot1 does not support resolution 640x240 (any: false)
[14:04:11.753037800] [7064] [console] leap::ModelManager::getCandidateModels()#176: Archive ldat-37931.ldat does not support os Windows os_api_ver vc142 or arch x86_64
[14:04:11.759031700] [7064] [console] leap::Evaluator::create()#806: No models. Throwing..
[14:04:11.759942500] [7064] [console] leap::Evaluator::create()#855: An exception occurred creating the Evaluator: No candidate models found for this environment.
Capture device = LMC
Tracking mode = Hmd
Available engines: tflite aot
[14:04:11.761418900] [7064] [console] leap::TrackingRunner::start()#63: Attempting to create tracker: 3
[14:04:11.772791100] [7064] [console] leap::ModelManager::getCandidateModels::::operator ()()#122: tflite is an available engine
[14:04:11.773062600] [7064] [console] leap::ModelManager::getCandidateModels::::operator ()()#122: aot is an available engine
[14:04:11.773975300] [7064] [console] leap::ModelManager::getCandidateModels()#134: Archive ldat-39154.ldat does not support tracking mode Hmd
[14:04:11.774712600] [7064] [console] leap::ModelManager::getCandidateModels()#134: Archive ldat-38290.ldat does not support tracking mode Hmd
[14:04:11.775440100] [7064] [console] leap::ModelManager::getCandidateModels()#150: Model windows_aot1 does not support resolution 640x240 (any: false)
[14:04:11.776166300] [7064] [console] leap::ModelManager::getCandidateModels()#176: Archive ldat-37931.ldat does not support os Windows os_api_ver vc142 or arch x86_64
[14:04:11.776885700] [7064] [console] leap::Evaluator::create()#806: No models. Throwing..
[14:04:11.777659600] [7064] [console] leap::Evaluator::create()#855: An exception occurred creating the Evaluator: No candidate models found for this environment.
Capture device = LMC
Tracking mode = Hmd
Available engines: tflite aot
[14:04:11.778474000] [7064] [console] leap::TrackingRunner::start()#69: create_hand_tracker fail
[14:04:11.786508100] [5036] [console] leap::SingleLeapC::set_tracking_mode()#218: Requesting tracking mode update for runner 1 mode 2
[2021-10-29 14:04:11] [connect] WebSocket Connection 127.0.0.1:49863 v13 "WebSocket++/0.8.2" / 101
[2021-10-29 14:04:12] [connect] WebSocket Connection 127.0.0.1:49864 v13 "WebSocket++/0.8.2" / 101
[14:05:03.689869900] [7064] [console] leap::SingleLeapC::set_tracking_mode()#218: Requesting tracking mode update for runner 1 mode 2
[14:05:03.690301800] [7064] [console] leap::SingleLeapC::set_tracking_mode()#218: Requesting tracking mode update for runner 1 mode 2
[14:05:03.694926000] [7064] [console] leap::SingleLeapC::set_tracking_mode()#218: Requesting tracking mode update for runner 1 mode 2
[14:05:03.926138500] [7064] [console] leap::SingleLeapC::set_tracking_mode()#218: Requesting tracking mode update for runner 1 mode 2

[natemakesgames]

I am having the same issue as Klaskak, I think. I get that problem when I sleep my PC, and the only fix seems to be restarting the whole computer. The problem appears to be with the tracking software itself, because the visualizer breaks as described above. I did not have this problem with the 5.0 preview.

[Klaskak]

@natemakesgames Thanks for your reply. I can confirm that the issue does not go away after a restart. This pc is set to never fall asleep so I can assure you that waking is not the issue. The issue is still present right after start up.

[natemakesgames]

My log has numerous errors when this happens related to "Camera is not streaming".

[natemakesgames]

One more thing about this: unplugging and replugging the device seems to fix my issue in many cases. I don't recall having this issue often in 5.0 preview and below, but now it consistently happens every time I sleep the PC (visualizer is light grey, software tracking status same as Klaskak, restarting tracking software doesnt work, "Camera is not streaming" errors show in log).

[Klaskak]

For me, unlike @natemakesgames I was never able to get the v5 to work. Unplugging/replugging, rebooting, reinstalling, restarting the service do nothing to resolve the issue. Meanwhile, v4 works flawlessly.

[broots]

@Klaskak v5.3 works on my desktop machine running Windows 8.1 Pro but shows a gray screen and no hand model in the Visualizer on my laptop running Windows 11. I can get v2.3.1 running in Windows 11 with the bug fix for Windows 10 but would much rather be running v5.3 on both machines for development in Unity.

Has anyone had luck with v5 in Windows 11?

[dankirby]

Hi @natemakesgames and @Klaskak,

please can you send your PC Spec including CPU and the Tracker Log to support@ultraleap.com and I can help you to diagnose this and resolve the issue

The tracker log can be found here: C:\ProgramData\Ultraleap\HandTracker\Logs\tracker_log