Unity 2017.3 update killed Leap Motion >_< Suggestions?

[jameskane05]

Have their been any known issues with Unity 2017.3 (just came out recently)? My project was going along fine in 2017.2 but I decided to update... now I am lucky to get 1 frame per second, hands don't track at all and I get the following error. Even the simple demo scenes just hang at 1 frame every few seconds. Even going back to 2017.2 and reimporting Leap Motion has no effect - same problem. Tried everything I can think of...

NullReferenceException
Leap.Unity.ProfilerSample..ctor (System.String sampleName, UnityEngine.Object obj) (at Assets/LeapMotion/Core/Scripts/Utils/ProfilerSample.cs:31)
Leap.Unity.Interaction.InteractionController.Leap.Unity.Interaction.IInternalInteractionController.FixedUpdateController () (at Assets/LeapMotion/Modules/InteractionEngine/Scripts/InteractionController.cs:230)
Leap.Unity.Interaction.InteractionManager.fixedUpdateInteractionControllers () (at Assets/LeapMotion/Modules/InteractionEngine/Scripts/InteractionManager.cs:388)
Leap.Unity.Interaction.InteractionManager.FixedUpdate () (at Assets/LeapMotion/Modules/InteractionEngine/Scripts/InteractionManager.cs:327)

[camdenbock]

See this thread:

Orion+Core 4.3+InteractionEngine not working in Unity 2017.3

[jameskane05]

Resolved with your help, thanks! Ultimately had to clone the github repo, switch to the 2017.3 branch, and start my project over from there (luckily was only a script or two in). Working really well now.