Search Issue Tracker
Fixed in 2018.3.X
Fixed in 2019.1.X
Votes
14
Found in
2018.2.0a1
Issue ID
1108929
Regression
Yes
[Linux][Nvidia] Graphical corruption in many games with OpenGL
Note: This fix is being backported to 2018.3, likely to land in 2018.3.4f1
In a number of Unity games on Linux, running on OpenGL and an Nvidia card, corruption is seen, usually as part of the UI, but in some circumstances, it affects the full framebuffer.
Available workarounds are to use "-force-glcore42 -force-clamped" for games that don't need GL 4.3 features or above, or "-force-vulkan" on games need those features.
See external mentions:
https://forum.unity.com/threads/graphical-corruption-in-2018-2.542646/
https://devtalk.nvidia.com/default/topic/1043953/linux/garbled-up-graphics-in-unity-opengl-/post/5303297/#5303297
https://www.gamingonlinux.com/articles/have-graphical-distortions-in-unity-games-with-nvidia-heres-a-workaround.13133.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Some UXML Template Asset foldouts appear enabled when all fields inside are disabled
- URP Terrain Demo crash on burst_signal_handler after Generating lighting
- Project window button icons are poorly visible and their shades differ in Light theme
- GC.Alloc called by HDRenderPipeline.LensFlareMergeOcclusionDataDrivenPass() when playing the default HDRP Sample Template project
- Automatic LOD fails and SRP Batcher incompatibility occurs when using spline-based quad-topology meshes
Add comment