Search Issue Tracker
Fixed
Fixed in 2023.1.0f1, 2023.2.0a17
Votes
4
Found in
2023.1.0b4
2023.2.0a2
Issue ID
UUM-27287
Regression
Yes
The “_MainTex_TexelSize” property is not being set when compiling a Shader
How to reproduce:
1. Open the attached project “My project.zip“
2. Open Scene “SampleScene“ (Assets/Scenes)
3. Observe the “Farm_Seed_Shelf_002 (1)“ GameObject in the Game view
Expected result: The “Farm_Seed_Shelf_002 (1)“ GameObject is visible
Actual result: The “Farm_Seed_Shelf_002 (1)“ GameObject isn’t visible
Reproducible with: 2023.1.0a11, 2023.1.0b4, 2023.2.0a2
Not reproducible with: 2020.3.45f1, 2021.3.19f1, 2022.2.7f1, 2023.1.0a10
Reproduced on: macOS 13.0.1 (Intel)
Note:
- The “_MainTex_TexelSize” property is not being set, if the property is replaced by a fixed value, the shader works
- Issue is reproducible in Builds
Comments (4)
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
- Multiple exceptions are thrown after exiting Play mode when Layout Group component is displayed in Debug Inspector and Padding section is expanded
- ScrollView elements are not restored to their original positions after removing a Layout Group with Undo action
- "Assembly with name already exists" errors are thrown when two packages with different technical names resolve to the same namespace
- A Select Scene Entry is added to Undo History when Deleting while a Scene is selected in the Hierarchy
- The Add Component Menu's back arrow accumulates phantom levels when the Menu is repeatedly opened into a Category and closed without selecting
Rocksuit
Apr 01, 2026 12:56
Still no fix in 2023.2.8f1, I use the _MainTex_TexelSize in the shaderLab right in the editor and prefab mode, but not right in the runtime.
xtytyx
Jun 04, 2023 23:55
One clarification: The issue is still present in 2023.2.0a17 so long as SRP batcher is enabled
xtytyx
Jun 04, 2023 23:40
I can confirm the issue is still there in 2023.2.0a17, either the issue is still there or there is a similar issue where the value is not the same as 2022.2.
Did the fix version get pushed to a different one?
patti_jajusaek1
Feb 25, 2023 05:30
I'm using macOS 13.0.1(M1) and have the same problem!
_MainTex_TexelSize is not set, and all the shaders using _MainTex_TexelSize for computation set 0 to its value and producing the wrong effects!!