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.
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
- Tile Palette selected dropdown text does not update when palette is renamed
- ArgumentException thrown and reference to Template gets unset when opening UXML file after editing referenced Template in Play mode
- [iOS][WebGL] Player freezes when multiple properties of a VisualElement are changed at the same time
- Warning 'GetControlID at event ValidateCommand returns a controlID different from the one in the Layout event' is logged when undoing the deletion of an Edited Freeform 2D Light
- ShadowCaster2D breaks on certain Rotation positions when Casting Source is set to PolygonCollider2D
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.