Search Issue Tracker
By Design
Votes
0
Found in
2021.3.45f1
2022.3.51f1
6000.0.25f1
6000.1.0a2
Issue ID
UUM-85587
Regression
No
“Shader error in 'Hidden/VFX/.../Minimal/Render Quad': undeclared identifier 'mainTexture' at line 2198 (on d3d11)” error appears when connecting a Switch Node output to the Main Texture in VFX Graph
Reproduction steps:
1. Open the attached “VFXURP.zip” project
2. Open the “SampleScene” (Assets > Scenes)
3. Open the “Main Texture Bug Demo.vfx” from the Project Window
4. Click Compile
5. Observe the Console
Expected result: No errors or warnings
Actual result: “Shader error in 'Hidden/VFX/Main Texture Bug Demo/Minimal/Render Quad': undeclared identifier 'mainTexture' at line 2198 (on d3d11)” error
Reproducible with: 2021.3.45f1, 2022.3.51f1, 6000.0.25f1, 6000.1.0a2
Reproducible on: Windows 11
Not reproducible on: no other environment tested
Notes:
- Error might appear instantly after opening the Editor or after a fewer steps
- Does not reproduce in BiRP and HDRP
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
- Crash on RaiseException when opening a specific project
- DownloadHandlerScript.CompleteContent is called twice when building for WebGL
- Scene view has Y coordinates of the Screen Position node flipped when some of the URP features are disabled
- Volumetric fog shader variants are missing from build when "Strict Shader Variant Matching" is disabled
- Unnecessary modifications clutter the Scene when using a RectTransform driven by a LayoutGroup in a Prefab
Resolution Note:
The switch (or any branch-based operator) will not function correctly if used to swap textures based on GPU evaluation—such as using a per-particle random value in this case.
Texture branching has been enabled starting with version 2023.3.0a1; however, this functionality is only valid when inputs can be evaluated on the CPU.
We acknowledge that this issue currently lacks constructive error feedback within the graph. Improvements to address this are under consideration, but please be advised that they will not render this graph valid.