Search Issue Tracker
Fixed in 2017.3.0f3
Fixed in 5.6.X, 2017.1.X, 2017.2.X
Votes
3
Found in
5.6.1p3
Issue ID
930709
Regression
No
[iOS][VR] VR shaders are included in Builds even though VR support is disabled
VR shaders seem to be included in builds even when VR support in Player Settings is disabled.
The easiest way to see that this is happening is to build to iOS with OpenGL ES 2.0 graphics API and see the warnings for the Hidden/VR/BlitCopyFromTexArray VR shader in the Xcode console. This could possibly be happening with other VR shaders too.
Steps to reproduce:
1. Open attached project "VRShaders.zip"
2. Build and run on iOS device
3. See warnings in Xcode console
Result: Waring in the Console showing that VR shaders are included into Build:
WARNING: Shader Unsupported: 'Hidden/VR/BlitCopyFromTexArray' - Pass '' has no vertex shader
WARNING: Shader Unsupported: 'Hidden/VR/BlitCopyFromTexArray' - Setting to default shader.
Reproduced with: 2017.2.0b2, 2017.1.0f3, 5.6.2p3.
Not reproduced with: 5.5.4p2 (No VR Support checkbox in Player Settings).
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Reisender
Feb 04, 2020 19:20
Definitely not fixed yet, UCB keeps logging these warnings.
Robdon
Jan 29, 2020 08:46
Yep, it's certainly NOT fixed in Unity 2018.4.15f1
Local and Cloud build gives all these 'errors'. Very annoying as I clutters the log and makes it more likely you will miss something important :(
It's been like it for at least a year in my logs.
13: [Unity] WARNING: Shader Unsupported: 'Hidden/BlitToDepth' - Pass '' has no vertex shader
14: [Unity] WARNING: Shader Unsupported: 'Hidden/BlitToDepth' - Setting to default shader.
15: [Unity] WARNING: Shader Unsupported: 'Hidden/BlitToDepth_MSAA' - Pass '' has no vertex shader
16: [Unity] WARNING: Shader Unsupported: 'Hidden/BlitToDepth_MSAA' - Setting to default shader.
17: [Unity] WARNING: Shader Unsupported: 'Hidden/VR/BlitTexArraySliceToDepth_MSAA' - Pass '' has no vertex shader
18: [Unity] WARNING: Shader Unsupported: 'Hidden/VR/BlitTexArraySliceToDepth_MSAA' - Setting to default shader.
19: [Unity] WARNING: Shader Unsupported: 'AR/TangoARRender' - Pass '' has no vertex shader
20: [Unity] WARNING: Shader Unsupported: 'AR/TangoARRender' - Setting to default shader.
21: [Unity] WARNING: Shader Unsupported: 'Hidden/BlitToDepth' - Pass '' has no vertex shader
22: [Unity] WARNING: Shader Unsupported: 'Hidden/BlitToDepth' - Setting to default shader.
23: [Unity] WARNING: Shader Unsupported: 'Hidden/BlitToDepth_MSAA' - Pass '' has no vertex shader
24: [Unity] WARNING: Shader Unsupported: 'Hidden/BlitToDepth_MSAA' - Setting to default shader.
25: [Unity] WARNING: Shader Unsupported: 'AR/TangoARRender' - Pass '' has no vertex shader
26: [Unity] WARNING: Shader Unsupported: 'AR/TangoARRender' - Setting to default shader.
27: [Unity] WARNING: Shader Unsupported: 'Hidden/VR/BlitTexArraySliceToDepth_MSAA' - Pass '' has no vertex shader
28: [Unity] WARNING: Shader Unsupported: 'Hidden/VR/BlitTexArraySliceToDepth_MSAA' - Setting to default shader.
samuel-levine
Jan 09, 2020 20:41
Come on, Unity. The warnings produced by this issue have shown up in Unity Cloud Build iOS notification emails for several years, and it's definitely still not fixed - I just saw it in a brand-new non-VR iOS project using 2018.4.14f1. It's been an irritant to professional developers for years, even if it *isn't* unnecessarily increasing the build size of Unity iOS apps, and I suspect it probably is for most builds.
A quick search through my email confirms that it's not even fixed in 2017.3.0f3 as claimed.
Unity, please reopen this and get it done!
FadiObaji
Feb 25, 2018 20:04
Where is the solution ?
tomerpeledNG
Jan 13, 2018 12:30
Bump...
Serhii-Horun
Nov 13, 2017 14:50
Any news?