Forum Discussion
v0.2.4 overrides custom Far Clip Plane settings?
I've been using some rather large FarClipPlane settings, and the recent 0.2.4 release ignores these settings, unless I hardcode them into the default values of the OVRCameraController.cs script. Bu...
I am having a similar problem where I use a game object called "Pilot" and attach the OVRCameraController to it. Inside the object I attach a left and right camera.
When I run the game, I have a blue culling square directly in front of me because of how big the area is. If the game is running and I change the far plan value to make it larger it fixes the problem. however, if I change the default value to be, say, 3000 instead of the default 1000, when i run the game there is no change and I still see a blue square.
However, in the scene view, if I select the object holding the pilot and cameras, it's clear that the view should cover the skybox I'm using and no square should be seen.
Weirder still, if I select the pilot, which is holding the OVRcameraController script, it fixes my issue.
What seems to be happening is that the farplane is defaulting to 1000.0f until i actually select the object in the hierarchy, which fixes the issue.
Obviously this is a problem because if I build an executable, I have no way of accessing the hierarchy.
When I run the game, I have a blue culling square directly in front of me because of how big the area is. If the game is running and I change the far plan value to make it larger it fixes the problem. however, if I change the default value to be, say, 3000 instead of the default 1000, when i run the game there is no change and I still see a blue square.
However, in the scene view, if I select the object holding the pilot and cameras, it's clear that the view should cover the skybox I'm using and no square should be seen.
Weirder still, if I select the pilot, which is holding the OVRcameraController script, it fixes my issue.
What seems to be happening is that the farplane is defaulting to 1000.0f until i actually select the object in the hierarchy, which fixes the issue.
Obviously this is a problem because if I build an executable, I have no way of accessing the hierarchy.