Orion+Core 4.3+InteractionEngine not working in Unity 2017.3

unity

orion

Tags: #<Tag:0x007f26d8393298> #<Tag:0x007f26d8393130>

abhiayan 2017-12-27 17:06:03 UTC #1

Hands going through the object. Can not grab objects.

Getting one error in console, which can be seen in the screenshot.

Note- I am able to use the Blocks demo perfectly, therefore guessing it has something to do with the editor.

Using Oculus Rift+Touch.

Any suggestions?

onurgunan 2017-12-28 21:36:39 UTC #2

Got same issue also.

camdenbock 2017-12-29 02:17:16 UTC #3

We had a similar issue. It seemed to work to clone the repository from GitHub, switch to the 2017.3 branch, and build the assets from there.

Then, in your project/repo import the assets. Seems to work for both Core and Interaction Engine.

I'll see if I can post the asset files.

camdenbock 2017-12-29 02:41:12 UTC #4

The asset packages are attached in a zip below.

https://drive.google.com/a/maine.edu/file/d/16Eppukbkr7BviNO2m1Me_iqddSR3Pkxi/view?usp=sharing

Make sure to delete ALL of the previous Leap Motion assets before loading, especially stray DLLs. Also, our DLLs didn't import into the correct folder and had to be moved.

This should be a temporary fix until they release something new:

Let me know if you have any questions! There were a few bumps along the way that I can't remember at the moment.

abhiayan 2018-01-02 10:55:12 UTC #5

Thanks!
I'll try this and let you know.

abhiayan 2018-01-02 13:01:46 UTC #6

Not working. Getting these errors.

Started a new project and imported all the packages from your google drive folder into it.

Can you write a bit more about which dll files you had to move for it to work?

camdenbock 2018-01-02 18:39:20 UTC #7

it looks like you still have the old DLLs installed. These aren't always removed when using Unity's package management.

Make sure to delete the LeapMotion folder and the LeapMotion dlls in /Assets/Plugins/ before importing the packages. (You should be able to delete those and then reimport.) EDIT: I see now that you are using a new project. See post below.

EDIT: This isn't a DLL problem, but a prefab problem in the example scene

I'm not sure how this is supposed to be setup, but I have it working with all Dlls removed fromt he /Assets/Plugins/ (where they were by default), and the dlls imported into /Assets/LeapMotion/Core/Plugins/ and ONLY the InteractionEngine dll in the /Assets/Plugins/

As far as I know LM includes the following Dlls:

InteractionEngineUtility
LeapC#.NET3.5
LeapC (x86)
LeapC (x86_64)

camdenbock 2018-01-02 18:42:14 UTC #8

I would also be cautious about installing all of the LM assets. We currently only use LM Core and LM Interaction Engine.

If I recall, some of the assets are for legacy support only.

EDIT: I'm getting the same profiler error when working in a new project with only the two modules.

camdenbock 2018-01-02 19:13:49 UTC #9

It appears (when importing only Core and InteractionEngine) that this is not a problem with the dlls or the assets, but a problem with the example scenes not being updated.

To resolve:

Delete the LM_HeadMountedRig from the scene.
Drag the LM_HeadMountedRig prefab into the scene
Drag the InteractionManager prefab into the scene.
Child the InteractionManager (in scene) to the LM_HeadMountedRig (in scene)

I have a working copy of (this scene) in a unity project linked below.

https://drive.google.com/open?id=1CG0BQvl2ibe3wY_L47gkeUhlW5y4jgO7

jameskane05 2018-01-02 19:50:41 UTC #10

Unfortunately not fixing it for me at this time... Same errors with your LM_Test project.

jameskane05 2018-01-02 20:09:39 UTC #11

UPDATE: Actually, I got it running. As you originally suggested, just cloning straight from github, then switching to the upgrade-2017.3 branch, then opening the project in Unity 2017.3. Everything's working again and smooth. Cheers!

tomy93 2018-01-08 16:40:31 UTC #12

Hi! I can't find that branch, just upgrade-2017.2 D: I'm doing something wrong? not an expert on git...

jameskane05 2018-01-08 19:49:06 UTC #13

Looks like as of last week they updated the master branch to work with 2017.3. Hope that helps!

tomy93 2018-01-08 21:52:23 UTC #14

Thanks a lot! but now I'm having this problem:

I'm using Unity 2017.3.0f3, and master branch. This error is when playing any InteractionEngine demo, any interaction behaviour are not working.

ccjenseninl 2018-01-12 20:15:03 UTC #15

I am having the same problem with the NullReferenceException error.

tomy93 2018-01-13 11:34:53 UTC #16

Hi, I checkout to this branch and everything is working fine https://github.com/leapmotion/UnityModules/pull/931, master was not working for me 5 days ago.