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
- UI Overlay Image gets darker on each Camera when multiple Cameras are used
- Assertion failed on expression: 'scriptedImporterClass == SCRIPTING_NULL error when opening the standalone profiler window
- Disabled assets in Import Unity Package window aren't tracked but count as being selected by user
- [Windows] Crash on GetManagerFromContext when video is playing and creating High Definition 3D Projects after FMOD failed to switch back to normal output Error appeared
- GC Alloc produced when adding items to MultiColumnListView with Auto Assign Binding
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;
}