Bug Using "XR Management" package renders to one eye only

Hi,

We've recently switched from built-in VR to the "XR Management" package on 2019.3 for standalone exe for WMR. We use the Standard shader and a custom shader in our scenes.

Everything using the standard shader works fine in VR, but our custom shader renders only to the left eye. (We also tried URP, but same problem)

Any idea's/leads? This is blocking us from moving away from the now deprecated built-in VR support.

Thank you,

Geert

 

Hi Thomas,

Thanks for replying. I'm actually using single pass in built-in VR and that works fine. This is my shader actually (now using URP):

Shader "Unlit/PointCloud"
{
Properties
{
_MainTex("Texture (RGB)", 2D) = "white" {}
}
SubShader
{
//Tags{ "RenderPipeline" = "LightweightPipeline" "ForceNoShadowCasting" = "True" "IgnoreProjector" = "True" }
Tags{ "Queue" = "AlphaTest" "IgnoreProjector" = "True" "RenderType" = "TransparentCutout" "ForceNoShadowCasting" = "True" }
Blend Off
AlphaToMask On
Cull Off
Pass
{
CGPROGRAM
#pragma vertex vert
#pragma geometry geom
#pragma fragment frag
#include "UnityCG.cginc"
sampler2D _MainTex;
struct GS_INPUT
{
float4 vertex : POSITION;
float4 color : COLOR;
};
struct FS_INPUT {
float4 vertex : SV_POSITION;
float4 color : COLOR;
float2 texcoord : TEXCOORD0;
};
GS_INPUT vert(appdata_full v)
{
GS_INPUT o = (GS_INPUT)0;
o.vertex = mul(unity_ObjectToWorld, v.vertex);
o.color = v.color;
return o;
}
[maxvertexcount(3)]
void geom(point GS_INPUT tri[1], inout TriangleStream<FS_INPUT> triStream)
{
float size = tri[0].color.a * 1.6;
if (size > 0)
{
half3 normal = mul(tri[0].vertex.xyz, unity_ObjectToWorld) - _WorldSpaceCameraPos;
half3 tangent = normalize(cross(half3(0, 1, 0), normal));
half3 up = normalize(cross(tangent, normal));
float4 vertex = tri[0].vertex;
half dist = distance(_WorldSpaceCameraPos, vertex);
if (size < dist / 250.0)
{
size = dist / 250.0;
}
if (size > dist / 5.0)
{
size = dist / 5.0;
}
half3 upSize = up * size;
half3 tangentSize = tangent * size / 1.1547;
FS_INPUT pIn = (FS_INPUT)0;
pIn.color = tri[0].color;
pIn.vertex = mul(UNITY_MATRIX_VP, vertex + half4(-tangentSize - upSize / 2, 0));
pIn.texcoord = half2(-0.366, 0);
triStream.Append(pIn);
pIn.vertex = mul(UNITY_MATRIX_VP, vertex + half4(upSize, 0));
pIn.texcoord = half2(0.5, 1.5);
triStream.Append(pIn);
pIn.vertex = mul(UNITY_MATRIX_VP, vertex + half4(tangentSize - upSize / 2, 0));
pIn.texcoord = half2(1.366, 0);
triStream.Append(pIn);
}
}
float4 frag(FS_INPUT i) : COLOR
{
float4 color = i.color;
color.a = step(0.5, tex2D(_MainTex, i.texcoord).a);
if (color.a < 0.5) {
discard;
}
return color;
}
ENDCG
}
}
}

Geert

 

I've just built using "Single Pass Instanced" using built-in VR and yes, you are right. Only Left eye. But with "Single Pass" it works fine.

Edit: so basically editing previous shader to be compatible with Single Pass Instanced rendering is the only thing keeping us from:

* having improved performance
* moving on to "XR Management" package and leaving deprecated built-in VR
* finally kicking out SteamVR (!!!!)

Can anyone help us modifying this shader? We have a dev job opening in a great company here too ;-)

 

Hey, Thomas! I got everything working thanks to your remarks … and it looks great. Thanks!

Another thing now: when no headset is connected I want to render onscreen in native resolution (as fallback). That was the default behavior of built-in VR and I need to keep that. That is not the behavior I observe with the latest "XR Managament" / WMR plugin. Any suggestions there on how to achieve this?

 

I try to check the VR status in Mock HMD and seems to always return MultiPass even if Single Pass Instance is selected, this probably creates issue as i only see image in left eye, right is full black with my image effect on

Is this a known bug ?

Thanks

 

Hi,

I have a DELL with nvidia, bought 3 years ago, i suppose should support it but cant be sure.

Is it possible that this is a such a highly advanced feature that only very last years cards support it ?

Thanks

 

Can anyone please share how exactly to update the shaders to SPI compatible? I'm having the shaders only rendering in the left eye issue. Even with the new XR Management stuff and the default XR rig, the lines from the controllers only render in the left eye. Please assist.

 

Hi @ThomasZeng
Same thing here, not using any custom shader just Unity UI!

Using Unity 2020, WMR headset with XR Management and XR Interaction Toolkit, for some reason normal Unity UI renders in one eye only, the left eye.

Tried to change the platform to Universal Windows Platform but that didn't change anything.

 

We are using world-space canvases, and this doesn't work after switching to xr plugin management plugin (2020.1.0f7 / HDRP 9.0.0 and 2020.2.0b4 / hdrp 10.0.0). Only renders in left eye. Bloom effect is not working correctly on left eye.

Also, screen mirroring in builds doesn't work after switching to xr plugin management package.

You can also see this in editor (that UI only renders to left eye)

 

When occlusion mesh is enabled in HDRP settings (XR), the left eye is rendered with a white "blur". See screenshot in link below:

https://drive.google.com/file/d/18GC2QmBL6MqGR1jDkbk92oXcoHlBcE8I/view?usp=sharing

 

True, I am using World Space Canvas.
Does this mean there is no way to use UI with VR in XR Management?

 

Is there any info on updating ShaderGraph shaders to use SPI? I'm having trouble with a shadergraph shader only rendering correctly through one eye.

 

I spoke to the team and they wanted to know

"What rendering mode are you using? As mentioned previously in the thread, we recommend upgrading your shaders to single pass instanced. Details on how to do that can be found here: https://docs.unity3d.com/Manual/SinglePassInstancing.html. If you are still running into issues, please file a bug and we will investigate."

Also from the team

"Although Shader Graph shaders can run in XR, Shader Graph doesn't currently support the XR utility feature to create SPI-compatible shader input textures. Unity will add this, as well as the ability to access eyeindex from Shader Graph, in a future release."

 

This is awesome news and I believe it will solve all of our problems. For now I've switched to URP and everything seems better across the board. If I have any issues, we'll update the shaders manually until their is a fix from you guys. Thanks for the help.

 

@Shaunyowns you recommend we upgrade to spi shaders, at the same time you say shadergraph doesn't support spi shaders for xr?? That is infuriating. When will this be resolved? Can you just fix this broken mess of an engine, please.

 

Hey there! @Innovine

Shader graph shaders are compatible with SPI by default. The only known restriction for now is that you can't access eye idx in shader graph and you can't use screen space textures other than camera color/depth (screen space texture needs to be texture2dArray in SPI and requires special care). If you encounter any issues, please file a bug so we can take a look.

 

I NEED YOUR HELP: when I try to run my unity vr project, my personal SHADER in the object is visible in one eye, but not in the other, I did not use URP AND HDRP in my project. HOW CAN I FIX THIS? PLEASE HELP

 

HELLO @ThomasZeng ! I NEED YOUR HELP: when I try to run my unity vr project, my personal SHADER in the object is visible in one eye, but not in the other, I did not use URP AND HDRP in my project. HOW CAN I FIX THIS? PLEASE HELP

 

I'm having this issue in 2019.4 only in assetbundle scenes including only the standard shader.

Would this be due to having built the scenes before switching to XR management and single-pass instanced?