Search Issue Tracker
Fixed
Fixed in 2021.3.45f1, 2022.3.50f1, 6000.0.25f1, 6000.1.0a1, 7000.0.0a2
Votes
0
Found in
2021.3.43f1
2022.3.45f1
6000.0.18f1
7000.0.0a1
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
- Foldout arrow indent is misaligned in the Inspector when used in Custom Type
- [Android] The Player screen turns black when playing a video under certain conditions
- Search window icons at the bottom are cut off when Search window is resized vertically
- "Try something else?" text label is cut off when searching for a long text in the Search window
- Rendering Debugger window sections do not have a minimum width set when resizing with the slider in the middle of the window
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.