Search Issue Tracker
Won't Fix
Votes
1
Found in
2017.4.0f1
2018.3.0a1
2018.3.2f1
2019.1.0a1
2019.2.0a1
Issue ID
1124553
Regression
No
HDR values "bleeding" through transparent shader on vertex color on Nvidia GPUs
Steps to reproduce:
1. Download and open the attached project (in comment) on a PC with an Nvdia GPU
2. Make sure player settings is set to Linear color space
3. Observe the game view
Expected result: sun disk is fully covered
Actual result: sun disks HDR values can be seen behind the sprite
Reproduced on 2017.4.0f1, 2017.4.20f1, 2018.3.5f1, 2019.1.0b2, 2019.3.0a2
DUT:
NVIDIA GeForce GTX 970 - reproducible
Radeon™ Pro WX 9100 - not reproducible
AMD Radeon(TM) RX 460 Graphics - not reproducible
Changing Color space to Gamma or turning off HDR removes the issue
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
Resolution Note:
Possibly due to driver issue. Workaround is to add a very small float number in Vertex shader.
v2f vert (appdata v)
{
v2f o;
o.vertex = UnityObjectToClipPos(v.vertex);
o.color = _Color+0.0001f; //workaround
return o;
}