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
- Texture Sampling overlap causes graphical errors on specific Graphics APIs and Devices when using Framebuffer Fetch
- [Android] AssetBundle loading performance degradation when loading from a local Assetbundle
- [iOS][Android] Reflection with Generic Class returns unexpected values
- Shader Variant Collection Asset UI is hard to read when multiple Shaders and keywords are added
- Regression for "WebGL build is missing "malloc" and "free" functions when passing "-sERROR_ON_UNDEFINED_SYMBOLS=0" to emscriptenArgs"
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.