Unity 5.3.4p1 roadblock with OVRPlugin 1.3.0 for Gear

I'm at a total roadblock and I can't seem to fix my issue. I have Unity 5.3.4p1 on Mac and trying to develop for the Gear.

I have installed the Oculus Utilities for Unity 5 v1.3.0 and OVRPlugin for Unity 5 v1.3.0.

When I try to play a default scene I receive the following error:

Couldn't open /Applications/Unity/Unity.app/Contents/VR/oculus/macosx64/OVRPlugin.bundle/Contents/MacOS/OVRPlugin, error: dlopen(/Applications/Unity/Unity.app/Contents/VR/oculus/macosx64/OVRPlugin.bundle/Contents/MacOS/OVRPlugin, 2): Library not loaded: @rpath/LibOVRRT_0.framework/Versions/5/LibOVRRT_0
Referenced from: /Applications/Unity/Unity.app/Contents/VR/oculus/macosx64/OVRPlugin.bundle/Contents/MacOS/OVRPlugin
Reason: image not found


Along with various errors like:

Could not load symbol ovrp_Initialize : invalid handle passed to dlsym()
VR: Oculus could not be loaded: Failed to load symbol ovrp_SetupDistortionWindow.
[VRDevice] Initialization of device oculus failed.

I feel like I'm missing something basic here.

Thanks for any help you can provide!

 

Have you tried installing the new Oculus Runtime 1.3 (AKA Oculus Home)?

 

@thomasphifer 's answer helped me out! Though now I am dealing with the issue here:
https://forums.oculus.com/developer...-mobile-documentation-outdated-how-do-i-start

For ref, I am building for Gear VR from OS X

 

I have Installed Oculus home on windows 10 but the same error appearing on unity. "[VRDevice] Initialization of device Oculus failed." and also the Oculus signature file not accepting by oculus on my Galaxy s6 for my test.apk

 

I have the exact same problem with Unity 5.3.4f1

My dev machine is running OSX 10.10.2 (Yosemite) and there's no problem.

Our Jenkins server has a OSX slave running 10.11.5 (El Capitan). It has the same 5.3.4f1 version of Unity installed. When it attempts to build our GearVR project, the following error is output in the log when Unity opens the project:

Followed by a bunch of "VR: Oculus could not be loaded" errors.

If I remote into the build slave and open the project in Unity there, the errors are in the console.

Can you clarify this recommendation? What does the Runtime for OS X (which btw is not really "supported" anymore and stuck at an old beta version) have to do with simply opening the Unity project? Also, the runtime is NOT installed on my dev machine, which as I said does not have this problem and is otherwise identical to the build slave except for OS X version.