Search Issue Tracker
Fixed
Fixed in 6000.3.5f1, 6000.4.0b5, 6000.5.0a5
Votes
0
Found in
6000.3.0a1
6000.4.0a1
6000.5.0a1
Issue ID
UUM-131278
Regression
Yes
Shader compilation logging hard to read and timings are not too useful
Example log:
d3d11 finished in 3890.99 seconds. Local cache hits 1 (0.00s CPU time), remote cache hits 0 (0.00s CPU time), compiled 15679 variants (30815.86s CPU time), skipped 0 variants
d3d11 finished in 3892.09 seconds. Local cache hits 1 (0.00s CPU time), remote cache hits 0 (0.00s CPU time), compiled 7 variants (0.62s CPU time), skipped 0 variants
d3d11 finished in 3892.09 seconds. Local cache hits 1 (0.00s CPU time), remote cache hits 0 (0.00s CPU time), compiled 3 variants (0.24s CPU time), skipped 0 variants
d3d11 finished in 3904.17 seconds. Local cache hits 1 (0.00s CPU time), remote cache hits 0 (0.00s CPU time), compiled 509 variants (118.35s CPU time), skipped 0 variants
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
- Texture Import Warnings are obscured by other Terrain Layer options in the Inspector
- Active Targets section text in Graph Inspector is truncated despite available space
- Burst Inspector middle divider is jittering when resized with the Burst Inspector window docked
- Shader Graph Node information is briefly displayed in Graph Inspector when clicking on Category in the Blackboard
- JsonConvert conversion fails trying to call GetCallbackMethodsForType when [OnDeserialized] is used in a class
Resolution Note:
Fixed in 6000.5.0a5
Resolution Note (fix version 6000.5.0a5):
Fixed in 6000.5.0a5
Resolution Note (fix version 6000.4.0b5):
Fixed in 6000.4.0b5
Resolution Note (fix version 6000.3.5f1):
Fixed in 6000.3.5f1