Search Issue Tracker
Won't Fix
Votes
0
Found in
5.2.0f2
Issue ID
722999
Regression
Yes
[SurfaceShader] LightToTangent space optimization got lost in 5.0, GPU rendering slower than with Unity 4.6
How to reproduce:
1. Open attached project in 4.6
2. Build to iOS and run
- Note the frame time in the FPS debug window in Xcode
3. Open project in the latest version of Unity
4. Build to iOS and run
- Note how the frame time is 50 to 90 percent larger than in 4.6
By Design:
- One of the reasons of the performance drop is caused by the way Surface Shaders are compiled in 5.0.
- Light calculations are now always performed in world space, allowing non-uniformly scaled objects to be rendered correctly. That results in additional shader operations in the pixel shader.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Arabic separator character (066B) is treated as a full-width character when Duospacing is enabled on a TMP text component
- Crash on CheckDeviceStatus when converting materials from built-in to URP and using DX12
- Higher CPU frame time on Android devices with Cortex-A510 efficiency cores (vs Cortex-A55)
- Alt+click on List header does not recursively toggle child foldouts when items use a UI Toolkit CustomPropertyDrawer
- Artifacts are rendered in UITK when using Font Assets and using negative outlines
Add comment