Change FOV in 5.4* on Vive via script gone?

We are no longer able to adjust the FOV on the VR Camera after updating to 5.4 for the Vive version of our app. It does work with Samsung Gear however.

Was this FOV control removed on purpose by Unity, or just change in some way I'm not detecting, or is this a bug with Steam VR?

Here is an example of the things we were doing with it:

Code (CSharp):

1.     public float IncrementForFOV ()
2.         {
3.             float fov = thisCamera.fieldOfView;
4.             float extentFOV = (targetFOV < thisCamera.fieldOfView) ? maxFOV : minFOV;
5.             float x = ((Mathf.Pow((defaultFOV - fov) / (defaultFOV - extentFOV), 2f) + 0.1f) / 1.1f);
6.             float dir = ((targetFOV - fov) / Mathf.Abs(targetFOV - fov));
7.             return dir * x;
8.         }

 

Thank you so much for your response, my studio recently released to Steam Early Access using 5.3, and are unable to update with more content after updating! Here's hoping there is a solution soon.

 

Yes, it can certainly cause motion sickness when used improperly. There are many tricks to counteract this neurological response by use of blur shaders, tunnel blinders (like in the Ubisoft Eagle demo), and of course letting the user control when to zoom and never doing it unexpectedly. I know it wasn't perfect in the initial release, but most of our mixed reviews are due to lack of content, with some complaints about the transition FX.

I'd like to continue to experiment with good ways to simulate zooming into a new degree of magnification power (this is a science app, not a game per se) but want to keep the benefits of being on the new version of Unity at all times. Is the word "broke" being used to say this is now by design, and I might need to make a feature request instead of a bug report? I feel it's a bit heavy handed for them to make design choices for devs by limiting the plugin - especially so early in our VR pioneer days!

Edit: Actually, if it's OPEN VR that is the FOV problem... at least it's OPEN! Someone at work just reminded me of this fact.

 

I just got this working (Thanks for making this available btw!). Joost, the cursor objects should be disabled until you have a successful raycast hit with a canvas - so don't disable the event system. Try this: I juts copied VivieControllerInput.cs and UIIgnoreRaycast.cs into my existing project, added the Input Module to my Camera Rig and attached the ViveControllerInput script to it (cursor scale is at 0.0001). Make sure you do not have another event system in your scene.

 

Is this in regards to overwriting the FOV controls? I posted on the Steamworks forums as well trying to figure out what the deal is.