Search Issue Tracker
Fixed in 2021.3.45f1
Fixed in 2021.3.X, 2022.3.X, 6000.0.X, 6000.1.0a1, 7000.0.0a2, future release
Votes
0
Found in
2021.3.43f1
2022.3.45f1
6000.0.18f1
Issue ID
UUM-79781
Regression
No
Log shader compilation does not give info on which shader instance had a variant compiled
Steps to reproduce:
1. Create a new Unity project.
2. Make sure "Log shader compilation" is enabled in Player settings.
3. Build and run, check the logs
Actual results:
There is no indication of which shader instance was used in the log.
Example log:
Uploaded shader variant to the GPU driver: TextMeshPro/Mobile/Distance Field SSD, pass: <Unnamed Pass 0>, stage: vertex, keywords UNDERLAY_ON
Expected results:
There is an indication of which shader instance was used in the log.
Uploaded shader variant to the GPU driver: TextMeshPro/Mobile/Distance Field SSD (instance 123456), pass: <Unnamed Pass 0>, stage: vertex, keywords UNDERLAY_ON; time: 0.24ms
Comments (1)
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
- “FMOD failed to set the software format to the custom sample rate…” warnings are thrown as System Sample Rate value is being changed in Audio section of Project Settings window
- VFX Marquee selection does match the visual indicator
- “Invalid AABB aabb” errors are spammed when “Infinity” value is entered in Collider Component fields
- Editor Role does not sync with the MPPM Play Mode Scenario Role when entering Play mode
- Long asset names cause overlap with the “Find” function in search result tabs
JeffreyK
Jan 07, 2025 09:21
Testing in 2022.3.55. Why is the "stage:" part removed from the message? This "bugfix" fixes the instance info but introduced a new issue to know which stage it was for.