LeapUnityExtension.cs not found in unity assets

[arshh]

Hello,
I recently started using leap motion and instead of trying out V2, I installed Orion beta and then imported the assets into Unity project. Then I tried the scene that came with it (without VR). Then I tried to write a simple script and when I compiled it. Monodevelop started showing errors in the LeapUnityExtension,cs, that the LeapInternal is missing and so are the Vector structure and other structure are also missing. (Which I suppose are defined under the leap namespace I think)

Please refer a possible solution.

[arshh]

Well now that I can not initialize (or say compile) a script because everytime I do, Monodevelop tells me that there is no namespace or class or structure of Vector and Hand and LeapInternal, (I tried copying the sdk c# script in unity assets and also then replacing the Leap.dll) But always the same error. Now I am moving to sdk V2. I hope to get it working.

But please point me in the right direction if possible. I am very sure that I downloaded/installed the Orion and then imported the assets and modules (which btw works fine on desktop... I don't have a HMD right now). But I can not compile a script

[Joe_Ward]

If you download and import the core asset package, you should have everything you need on the Unity asset side. You also need Unity 5.4.0+ and the Leap Motion service installed.

The Vector, Hand, LeapInternal namespace, etc. are all defined in the LeapCSharp.NET3.5.dll that should already be in the Plugins folder. If they are missing then something has gone amiss when you downloaded or imported the assets. On Windows you should not have to copy files from the SDK package to the Unity project. The core asset package already does this for you.

[arshh]

Okay
I really thought that Unity 5.3.1.3f would work for this and have been using it. Thanks. Maybe this may be the issue.

Thanks

[arshh]

Well I downloaded the Unity 5.4 version and the error still shows. I am still not sure why it is happening. Though the console window shows no error but when I compile any script, the LeapUnityExtension.cs script pops up with 111 errors

One of them says that there are no namespace of LeapInternal...

[arshh]

This is what is happening.

[Joe_Ward]

Does it work if you import the Leap Motion assets in a new project?

Do the scripts work in Unity? In the past I've had difficulty compiling Unity projects in Mlnodevelop or Visual Studio -- even though Unity itself compiles the scripts without problem. I think this had to do with missing references in the Monodevelop/VS projects created by Unity. But I haven't had this problem in several Unity versions. You should see LeapCSharp.NET3.5 listed in the references for the project in MonoDevelop. If you double-click that, then you should see the classes in the Leap and LeapInternal namespaces.

There are actually 2 compile errors, that don't seem to trip up Unity, relating to using "this" in an extension method defined in the wrong place. (You can safely delete the "this" to fix.)

[arshh]

Yes, examples work as long as I don't use the Leap.unity and Leap namespace in any other scripts (though the errors of LeapUnityExtension.cs still shows). I will import the assets in a new project. Maybe I deleted and Imported the assets too many times that's why it is doing that.

Btw I don't see any LeapInternal file in the SDK source-folder as well. Though there are other class files like Vector

[arshh]

I imported the project into new project and the same thing happens.
I checked if the reference is set (or present) and yes it is there in MonoDevelop. I tried changing the .NET framework from 2.0 to 2.0 subset in the player settings (It used to work for Kinect) - No luck.

I also tried to copy paste the LeapCsharp.NET.4.0 and 4.5 files from the Orion SDK into asset folder and used the Edit Reference option to enable one at a time. I noticed that when I enabled only LeapCSharp.NET.4.5, it recognizes the LeapInternal and other methods/classes but then It will give error saying that LeapServiceProvider's method has two arguments instead of one

Please suggest some possible solutions, desperately wanting it to work.

[Joe_Ward]

So you see the reference to LeapCSharp.NET3.5 in your Monodevelop project and you see the namespaces and classes that can't be found when you view this .dll in the Assembly browser?

Whether you use .NET 2 or the subset shouldn't matter.

Unity requires .NET3.5, the other versions won't work. You need the assets from https://developer.leapmotion.com/unity. Don't use the c# files in the SDK. (LeapInternal is a namespace, it doesn't have its own file.)

[arshh]

Yes Joe, I can see all the references once I double click the LeapCSharp .NET 3.5 file under reference folder.

and Adding those .NET4.0 and .NET 4.5 was done later when I had no other option to try. I can't still make it to compile with the 'missing namespace' error so I can not use 'Frame or Hand' class

[Joe_Ward]

I'm afraid I can't think of anything else. The references seem to be present, Mondevelop just can't resolve them at compile time, which doesn't make much sense.

[Joe_Ward]

Are you getting the following warning in addition to the errors?

Warning The primary reference "LeapCSharp.NET3.5" could not be resolved because it has an indirect dependency on the .NET Framework assembly "System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" which has a higher version "4.0.0.0" than the version "2.0.0.0" in the current target framework. UnityModules.CSharp

If so, then while annoying, it isn't fatal. Unity compiles the files just fine even though the IDE cannot. I only get the problem on Windows with Visual Studio, though -- not MonoDevelop (at least on the Mac). We inadvertently added a dependency to a later .NET version when we last built LeapCSharp.NET3.5. This should be corrected soon, but in the meantime, as long as Unity compiles the scripts, things should be fine.

[arshh]

Yes I am getting this error.
Thank you for your help. I just noticed that you are right, Unity would let me go into playmode and does not see these errors (of MonoDevelop) as Errors. Thanks.

[sidhants]

I am facing the exact same issue with those compiler errors in monodevelop. I have the latest unity (5.4+) , the latest Orion and latest Assets. Is there any solution to this?

[Joe_Ward]

As stated above, the errors may be annoying, but they do not prevent Unity from compiling and running your code. We need to release a new LeapCSharp.NET3.5.dll to fix the errors, which should happen within the next couple of weeks.

[sidhants]

Thanks for the quick response. Is it advisable to use the latest asset pack with Unity 5.3.5f1 (I have not moved my project to a newer Unity version yet) as I see the same set of errors that I see in 5.4+?

[Joe_Ward]

The latest assets require Unity 5.4+. This is mainly because Unity 5.4 is not backwards compatible with Unity 5.3. Specifically, prefabs saved in 5.4 often don't work in 5.3. Some other features, like Vive support also require 5.4.

The errors in question here are Visual Studio/MonoDevelop errors, so it shouldn't make a difference which version of Unity you use in that regard.

[sidhants]

Got it. Thanks. The prefabs might cause an issue then.Ill check that.

[leandroazevedo]

@arshh On MonoDevelop go to
Project > Assembly-CSharp Options > Build > General
and change the target framework