Updated to Oculus integration sdk 1.0.0+, now game's broken

If you want a GameObject to move with head tracking, attach it to OVRCameraRig.centerEyeAnchor. If you want it to follow the yaw but not pitch and roll of head tracking, you can use something like OVRPlayerController. See the First Person Example in our SDKExamples package: https://developer.oculus.com/downloads/game-engines/1.3.0/Oculus_Utilities_for_Unity_5_SDK_Examples/

I did do this, but it's not working. Very strange because it works I the unity player screen, but not on the Gear VR headset.

The documentation is garbled, there's several conflicting unity oculus set up guides, and Google prefers showing results for the pre 1.0 integration. So I might have unity set up wrong, but how to fix? I have unity 5.3.4f1, oculus integration 1.0+, I (think) it's 1.1 but there are so many I tried, i just know it's 1.0+. Then i copied posted new files into UNITY/.../Oculus folder for all the Win86, and other folders. Restarted unity. Now, where did i go wrong?

These are the two files you should use:
https://developer.oculus.com/downloads/game-engines/1.3.2/Oculus_Utilities_for_Unity_5/
https://developer.oculus.com/downloads/game-engines/1.3.2/OVRPlugin_for_Unity_5/

The Oculus Integration is for Unity 4 and is no longer recommended to use.

Thanks cybereality, those worked:)

So, how long does app submission usually take?

and thanks vrdaveb, I got the weapon working with head tracking:)  ..and yes, how long does app submission usually take?

Unfortunately it can take several weeks to get an app submitted.

Okay.  So I've kept UI very simple, there's simply a text with image connected to Canvas, out about three VR meters from first person view, says "shoot to start", with image showing basic gamepad controls.  I didn't feel a full menu was a great option in VR.  Keeping it simple feels more "real"... what do you think about this?  I don't want to get a reject for going simple..