Search Issue Tracker
Fixed in 2017.1.X
Votes
0
Found in
5.6.0b3
Issue ID
870591
Regression
Yes
Shaders become unlit when RenderTexture Anti-aliasing is active and Camera RenderingPath is set to Deferred
When using a RenderTexture with Anti-Aliasing turned on, the object shaders become unaffected by lights if the MainCamera Rendering Path is set to Deferred.
1. Open attached project
2. Open GAME scene
3. Observe unlit models in Game view
4. To return shaders to normal either:
a) In Assets folder go to Graphics -> BaseMaterials to find the RenderTexture "SCREEN" and set it to "None"
b) In SceneView find Main Camera and set the Rendering Path to anything but "Deferred" (for example "Forward")
Expected outcome: Objects represented on the RenderTexture are lit up, have proper shadows, they react to different lighting.
Actual outcome: Objects become unlit, unreactive to different lighting.
Reproduced on versions 5.6.0b3, 5.6.0b6, 2017.1.0a4
Failed to Reproduce on versions 5.5.2f1, 5.5.0p2.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- There is no way to adjust the HDR Paper White value of the Unity Editor's interface, making it difficult/uncomfortable for some developers to work on very dark/bright scenes in HDR
- Animator window has a dropdown button that throws “MissingReferenceException” error on a new project when the previous project had a GameObject with an animation
- Animator State name overflows outside the visual box when the State has a long name
- UI Document file remains marked as Dirty after Undoing made changes
- Switching between UI Documents with different Canvas sizes marks the UXML file as dirty
Add comment