Search Issue Tracker
Not Reproducible
Votes
0
Found in
5.0.0p3
Issue ID
685757
Regression
Yes
Shader compilation errors with the NFAA antialiasing effect
The NFAA antialiasing effect in the standard assets requires Shader Model 3.0. However, it lacks a proper shader target declaration ("#pragma target 3.0"), and because of that, it emits shader compilation errors while building a Windows standalone player.
Comments (3)
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
- 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
XMachinaX
Jul 31, 2015 12:28
For those that need a bit more guidance, just add :
#pragma target 3.0
at the end of the CGProgram declarations
Michel G
May 29, 2015 18:16
How did you fix the compilation error?
Ajinkya
Apr 18, 2015 17:16
It did fix the compilation error but it didn't show up in the update. I had to add the declaration on the code on my end.