Graphical glitch in viewport using stereoscopy #109874

New Issue

Damien Picard · 2023-07-09T16:40:04+02:00

Damien Picard commented

2023-07-09 16:40:04 +02:00

System Information
Operating system: Linux-6.2.0-24-generic-x86_64-with-glibc2.37 64 Bits, X11 UI
Graphics card: NVIDIA GeForce RTX 3060 Laptop GPU/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 535.54.03

Blender Version
Broken: version: 4.0.0 Alpha, branch: main, commit date: 2023-07-08 02:41, hash: c677f791f063
Worked: 3.6.0

Short description of error
Upon enabling Stereoscopy, a graphical glitch appears in the viewport. It kind of looks like a graphics driver issue but I’m using the most up-to-date available from Nvidia on Ubuntu.

Exact steps for others to reproduce the error

stereo_glitch.blend or factory startup
Go to camera view
Enable Stereoscopy.

**System Information** Operating system: Linux-6.2.0-24-generic-x86_64-with-glibc2.37 64 Bits, X11 UI Graphics card: NVIDIA GeForce RTX 3060 Laptop GPU/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 535.54.03 **Blender Version** Broken: version: 4.0.0 Alpha, branch: main, commit date: 2023-07-08 02:41, hash: `c677f791f063` Worked: 3.6.0 **Short description of error** Upon enabling Stereoscopy, a graphical glitch appears in the viewport. It kind of looks like a graphics driver issue but I’m using the most up-to-date available from Nvidia on Ubuntu. ![image](/attachments/4e8d4159-3368-4984-9bf7-de8ec0aaccd7) **Exact steps for others to reproduce the error** - [stereo_glitch.blend](/attachments/112c5618-8a33-4823-a116-2239b26a4ca2) or factory startup - Go to camera view - Enable Stereoscopy.

stereo_glitch.blend

874 KiB

image.png

588 KiB

Damien Picard added the

labels 2023-07-09 16:40:05 +02:00

Pratik Borhade commented

2023-07-10 05:49:02 +02:00

Can't replicate on Windows (4.0, 4da96623ffe9b75c677224037d95f37fb2e60097).
@lichtwerk , can you check?

**System Information**
Operating system: Windows-10-10.0.22000-SP0 64 Bits
Graphics card: NVIDIA GeForce RTX 3050 Laptop GPU/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 532.03

Can't replicate on Windows (4.0, `4da96623ffe9b75c677224037d95f37fb2e60097`). @lichtwerk , can you check? ``` **System Information** Operating system: Windows-10-10.0.22000-SP0 64 Bits Graphics card: NVIDIA GeForce RTX 3050 Laptop GPU/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 532.03 ```

Alaska commented

2023-07-10 06:42:06 +02:00

There was a bug very similar to this back when Blender 2.80 or 2.83 or something was in-development.

It was an issue that impacted Nvidia GPUs only, and only occurred if anti-aliasing was enabled in the viewport (Anti-aliasing can be configured in the Blender preferences Edit -> Preferences -> Viewport -> Quality -> Viewport Anti-Aliasing).

I believe a work around was put in Blender, along with Nvidia releasing a driver update for it. However, the driver update for Linux was accidentally missed. I believe the fix was finally released on Linux, but maybe it's been removed by accident again.

Note: I can not reproduce this issue on Windows with a RTX 4090. This might be a Linux+Nvidia only issue.

There was a bug very similar to this back when Blender 2.80 or 2.83 or something was in-development. It was an issue that impacted Nvidia GPUs only, and only occurred if anti-aliasing was enabled in the viewport (Anti-aliasing can be configured in the Blender preferences `Edit -> Preferences -> Viewport -> Quality -> Viewport Anti-Aliasing`). I believe a work around was put in Blender, along with Nvidia releasing a driver update for it. However, the driver update for Linux was accidentally missed. I believe the fix was finally released on Linux, but maybe it's been removed by accident again. Note: I can not reproduce this issue on Windows with a RTX 4090. This might be a Linux+Nvidia only issue.

Alaska commented

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

#76874

https://projects.blender.org/blender/blender/issues/76874

👍 3

YimingWu commented

2023-07-10 11:06:09 +02:00

Yepp. I can reproduce with linux and nvidia K5100M, this seems to be a very old bug.

Edit: the driver version I'm using is no longer updated by nvidia so I probably have to settle with what I have, but not sure if you could update your driver and see the difference. Any luck using distribution-specific drivers (like ubuntu ppa) instead of from nvidia .run driver?

Yepp. I can reproduce with linux and nvidia K5100M, this seems to be a very old bug. Edit: the driver version I'm using is no longer updated by nvidia so I probably have to settle with what I have, but not sure if you could update your driver and see the difference. Any luck using distribution-specific drivers (like ubuntu ppa) instead of from nvidia `.run` driver?

Damien Picard commented

2023-07-10 12:40:41 +02:00

Any luck using distribution-specific drivers (like ubuntu ppa) instead of from nvidia .run driver?

I’m using the Nvidia drivers straight from Ubuntu.

> Any luck using distribution-specific drivers (like ubuntu ppa) instead of from nvidia `.run` driver? I’m using the Nvidia drivers straight from Ubuntu. ![image](/attachments/32d11673-efb4-4668-b181-f0414f427e79)

image.png

145 KiB

Philipp Oeser commented

2023-07-13 10:43:10 +02: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.

@pioverfour : can you check if there is a specific Application Profile for Blender in the Nvidia driver settings that works for you?
(not sure if I understand the changelog correctly, dont currently have access to my nvidia GPU)

> 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. > > @pioverfour : can you check if there is a specific Application Profile for Blender in the Nvidia driver settings that works for you? (not sure if I understand the changelog correctly, dont currently have access to my nvidia GPU)

Philipp Oeser added

Status

Needs Information from User

and removed

Status

Needs Triage

labels 2023-07-13 10:43:28 +02:00

Damien Picard commented

2023-07-13 18:47:40 +02:00

can you check if there is a specific Application Profile for Blender in the Nvidia driver settings that works for you?

Sorry, I don’t understand how these work, there is no profile to be selected from the Nvidia settings, just an interface to create one with key-value pairs. Neither the linked changelog nor the task give information about which settings to add. Maybe I don’t have the right driver but I’d rather stick with the Ubuntu-provided ones.

> can you check if there is a specific Application Profile for Blender in the Nvidia driver settings that works for you? Sorry, I don’t understand how these work, there is no profile to be selected from the Nvidia settings, just an interface to create one with key-value pairs. Neither the linked changelog nor the task give information about which settings to add. Maybe I don’t have the right driver but I’d rather stick with the Ubuntu-provided ones. ![image](/attachments/5fc86bc0-aeda-44de-bce8-23225ee25987)

image.png

46 KiB

Alaska commented

2023-07-14 03:14:57 +02:00

@pioverfour We should start by confirming is this is the same issue as was previously reported.

Does the issue remain if you disable anti-aliasing (Edit -> Preferences -> Viewport -> Quality -> Viewport Anti-Aliasing)? If it does, then it's not the same issue.
If the issue disappears after disabling anti-aliasing, then it would suggest we're dealing with a similar, if not the same issue as before.

The issue reported back in the Blender 2.83 times was fixed with a Nvidia driver update. All you had to do was update your GPU driver and it was done. The "Application profile" that was added is an internal application profile and was automatically applied. With the right software you can view and/or edit that profile, but I don't know of any software that supports Linux that does that.

One possible cause for this issue reappearing could be that the application profile mentioned in the change log has been removed in newer versions of the GPU driver. And so updating to the latest GPU driver may actually make the issue re-appear. But this is purely speculation. It should also be noted. That if the profile was removed from the driver, then the issue would re-appear in other versions of Blender too, like Blender 3.6.

In your original report you mentioned everything works in Blender 3.6, but it's broken in 4.0. This implies that a change was made to the Blender source code that resulted in the issue re-appearing. Since various people are unable to reproduce the issue with their computers and Blender 4.0s, it's likely that the issue is still with the driver somehow. As in, something was changed in the Blender source code, and now the Application profile found in the Nvidia driver doesn't fix the issue. AS for why it impacts Linux only, I don't know. We also don't know if it's Linux only since we've only had a limited number of tests.

@pioverfour We should start by confirming is this is the same issue as was previously reported. - Does the issue remain if you disable anti-aliasing (`Edit -> Preferences -> Viewport -> Quality -> Viewport Anti-Aliasing`)? If it does, then it's not the same issue. - If the issue disappears after disabling anti-aliasing, then it would suggest we're dealing with a similar, if not the same issue as before. The issue reported back in the Blender 2.83 times was fixed with a Nvidia driver update. All you had to do was update your GPU driver and it was done. The "Application profile" that was added is an internal application profile and was automatically applied. With the right software you can view and/or edit that profile, but I don't know of any software that supports Linux that does that. One possible cause for this issue reappearing could be that the application profile mentioned in the change log has been removed in newer versions of the GPU driver. And so updating to the latest GPU driver may actually make the issue re-appear. **But this is purely speculation**. It should also be noted. That if the profile was removed from the driver, then the issue would re-appear in other versions of Blender too, like Blender 3.6. --- In your original report you mentioned everything works in Blender 3.6, but it's broken in 4.0. This implies that a change was made to the Blender source code that resulted in the issue re-appearing. Since various people are unable to reproduce the issue with their computers and Blender 4.0s, it's likely that the issue is still with the driver somehow. As in, something was changed in the Blender source code, and now the Application profile found in the Nvidia driver doesn't fix the issue. AS for why it impacts Linux only, I don't know. We also don't know if it's Linux only since we've only had a limited number of tests.

Damien Picard commented

2023-07-14 14:14:33 +02:00

@Alaska Thanks a lot for the detailed explanations and procedure!

Does the issue remain if you disable anti-aliasing (Edit -> Preferences -> Viewport -> Quality -> Viewport Anti-Aliasing)?

You were right, the issue disappears on disabling anti-aliasing (and reappears on re-enabling it).

The "Application profile" that was added is an internal application profile and was automatically applied.

Ahh I didn’t know about these, thanks.

One possible cause for this issue reappearing could be that the application profile mentioned in the change log has been removed in newer versions of the GPU driver.

I tested with versions 525 and 470 of the driver and still had the issue so I don’t think that is the case.

In your original report you mentioned everything works in Blender 3.6, but it's broken in 4.0.

I confirm this after trying both versions with all three drivers.

This implies that a change was made to the Blender source code that resulted in the issue re-appearing.

I started bisecting but I won’t have time to finish until Monday. I’ll update then.

@Alaska Thanks a lot for the detailed explanations and procedure! > - Does the issue remain if you disable anti-aliasing (`Edit -> Preferences -> Viewport -> Quality -> Viewport Anti-Aliasing`)? You were right, the issue disappears on disabling anti-aliasing (and reappears on re-enabling it). > The "Application profile" that was added is an internal application profile and was automatically applied. Ahh I didn’t know about these, thanks. > One possible cause for this issue reappearing could be that the application profile mentioned in the change log has been removed in newer versions of the GPU driver. I tested with versions 525 and 470 of the driver and still had the issue so I don’t think that is the case. > In your original report you mentioned everything works in Blender 3.6, but it's broken in 4.0. I confirm this after trying both versions with all three drivers. > This implies that a change was made to the Blender source code that resulted in the issue re-appearing. I started bisecting but I won’t have time to finish until Monday. I’ll update then.

Alaska commented

2023-07-15 02:52:35 +02:00

I tested with versions 525 and 470 of the driver and still had the issue so I don’t think that is the case.

Just for the record, the fix wasn't included until a 510 driver. So reverting to 470 basically guarantees you'll have the issue.

> I tested with versions 525 and 470 of the driver and still had the issue so I don’t think that is the case. Just for the record, the fix wasn't included until a 510 driver. So reverting to 470 basically guarantees you'll have the issue.

👍 1 👀 1

Damien Picard commented

2023-07-16 19:26:27 +02:00

Well, now I can’t reproduce the issue any more, whatever I try… If it comes up again, I’ll let you know.

👀 1

Pratik Borhade commented

2023-08-04 07:35:23 +02:00

Well, now I can’t reproduce the issue any more, whatever I try… If it comes up again, I’ll let you know.

Hi @pioverfour , any updates?

> Well, now I can’t reproduce the issue any more, whatever I try… If it comes up again, I’ll let you know. Hi @pioverfour , any updates?

Damien Picard commented

2023-08-04 08:23:58 +02:00

Hi @PratikPB2123, no the issue hasn’t come up again. Is it better to close the issue for now or leave it open in case anyone can reproduce?

Pratik Borhade commented

2023-08-04 11:24:58 +02:00

Thanks :)

open in case anyone can reproduce?

I'd prefer to close the report. So far only @ChengduLittleA is able to confirm but Yiming don't have access to newer drivers :)
BTW, which changes in system has solved the issue at your end?

Thanks :) > open in case anyone can reproduce? I'd prefer to close the report. So far only @ChengduLittleA is able to confirm but Yiming don't have access to newer drivers :) BTW, which changes in system has solved the issue at your end?

Damien Picard commented

2023-08-04 11:47:49 +02:00

BTW, which changes in system has solved the issue at your end?

Ahh wait on testing it’s doing it again! But this time it’s happening after a GPU driver update, and during this update the screen went dark and I had to restart the machine. I wouldn’t be surprised if the driver installation couldn’t complete and was left in a broken state or something.

I’ll try to bisect again later today, and I’ll close the issue if it doesn’t work.

> BTW, which changes in system has solved the issue at your end? Ahh wait on testing it’s doing it again! But this time it’s happening after a GPU driver update, and during this update the screen went dark and I had to restart the machine. I wouldn’t be surprised if the driver installation couldn’t complete and was left in a broken state or something. I’ll try to bisect again later today, and I’ll close the issue if it doesn’t work.

Damien Picard commented

2023-08-04 18:05:55 +02:00

I tried bisecting but the result is incoherent and after a few minutes the issues stops occurring even with a build in which it previously did…

I don’t quite know how to proceed so I’ll close the issue for now.

I tried bisecting but the result is incoherent and after a few minutes the issues stops occurring even with a build in which it previously did… I don’t quite know how to proceed so I’ll close the issue for now.

Damien Picard closed this issue

2023-08-04 18:05:57 +02:00

Blender Bot added

Status

Archived

and removed

Status

Needs Information from User

labels 2023-08-04 18:05:59 +02:00

Pratik Borhade commented

2023-08-07 04:41:41 +02:00

ok, thanks for investigating.