Search Issue Tracker
Duplicate
Votes
1
Found in
2018.3.0f1
2018.3.0f2
2019.1.0a1
2019.2.0a1
Issue ID
1115278
Regression
No
Scene rendering flickers when Camera is using an Image Effect with SAMPLE_TEXTURE2D written for Post Processing Stack
How to reproduce:
1. Open user attached project "PPS.zip"
2. Move the cursor within the bounds of the Game or Scene View
Expected result: There is no flickering in Game/Scene View
Actual result: There is flickering in Game/Scene View
Reproducible with - 2018.3.3f1, 2019.1.0a15, 2019.2.0a2
Notes:
1) This bug is not reproducible with AMD Radeon Pro WX 9100, but is reproducible with NVIDIA Geforce GTX 950
2) Not reproducible on 2017.4 because this version does not have these: PostProcessEffectSettings, PostProcessEffectRenderer, FloatParameter, PostProcessRenderContext
-
Resolution Note:
Workaround:
v2f vert (appdata v)
{
v2f o;
o.vertex = UnityObjectToClipPos(v.vertex);
o.color = _Color+0.0001f; //workaround
return o;
}
Comments (1)
-
Kronnect
Mar 20, 2019 08:14
This is a showstopper for any decent post-processing effect added to the stack. Should be marked high priority for 2019.1.
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
This is a duplicate of issue #1124553