Search Issue Tracker
Won't Fix
Votes
0
Found in
2021.3.37f1
2022.3.26f1
6000.0.0f1
Issue ID
UUM-71797
Regression
No
The Property's reference does not default to "_MainTex" when creating a new Texture2D Property in a ShaderGraph
Reproduction steps:
1. Open the “IN-73972.zip” Project
2. Open the “MainTex” Shader in Assets > Shaders
3. Create a new Texture2D Property ( + > Texture2D in the Blackboard window)
4. Observe the Property’s Node Settings in the Graph Inspector
Expected result: The Reference is automatically set to “_MainTex”
Actual result: The Reference is set to “_Texture2D”
Reproducible with: 2021.3.37f1, 2022.3.26f1, 6000.0.0f1
Reproducible on: Windows 10 (by reporter), Windows 11
Not reproducible on: No other environment tested
Note:
- There is a lack of documentation saying that “_MainTex” is required for the texture to work correctly
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
- [iOS] Text Input field stops receiving changes when the "Cancel" button is used on the soft keyboard
- [WebGPU] URP RenderGraph RenderPass doesn't clear textures
- Query Builder items display raw code style names instead of human readable labels in search field
- “+” button does nothing and has no functionality when clicked in Human Template "Bone Template" list
- Solid gray or black areas are present when using ShaderGraph with Custom Function nodes without manual reimport
Resolution Note:
We won't address this issue as a bug in the way that's been described. We are looking at how we can generally improve the way that material property attributes are managed. This will include things like MainTexture, MainColor, and the others that are available.