Enabling "Steroscopy" in the viewport camera causes graphical glitches with anti-aliasing enabled. #76874

New Issue

Alaska · 2020-05-19T07:32:18+02:00

Alaska commented

2020-05-19 07:32:18 +02:00

System Information:
Operating system: Linux-5.4.0-7626-generic-x86_64-with-debian-bullseye-sid 64 Bits
Graphics card: GeForce GTX 1050 Ti 440.82

Blender Version:
Broken: 2.83 ff7a30d92884 (2020-05-18 23:31), 2.90 7bd07c9f5adf (2020-05-18 23:33)
Worked: 2.82a

Short description of error:
This isn't a new issue, it just seems it was missed during 365e9cb6aa. This task was created as an extension of #74243 because #74243 was closed.

Edit: This may also be related: 5593efec01

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 #74243 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.

Workaround:
Change shading to material mode once and the issue is gone.

**System Information:** Operating system: Linux-5.4.0-7626-generic-x86_64-with-debian-bullseye-sid 64 Bits Graphics card: GeForce GTX 1050 Ti 440.82 **Blender Version:** Broken: 2.83 `ff7a30d92884` (2020-05-18 23:31), 2.90 `7bd07c9f5adf` (2020-05-18 23:33) Worked: 2.82a **Short description of error:** This isn't a new issue, it just seems it was missed during 365e9cb6aa. This task was created as an extension of #74243 because #74243 was closed. ![Screenshot from 2020-05-19 17-27-50.png](https://archive.blender.org/developer/F8542456/Screenshot_from_2020-05-19_17-27-50.png) Edit: This may also be related: 5593efec01 **Exact steps for others to reproduce the error:** 1. Open Blender with default settings and a default startup scene. 2. Change to "Active Camera" view (Numberpad 0). 3. In the properties editor select the "Output" tab and enable "Stereoscopy". 4. 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 #74243 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. **Workaround:** Change shading to material mode once and the issue is gone.

Alaska commented

2020-05-19 07:32:18 +02:00

Added subscriber: @Alaska

blender-admin commented

2020-05-19 07:32:18 +02:00

#83873 was marked as duplicate of this issue

blender-admin commented

2020-05-19 07:32:18 +02:00

#79351 was marked as duplicate of this issue

Alaska commented

2020-05-19 07:32:40 +02:00

Removed subscriber: @Alaska

Alaska commented

2020-05-19 07:32:44 +02:00

Added subscriber: @Alaska

Clément Foucault was assigned by Alaska

2020-05-19 07:33:13 +02:00

Alaska commented

2020-05-19 07:34:26 +02:00

@fclem I have assigned you to this task as you worked on the fix for the other issue. Sorry if this task should be assigned to someone else.

Aaron Carlisle commented

2020-05-19 07:46:04 +02:00

Added subscriber: @Blendify

Aaron Carlisle commented

2020-05-19 07:46:04 +02:00

I cannot reproduce on windows.

Alaska commented

2020-05-19 07:57:04 +02:00

Looks like it may end up like #74243. A Nvidia only, Linux only issue. Will need more investigation to confirm this.

Philipp Oeser commented

2020-05-19 10:27:56 +02:00

Added subscriber: @lichtwerk

Philipp Oeser commented

2020-05-19 10:27:56 +02:00

Changed status from 'Needs Triage' to: 'Confirmed'

Philipp Oeser commented

2020-05-19 10:27:56 +02:00

I can confirm actually

System Information
Operating system: Linux-5.5.13-200.fc31.x86_64-x86_64-with-fedora-31-Thirty_One 64 Bits
Graphics card: GeForce GTX 970M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 440.64
version: 2.90 (sub 2), branch: master, commit date: 2020-05-19 03:31, hash: 1151bcd53d

I can confirm actually **System Information** Operating system: Linux-5.5.13-200.fc31.x86_64-x86_64-with-fedora-31-Thirty_One 64 Bits Graphics card: GeForce GTX 970M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 440.64 version: 2.90 (sub 2), branch: master, commit date: 2020-05-19 03:31, hash: `1151bcd53d`

Dalai Felinto commented

2020-05-19 10:44:50 +02:00

Added subscribers: @Jeroen-Bakker, @dfelinto

Dalai Felinto commented

2020-05-19 10:44:50 +02:00

@fclem @Jeroen-Bakker I can reproduce this on Linux btw using GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 440.44.

@Alaska for the record, refrain from tagging your own report as 2.83. The tag means the issue is planned to be tackled by 2.83, not that it happens in 2.83. But for now leave it as it is, since I hope this can be fixed for 2.83.

@fclem @Jeroen-Bakker I can reproduce this on Linux btw using `GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 440.44`. @Alaska for the record, refrain from tagging your own report as 2.83. The tag means the issue is planned to be tackled by 2.83, not that it happens in 2.83. But for now leave it as it is, since I hope this can be fixed for 2.83.

Alaska commented

2020-05-19 10:56:57 +02:00

In #76874#934497, @dfelinto wrote:
@Alaska for the record, refrain from tagging your own report as 2.83. The tag means the issue is planned to be tackled by 2.83, not that it happens in 2.83.

I will keep that in mind for future reports.

> In #76874#934497, @dfelinto wrote: > @Alaska for the record, refrain from tagging your own report as 2.83. The tag means the issue is planned to be tackled by 2.83, not that it happens in 2.83. I will keep that in mind for future reports.

Philipp Oeser commented

2020-05-19 11:26:55 +02:00

@fclem: Probably again something along the lines of the following?

P1403: T76874_snippet



diff --git a/source/blender/draw/engines/overlay/overlay_extra.c b/source/blender/draw/engines/overlay/overlay_extra.c
index af54e524445..0143c07e697 100644
--- a/source/blender/draw/engines/overlay/overlay_extra.c
+++ b/source/blender/draw/engines/overlay/overlay_extra.c
@@ -1140,6 +1140,12 @@ void OVERLAY_camera_cache_populate(OVERLAY_Data *vedata, Object *ob)
   const bool look_through = (is_active && (rv3d->persp == RV3D_CAMOB));
 
   const bool is_multiview = (scene->r.scemode & R_MULTIVIEW) != 0;
+
+  /* this works, but of course this doesnt really detect the CHANGE / UPDATE! */
+  if (is_multiview) {
+    rv3d->rflag |= RV3D_GPULIGHT_UPDATE;
+  }
+
   const bool is_stereo3d_view = (scene->r.views_format == SCE_VIEWS_FORMAT_STEREO_3D);
   const bool is_stereo3d_display_extra = is_active && is_multiview && (!look_through) &&
                                          ((v3d->stereo3d_flag) != 0);
diff --git a/source/blender/draw/engines/workbench/workbench_data.c b/source/blender/draw/engines/workbench/workbench_data.c
index 7b08e97ac31..891c6383ca6 100644
--- a/source/blender/draw/engines/workbench/workbench_data.c
+++ b/source/blender/draw/engines/workbench/workbench_data.c
@@ -188,6 +188,14 @@ void workbench_private_data_init(WORKBENCH_PrivateData *wpd)
       draw_ctx->object_edit, draw_ctx->obact, draw_ctx->object_mode);
 
   wpd->preferences = &U;
+
+  /* Tried this, but apparently wpd->scene is not ensure to be valid here? */
+  const bool wpd_multiview = wpd->scene ? (wpd->scene->r.scemode & R_MULTIVIEW) != 0 : false;
+  const bool scene_multiview = (scene->r.scemode & R_MULTIVIEW) != 0;
+  if (wpd_multiview != scene_multiview) {
+    wpd->view_updated = true;
+  }
+
   wpd->scene = scene;
   wpd->sh_cfg = draw_ctx->sh_cfg;

@fclem: Probably again something along the lines of the following? [P1403: T76874_snippet](https://archive.blender.org/developer/P1403.txt) ``` diff --git a/source/blender/draw/engines/overlay/overlay_extra.c b/source/blender/draw/engines/overlay/overlay_extra.c index af54e524445..0143c07e697 100644 --- a/source/blender/draw/engines/overlay/overlay_extra.c +++ b/source/blender/draw/engines/overlay/overlay_extra.c @@ -1140,6 +1140,12 @@ void OVERLAY_camera_cache_populate(OVERLAY_Data *vedata, Object *ob) const bool look_through = (is_active && (rv3d->persp == RV3D_CAMOB)); const bool is_multiview = (scene->r.scemode & R_MULTIVIEW) != 0; + + /* this works, but of course this doesnt really detect the CHANGE / UPDATE! */ + if (is_multiview) { + rv3d->rflag |= RV3D_GPULIGHT_UPDATE; + } + const bool is_stereo3d_view = (scene->r.views_format == SCE_VIEWS_FORMAT_STEREO_3D); const bool is_stereo3d_display_extra = is_active && is_multiview && (!look_through) && ((v3d->stereo3d_flag) != 0); diff --git a/source/blender/draw/engines/workbench/workbench_data.c b/source/blender/draw/engines/workbench/workbench_data.c index 7b08e97ac31..891c6383ca6 100644 --- a/source/blender/draw/engines/workbench/workbench_data.c +++ b/source/blender/draw/engines/workbench/workbench_data.c @@ -188,6 +188,14 @@ void workbench_private_data_init(WORKBENCH_PrivateData *wpd) draw_ctx->object_edit, draw_ctx->obact, draw_ctx->object_mode); wpd->preferences = &U; + + /* Tried this, but apparently wpd->scene is not ensure to be valid here? */ + const bool wpd_multiview = wpd->scene ? (wpd->scene->r.scemode & R_MULTIVIEW) != 0 : false; + const bool scene_multiview = (scene->r.scemode & R_MULTIVIEW) != 0; + if (wpd_multiview != scene_multiview) { + wpd->view_updated = true; + } + wpd->scene = scene; wpd->sh_cfg = draw_ctx->sh_cfg; ```

Zsolt Stefan commented

2020-05-19 11:35:28 +02:00

Added subscriber: @ZsoltStefan

Zsolt Stefan commented

2020-05-19 11:35:28 +02:00

I can confirm this also happens on Windows. I get a red/cyan checkerboard pattern in the upper part of the screen. If there are more 3D views open, and one is in camera view, then the other viewports also get the glitch even if they are not in camera view. Switching to Material Preview and back to solid shading solves the problem.

Operating system: Windows-10-10.0.18362-SP0 64 Bits
Graphics card: GeForce RTX 2080 with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 442.19
Broken: version: 2.90 (sub 2), branch: master, commit date: 2020-05-18 09:05, hash: f3edff2d7d

I can confirm this also happens on Windows. I get a red/cyan checkerboard pattern in the upper part of the screen. If there are more 3D views open, and one is in camera view, then the other viewports also get the glitch even if they are not in camera view. Switching to Material Preview and back to solid shading solves the problem. Operating system: Windows-10-10.0.18362-SP0 64 Bits Graphics card: GeForce RTX 2080 with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 442.19 Broken: version: 2.90 (sub 2), branch: master, commit date: 2020-05-18 09:05, hash: `f3edff2d7d`

Alaska commented

2020-05-19 12:06:50 +02:00

Removing the Linux project as @ZsoltStefan can reproduce the issue on Windows.

I am also able to reproduce the issue where other viewports get corrupted when one is in the camera view.

Removing the Linux project as @ZsoltStefan can reproduce the issue on Windows. I am also able to reproduce the issue where other viewports get corrupted when one is in the camera view.

Dalai Felinto commented

2020-05-27 17:37:38 +02:00

In the end this is a driver issue. And with a workaround (change once to material mode, and the issue is gone once you go back to solid). Moving this to known issue.

Clément Foucault was unassigned by Alaska

2020-06-02 05:53:02 +02:00

Alaska commented

2020-06-02 05:53:02 +02:00

Added subscriber: @fclem

Alaska commented

2020-07-29 06:19:20 +02:00

Added subscriber: @Rogo

Alaska commented

2020-12-17 07:23:13 +01:00

Added subscriber: @sundriftproductions

Aaron Carlisle commented

2020-12-17 08:48:22 +01:00

Removed subscriber: @Blendify

Patrick Mours commented

2021-01-05 13:04:42 +01:00

Added subscriber: @pmoursnv

Patrick Mours commented

2021-01-05 13:04:42 +01:00

This has been fixed with the r460 driver releases (Windows 460.79+, Linux 460.27.04+). Please try again and let me know if it can be closed.

Jeff Boller commented

2021-01-06 02:51:30 +01:00

@pmoursnv -- I installed driver version 460.89 for RTX/Quatro on Windows (https://www.nvidia.com/Download/driverResults.aspx/167756/en-us ) and the problem appears to have been fixed with this driver version.

I don't know if the problem is also resolved on Linux systems.

@pmoursnv -- I installed driver version 460.89 for RTX/Quatro on Windows (https://www.nvidia.com/Download/driverResults.aspx/167756/en-us ) and the problem appears to have been fixed with this driver version. I don't know if the problem is also resolved on Linux systems.

Alaska commented

2021-11-24 12:07:05 +01:00

I just thought I would update on this since it's been a while. I am still able to produce this bug, or something similar, with the setup below:

System Information
Operating system: Linux-5.15.0-1-amd64-x86_64-with-glibc2.32 64 Bits
Graphics card: NVIDIA GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 495.44

Blender Version 3.1.0

I just thought I would update on this since it's been a while. I am still able to produce this bug, or something similar, with the setup below: ![Rendering artifacts on Nvidia GPU.png](https://archive.blender.org/developer/F11979371/Rendering_artifacts_on_Nvidia_GPU.png) **System Information** Operating system: Linux-5.15.0-1-amd64-x86_64-with-glibc2.32 64 Bits Graphics card: NVIDIA GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 495.44 Blender Version 3.1.0

Dalai Felinto commented

2021-11-24 14:52:50 +01:00

The problem is also still here on:
Operating system: Linux-5.11.0-40-generic-x86_64-with-glibc2.31 64 Bits
Graphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.91.03

The problem is also still here on: Operating system: Linux-5.11.0-40-generic-x86_64-with-glibc2.31 64 Bits Graphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.91.03

Patrick Mours commented

2021-11-24 14:57:22 +01:00

Turns out this was accidentally only fixed on Windows, not Linux. I'll bring it up internally.

Alaska commented

2022-02-02 04:13:47 +01:00

Changed status from 'Confirmed' to: 'Resolved'

Alaska closed this issue

2022-02-02 04:13:47 +01:00

Alaska self-assigned this 2022-02-02 04:13:47 +01:00

Alaska commented

2022-02-02 04:13:47 +01:00

Linux Nvidia GPU driver 510.47.03 has this in the changelog:

Added an application profile to avoid an image corruption issue in Blender, as described at https://developer.blender.org/T76874
Source: https://www.nvidia.com/Download/driverResults.aspx/186156/en-us

And updating to GPU driver 510.47.03 does indeed fix the issue for me. As such I will be closing this report.

Linux Nvidia GPU driver 510.47.03 has this in the changelog: > Added an application profile to avoid an image corruption issue in Blender, as described at https://developer.blender.org/T76874 > Source: https://www.nvidia.com/Download/driverResults.aspx/186156/en-us And updating to GPU driver 510.47.03 does indeed fix the issue for me. As such I will be closing this report.

Alaska referenced this issue

2023-07-10 06:48:40 +02:00

Graphical glitch in viewport using stereoscopy #109874

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Enabling "Steroscopy" in the viewport camera causes graphical glitches with anti-aliasing enabled. #76874