Search Issue Tracker
Fixed in 2020.2.X
Fixed in 2019.4.X, 2020.1.X
Votes
0
Found in
2018.4
2019.3.15f1
2020.2
Issue ID
1269926
Regression
No
[Bug] Inout parameter is only valid in shader files, but not valid in cginc files
How to reproduce:
1. Open user-submitted project (InoutInCginc.zip)
2. Inspect the shader files located in Assets/Lib folder(testDepthBufferFetch and testDepthBufferFetch1)
3. Select each Shader, click the arrow next to 'Compile and show code' and select 'GLES3x'
4. Click 'Compile and show code'
5. Compare both compiled files
Expected result: Compiled-Unlit-testDepthBufferFetch.shader contains "#extension GL_EXT_shader_framebuffer_fetch : enable"
Actual result: Compiled-Unlit-testDepthBufferFetch.shader does not contain "#extension GL_EXT_shader_framebuffer_fetch : enable"
Reproducible with: 2018.4.26f1, 2019.4.8f1, 2020.1.3f1, 2020.2.0a20
Notes:
The only difference between testDepthBufferFetch and testDepthBufferFetch1 is that a portion of the code for testDepthBufferFetch is in a cginc file
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Long Prefab save times when using Unity 2022.2 and higher
- Console displays error "UnityException: Creating asset at path Assets/Scenes/ .scenetemplate failed." during scene template saving
- "Development Build" watermark is shown in non-development UWP release builds
- Console errors appear when the Inspector is set to Debug and a GameObject is selected
- A script public variable value is not used when set in the Inspector window
Resolution Note (fix version 2020.2):
Fixed in 2021.1.0a2
Resolution Note (fix version 2020.2):
Fixed in 2020.2.0b14
Resolution Note (fix version 2020.1):
Fixed in 2020.1.14f1
Resolution Note (fix version 2019.4):
Fixed in 2019.4.16f1