Orion SDK Update

Tags: #<Tag:0x00563fd3245c70> #<Tag:0x00563fd32447a8> #<Tag:0x00563fd323f820>

Merglasch 2018-06-26 10:46:35 UTC #22

@AlexColgan Yeah I've enabled that somewhere inbetween as an effort to solve these problems. I went in to disable it, but it was already disabled. I've reenabled, saved, exited setting, reopened settings and disabled it, saved, exited settings just to be sure. Weirdly enough now my data frame rate has climbed up to 115. It's even weirder as I had the 43 data framerate already before I switched on low resource mode and it stayed after I switched it off. But now switching it on and off again fixed it, so I guess yay?

AlexColgan 2018-06-26 14:12:36 UTC #23

I'll go with yay Perhaps the setting was stuck for some reason... we're likely going to pull that option from future builds since there are other ways to run optimally on low-powered computers than simply dropping the framerate.

_mike 2018-07-13 21:41:28 UTC #24

Just tried the Orion SDK update. Everything works great so far, except 1 thing:
- If you press Play in Editor without a LEAP device attached, when you press Stop Unity will completely hang and freeze. You have to kill it via Task Manager. Behaviour is consistent across several machines.

HOTTHANDS 2018-07-17 21:59:49 UTC #25

Thanks for that head up -mike!
Which version of Unity?

HOTTHANDS 2018-07-17 22:12:12 UTC #26

Hi Alex,
We have tried to set settings using the panel and find they do not "stay" - and it has been mentioned in various threads that defaults have changed... We would like to control these programmatically.
1. Is there an configuration guide specifically for 4.0 and
2. What is the best way to set LEAP for use with Unity 2018 executables... in a non VR headset environment.
Is it better to launch a startup routine for LEAP to assure it is running optimally and then launch Unity executable for our users
or Should we embed it in the startup or menu of the unity program - like a manual start for LEAP with the settings we need?
Thanks in advance!

_mike 2018-07-17 22:49:54 UTC #27

using 2017.4.4f1 LTS

HOTTHANDS 2018-07-18 00:47:10 UTC #28

Thanks for sharing.

We shifted from 2017 1 to 3 and think we are going to settle for 2017.3 or 2018. Not sure why the team skipped over 2017.4 but the 2018 provides a better C# alignment with Microsoft for inter-reliability of programming, so we are trying it.

We are non-visor, so we do not use those SDK...which might impact...
I am beginning to wonder if Microsoft's Plug and Play, 3D services or Windows Hello cameras, etc. might be tweaking LEAP which on my system always winds up as a USB Camera with a 2006 Microsoft Driver.

In contrast, my Intel D400 series cameras for computer vision always appear as imaging devices and they had been firing up for imaging (not hand tracking) with better reliability than LEAP seems to fire up. But, Intel is stepping away from implementations and solid connections with Unity3d and edging toward being simply a 3D device...Hopefully LEAP has a best practice for us because I don't really want to do the math

I am stripping down a machine and reloading to test some builds this week.
Thanks to your diligence, I have added you potential bug to my checklist.

I will post what I discover!