Search Issue Tracker
By Design
Votes
0
Found in
5.0.0a18
Issue ID
623387
Regression
Yes
5.0 surface shaders use 13-14 more ALU instructions and are 20-50% slower
Import the attached Blend SM2.shader in Unity 4.x. It will work fine. Import it in Unity 5.0 and you will get the following compilation error:
"Arithmetic instruction limit of 64 exceeded; 65 arithmetic instructions needed to compile program"
There is a workaround to make the errors go away, by adding "#pragma target 3.0" to the appropriate place in the shader file, but that has its own drawbacks.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
Add comment