Unity: Additional inputs to leap project + error at "Leap.Unity.ProfilerSample..ctor"

[LookB4ULeap]

I have a project that was built from the ground up with just Unity + Leap Motion, now I'm looking into adding multiple options for controllers, like Oculus Touch and, just for testing, keyboard. I took a look at the Leap Interaction Engine and it seems to be what I need.
However, I don't think it properly explains how to map VR controls to the controls that are already present in a leap project. I also get a ton of errors, and can't run the example scenes. Anyone have experience doing this? What properties should one define for its grasp axes?

I'm using Unity version 2018.1.1f, Orion 3.2.1, Core Assets 4.3.2, and Interaction Engine 1.1.0 (so any tutorials that mention Brush Hands are too old to be relevant).

Update:
I decided to try the included example projects to get a better idea how to set up a rig and controllers, but I keep getting these errors. I have fixed the problem with not recognizing tokens, but why am I getting a new CTOR error every second

[AlexColgan]

Is it related to this issue? https://forums.leapmotion.com/t/leap-motion-unity-error/7091

[LookB4ULeap]

It does seem similar at first, but I edited the tags in the inspector and now those debug logs aren't appearing in the console. Even when trying to run the example scenes, however, nothing works because the constructor of Leap.Unity.ProfilerSample keeps generating a NullReferenceException. The comments in the code don't really give a good overview of what the script does, so I'm not sure why this is occurring.

[LookB4ULeap]

It is actually not related to that issue at all, the input axes are a different animal, and I found out how to set them up myself by digging through the Unity forums.
After another day of work I'm still getting all those errors from ProfilerSample. The only part of the project that changed from the working build to this build is the SteamVR version on my computer. Do you believe that might have something to do with it? I don't know what the "profiler" is in this context.

[nbenson]

Can you click on one of the ProfilerSample errors and paste the stack trace? The ProfilerSample is just a utility class that makes it easier to annotate the Unity profiler with performance metrics, so it's strange that it's throwing null reference exceptions.

[LookB4ULeap]

Thank you for taking interest! Here is a png of the stack trace:

And here is a text version in case the pic does not display:
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)

[nbenson]

Looks like that version had an oversight where sometimes a contact bone parent game object was being accessed before it was assigned.

This behavior should be fixed in IE 1.1.1 and up. Would you be able to upgrade your Core and IE? The latest is preferred, but at least having Core 4.3.4 and IE 1.1.1 should fix this issue.

[LookB4ULeap]

Thank you, that must be it. It might be a bit cumbersome, but I could upgrade.