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
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
- Game view renders artifacts when Camera's Component "Post Anti-aliasing" is set to "TAA" and Dynamic Resolution's "Forced Screen Percentage" is changed
- A deactivated Prefab's name color becomes white when a GameObject in the scene is deactivated
- The Game view becomes blank when using Frame Debugger with MSAA and Texture binding enabled in Play Mode
- Crash on dynamixel_sdk.dynamixel:groupSyncReadTxRxPacket when entering Play Mode after updating path to Dynamixel SDK in script
- NullReferenceException is thrown when changing the Inspector preview selection
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!!