Search Issue Tracker
Duplicate
Votes
0
Found in
5.6.1f1
Issue ID
910536
Regression
No
Legacy Shaders/Specular flickering when both HDR and Anti Aliasing are enabled
To reproduce:
1. Open attached Unity project "MSAA Bloom.zip"
2. Open "TEST" scene
3. Look around the scene with right mouse button and observe the "edge" of the sphere
Expected result: The sphere should not emit any flickering
Actual result: There is a minimal visible white pixel flickering at the "edge" of the sphere
Note: flickering is present in both Play and Editor modes.
Reproduced on: 5.6.0f1, 5.6.0p3, 5.6.0p4, 5.6.1f1, 5.6.1p1, 2017.1.0b5
Note: Can't reproduce on 5.5 and older versions since it was not possible to have both HDR and Anti Aliasing enabled at the same time.
Note: attached gif "flicker1" shows the flickering in all 2017 versions and 5.6 versions from 5.6.0f1 to 5.6.0p3
Note: attached gif "Flickernew" shows the flickering from 5.6.0p4 to 5.6.1p1
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
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
This is a duplicate of issue #903772