When using Single-Pass Stereo, my game will switch, mid playthrough, to a double vision which looks like this:
Note that this does not happen immediately at start but always eventually happens.
It will even split the screen into 4ths sometimes like this:
Interestingly, if I have a second camera overlayed on top of the messed up one, it renders fine. Like this:
Has anyone else experienced this? What was the solution to fix it? This is on Windows and Unity 2018.
no reply to this yet? I have the same issue, but only when using networking.
I’m having this exact same problem for the game I am developing. No easy way to reproduce, but I’m getting it once in a while on multiple PCs with different Oculus headsets and I have no idea how to fix it. The above comment mentions networking. I too am using a little bit of networking, but nothing heavy and it’s not really an option not to use networking anyway. If only I had a consistent reproducible case, then I could test out different things, but I simply can’t reproduce on command yet.
I have no idea what is causing it or how to fix it and it feels like a bug with either Unity or Oculus or both.
My best theory right now is perhaps single-pass rendering mode, which I enabled maybe around early spring 2019.
Another theory is that I’m using some post processing effects, such as Bloom and Color Grading, that maybe has some issues. Historically the post processing stack has had its share of problems, in particular with single-pass rendering mode. However, I’ve seen this on scenes without post processing so I’m kind of ruling it out.
A third theory is that I started getting this after complying with Oculus’ requirements to pause the game, mute the audio and deactivate the avatar and other VR-pose driven elements when the headset is removed or opening the Oculus dashboard in order to support Oculus’ overlay dashboard. But I don’t recall if this error started before or after this change.
Hoping someone from Unity can reach out and give some pointers on how we should proceed to fix this. I’m happy to assist in any way I can to help provide debugging information.
@hellowill89 did you find anything more on this issue?
I’ve raised a support ticket with Oculus to hopefully to get some assistance as it’s impacting my customers and I need to resolve it fast.
@hellowill89 I think I have finally found the root cause of the problem.
Post Processing does not seem to work with Adaptive Resolution. I have tried older versions and the latest versions.
I’m using OVRManager and enabled Adaptive Resolution with min 0.7, max 2.0 values.
Simplest repro so far
I don’t think this bug is limited to VR and Oculus, but this is my current setup.
If you fail to reproduce, maybe it helps load a heavier scene, something that causes adaptive resolution to change the render target resolution.
You can also try dragging the max slider during runtime. I could only drag it to higher values, so you’d have to start with max=1.0 or something.
Workarounds
Related links
[V2] Incompatible with VRSettings.renderViewportScale changes at runtime · Issue #102 · Unity-Technologies/PostProcessing
Related to Dynamic Resolution
I’ve learned this is not the same as Adaptive Resolution, which uses renderViewPortScale and eyeTextureResolutionScale. It did however have similar bugs in Post Processing v2 and was fixed earlier this year. Maybe the fix for Adaptive Resolution can reuse some of that work?
Breaking Dynamic Resolution · Issue #801 · Unity-Technologies/PostProcessing
Adding support for dynamic resolution by JoJo2nd · Pull Request #834 · Unity-Technologies/PostProcessing
v2.1+ breaking Dynamic Resolution on Xbox · Issue #728 · Unity-Technologies/PostProcessing
Same issue here. The double vision occurs when using Single-Pass Stereo and when using a custom shader written for single pass in mind. The shader is a simple fader shader, which is used in OnRenderImage() with the Graphics.Blit() function. If this code is disabled, so the shader is not used, the effect goes away.
The shader:
Shader code
// Source: https://github.com/C-Through/VR-XRSceneLoader/blob/d6d0a53199df162fa6461ddcdc1199c6c1494ee1/Assets/Shaders/ScreenFade.shader
Shader "ScreenFader"
{
Properties
{
_MainTex("Texture", 2D) = "white" {}
_FadeColor ("Color", Color) = (0,0,0,0)
_Intensity ("Intensity", float) = 0
}
SubShader
{
Cull Off ZWrite Off ZTest Always
Pass
{
CGPROGRAM
#pragma vertex vert
#pragma fragment frag
#include "UnityCG.cginc"
struct appdata
{
float4 vertex : POSITION;
float2 uv : TEXCOORD0;
};
struct v2f
{
float2 uv : TEXCOORD0;
float4 vertex : SV_POSITION;
UNITY_VERTEX_OUTPUT_STEREO
};
v2f vert (appdata v)
{
v2f o;
UNITY_INITIALIZE_VERTEX_OUTPUT_STEREO(o);
o.vertex = UnityObjectToClipPos(v.vertex);
o.uv = v.uv;
return o;
}
UNITY_DECLARE_SCREENSPACE_TEXTURE(_MainTex);
half4 _FadeColor;
half _Intensity;
fixed4 frag(v2f i) : SV_Target
{
UNITY_SETUP_STEREO_EYE_INDEX_POST_VERTEX(i);
fixed4 color = UNITY_SAMPLE_SCREENSPACE_TEXTURE(_MainTex, i.uv);
fixed4 lerpedColor = lerp(color.rgba, _FadeColor.rgba, _Intensity);
return lerpedColor;
}
ENDCG
}
}
}
How could this shader be made to support Single-Pass rendering?
I think the issue is at:
UNITY_DECLARE_SCREENSPACE_TEXTURE(_MainTex)
in the shader. This could be the reason it shows double vision (screenspace + screenspace).
If you are just using this shader to fade in/out, then I would suggest to use the script in Oculus library called as ScreenFade.cs/ScreenFader.cs. It will be attached to CentreAnchorCamera under OVRCameraRig and works better.
Adjusting the UV’s fixed the issue on windows:
This part of the documentation was useful: Unity - Manual: Single Pass Stereo rendering (Double-Wide rendering) (unity3d.com). On Android everything turns white though. But I guess that’s another issue with my grayscale shader.