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
- Typo on "Chromatic Abberation" and "chromaticAbberationIntensity" when instead it should be aberration
- UI Document (UXML) UI disappears from the Game view when any asset is imported and does not reappear until clicking in the Editor
- Warnings about invalid URIs are thrown when UI Builder's Material field is set to null
- Warnings about invalid URIs are thrown when UI Builder's Variable Asset Reference field is set to null
- "Attempting to use an invalid operation handle" error is thrown when stopping Play Mode after loading an Addressable scene using LoadSceneAsync
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.