Operating system: Linux-5.4.0-7626-generic-x86_64-with-debian-bullseye-sid 64 Bits
Graphics card: GeForce GTX 1050 Ti 440.82
Broken: 2.83 ff7a30d92884 (2020-05-18 23:31), 2.90 7bd07c9f5adf (2020-05-18 23:33)
Short description of error:
This isn't a new issue, it just seems it was missed during rB365e9cb6aa86. This task was created as an extension of T74243 because T74243 was closed. I will mark this report as Linux only unless people on Windows or Mac OS can replicate it.
Edit: This may also be related: rB5593efec01c2
Exact steps for others to reproduce the error:
- Open Blender with default settings and a default startup scene.
- Change to "Active Camera" view (Numberpad 0).
- In the properties editor select the "Output" tab and enable "Stereoscopy".
- Now the viewport should have the glitch shown in the above screenshot. If you then go to user preferences and in the "viewport" section change the anti-aliasing method to "none" or "single pass" the issue goes away. All other anti-aliasing settings have the issue.
Note 1: This issue only occurs in solid mode. The issue also seems to disappear if you change to "Material Preview" or "EEVEE rendered" mode at anytime while having that Blender instance open. E.G. Open Blender, switch to "Material Preview" mode, switch back to "Solid" mode then enable "Stereoscopy" and go the the active camera. Now the issue won't occur. Load factory defaults, enable "Stereoscopy", switch to active camera, the issue won't occur. I have to close Blender and re-open it to get the issue to occur again.
Note 2: I have tested to ensure the issue described in T74243 hasn't returned. So far I'm only seeing the issue with stereoscopy. The issues with weight paint and wireframes hasn't returned as far as I can tell.