Search Issue Tracker
Fixed in 2018.2.X
Votes
0
Found in
2017.1.0f3
2017.2.0b9
Issue ID
949364
Regression
Yes
Missing Z coordinate in UnityCustomRenderTexture.cginc
In UnityCustomRenderTexture.cginc, notice that in line 210 TEXCOORD0 is float2, but should be float3 in order to work with 3D textures:
struct v2f_init_customrendertexture
{
float4 vertex : SV_POSITION;
float2 texcoord : TEXCOORD0;
float3 direction : TEXCOORD1;
};
Z coordinate gets tossed in line 219:
v2f_init_customrendertexture InitCustomRenderTextureVertexShader (appdata_init_customrendertexture v)
{
v2f_init_customrendertexture o;
o.vertex = UnityObjectToClipPos(v.vertex);
o.texcoord = float3(v.texcoord.xy, CustomRenderTexture3DTexcoordW);
o.direction = CustomRenderTextureComputeCubeDirection(v.texcoord.xy);
return o;
}
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- “Readme” Asset is unreadable in the Inspector window when switching Editor Theme to Light
- “NullReferenceException” error thrown when switching Editor Theme to Light if “Unity Version Control” tab is enabled
- A Warning is displayed in the Inspector when a Mesh with any Material is added as a Terrain Detail
- [Android][Vulkan] Memory leak when playing and stopping a video using the Video Player on some devices
- Caret moves by a character when typing "." and any number into 'Grid and Snap' toolbar's input field
Add comment