Oculus Rift DK2 + Leap Motion Orion + Unity setup questions

Apidcloud 2017-03-15 19:16:08 UTC #1

Good evening!

It's been a while since I have been around, but I am back and would like to try Orion SDK!

Thing is, I'm using a laptop with both intel graphics and a GTX 850M, and Oculus Setup isn't recognizing the HDMI - seems to be a known issue with Optimus... Any workaround? Can't seem to find a solution for this.

An alternative would be to use Oculus runtime 0.8 and Orion together. Is that possible? And would I need a specific Unity version?

Thanks!

Edit with 'basic' solution:

Install Unity 5.3.4f, as it seems to be the latest version implementing Oculus 0.8 runtime. Note that 5.3.4p1 already implements Oculus 1.3!
Create a new project and import Leap Motion Core Asset Orion 4.1.5
Change LeapServiceProvider to https://gist.github.com/Apidcloud/5727417c7f7c7b22343740e7d2281f83

Also note that LeapServiceProvider was only changed (a rollback to a previous commit) to fix compatibility issues, namely with Shader.SetGlobalMatrixArray. To fix further issues, provider mode and image time stamp were added. Thus, any further changes (see github) were not yet considered.

Working project at https://github.com/Apidcloud/Unity5_3_4f-Oculus0_8-LeapMotionOrionAssets4_1_5/

AlexColgan 2017-03-16 14:34:05 UTC #2

Not familiar with Optimus laptops, but know that Oculus may not work with machines on those specs.

Oculus runtime 0.8 would work with the Orion software, but of course that heavily constrains how many demos you can try. The older demos also aren't based on our LeapC API, which means that they aren't as optimized for VR.

As for the assets, you should be able to use the latest ones, though expect there may be a few errors if you use Unity 5.3.4p1 or higher.

Apidcloud 2017-03-16 15:11:46 UTC #3

Thanks for the reply!

I'm not sure if I'm missing anything, but leap motion VR Visualizer doesn't detect the HMD. I suppose Orion is only compatible with the new runtimes...

AlexColgan 2017-03-16 15:13:51 UTC #4

The VR Visualizer from the taskbar is definitely only compatible with Oculus 1.3+ because it's a Unity app that was built on that SDK.

Apidcloud 2017-03-16 15:22:19 UTC #5

Oh, that makes sense.

Then do I have to change anything in the LeapMotion_CoreAsset_Orion_4.1.5 unity package to make it work with Oculus runtime 0.8?

I'm going to downgrade Unity to the version you mentioned, as 5.4.5 might be using 1.3. I'll update this post when I do.

Thanks!

Apidcloud 2017-03-16 19:12:41 UTC #6

I have installed Unity 5.3.4p1, but there is the following error:
Assets/LeapMotion/Scripts/LeapServiceProvider.cs(301,14): error CS0117: `UnityEngine.Shader' does not contain a definition for SetGlobalMatrixArray

Which version was used to build Blocks demo?

Thanks!

AlexColgan 2017-03-16 19:41:48 UTC #7

Blocks for Oculus 1.3 was built in that version; but note that the Oculus integration for Unity in that version was bumped up to Oculus 1.3.

Apidcloud 2017-03-16 22:05:26 UTC #8

I didn't explain myself correctly. Which Unity version was used to build blocks 0.8 demo? I was able to run it just fine

Or when you say 'bumped up to Oculus 1.3' you mean that it supported 0.8 before?

That's likely the case. I have installed 5.3.4f, as it probably has oculus 0.8 implemented. Is there an easy rollback to the LeapServiceProvider used in the blocks 0.8 demo? I've taken a look over github, but there are many changes.

Edit:
Alright, I've edited LeapServiceProvider and it seems to be working! wohoo

I'll update the main post with the solution!

Thanks!

AlexColgan 2017-03-17 14:34:36 UTC #9

Nice! Appreciate you posting the solution as well.

Apidcloud 2017-03-17 15:26:24 UTC #10

Is there an alternative to Shader.SetGlobalMatrixArray? I believe it would be better to just use the latest version and just fix that specific compatibility issue.

Thanks!