My report is about the omission of any antialiasing in the viewport when enabled. However, I can see from T73494 that there might be some tiny changes in the viewport that I didn't notice in my testing when stepping through the sampling options. My case does not involve Edit mode. My scene generates output with missing edges when changing to specific sampling settings which are not persistent when switching focus back to the viewport with a mouseclick.

With No Anti-Aliasing set:

then switch to Single Pass Anti-Aliasing (the image disappears):

then switch to 5 Samples and you see grey silhouette edges (interior edges missing):

switching to 32 Samples appears to make no difference:

switching back to 5 Samples renders with thicker lines:

clicking back into the viewport redraws the scene with a quality of the No Anti-Aliasing option as in the first image in this post.

@Richard Antalik (ISS) The default cube exhibits this as in my first post. The steps involved can't be recorded to a blend file.

T75815: Viewport Glitches while changing viewport anti-aliasing settings looks like it got worse

Was this fixed in final release? It does resemble T75815 for sure.

No, this is not fixed. However, the inconsistent behaviour now appears more consistent. The scenes I used to test this initially still show aliased lines in the viewport and also in the output image when using View | Viewport Render Image to take a snapshot of the active viewport. This produces the same image irrespective of the sample settings in Quality | Viewport Antialiasing. The Overlay Smooth Wires option does appear to improve things slightly with few edges but most are still badly aliased.

@Paul McManus (PaulMc) Did you try updating your graphics driver? I know you were using 445.75 when reporting the bug, but the newest one is 451.48.

What you can also do is try launching blender using blender_debug_gpu_glitchworkaround.cmd and see if it changes anything.

Anyway could you attach the result of running blender_debug_gpu.cmd here so we can see if there is anything wrong. Also your system-info.txt would be nice.

Hi @Clément Foucault (fclem) , I was using 446.14 but have updated to 451.18 and the results are the same.

Here are the log files

Running blender_debug_gpu_glitchworkaround.cmd appeared not to make any difference.

This is quite strange as you have a quite usual setup and there is no other reports like this one. Can you try using factory startup to see if that does not come from an addon?

Running from blender_factory_startup.cmd made no difference. Is that a sufficient test?

To add to this a little (and repeat some earlier comments) my graphics card is noisy which means I can hear a sound when it is processing. When I open the Preferences dialog and change the sample settings there is a noise as if the screen is re-rendering but the on-screen image doesn't change. It is as if there is double-buffering in place but the buffer never gets switched. As I move down the sample settings to 32 the sound gets longer ~ 1/2 second on the last one (32) with a big scene and just a tiny click on the top one with no anti-aliasing. Changing that setting makes no difference to the screen image. The only option in this panel that appears to make any change is the Overlay Smooth Wires checkbox. I've now tried this on another computer and the results are the same. This was a laptop with a GTX 980M NVIDIA card. Will any still or video screen captures help?

@Paul McManus (PaulMc) Video capture can help to understand yes. BTW did you tried 2.81.1 and 2.90 alpha to see if it makes any difference?

Here are some screen captures and zoomed in areas from all three versions (2.81, 2.83 & 2.90). I didn't do every combination of settings, just a sample to show the differences. If there are any that you'd specifically like to see then please let me know.

I see nothing wrong in you aatest.pdf

I think you are just reporting that the antialiasing changed in 2.82. Yes it changed as we have completely rewritten how antialiasing is done for overlays. There was technical benefits for this choice but overlays and viewport render are antialiased separatedly. The dashed edges are one of the issues but I fixed it entirely in 2.83 if I remember correctly.

So to be clear:

• Viewport Anti-Aliasing: Should affect Shaded Outlines (the one you can change the color in shading pop-over) and shaded meshes.
• Smooth Wire: Should affect selection outline and all overlays (empties, wireframes, etc...).

I was under the impression that you were reporting that the wireframes disapeared under certain settings.

This is what this scene shoud looks like with smooth wires.

Sorry, @Clément Foucault (fclem) it sounds like my original post might have misled you.

I wasn't aware that the Viewport Anti-Aliasing option only applied to shaded outlines.

I also wasn't aware of the criteria for when Smooth Wire would be applied. Or that these two options were in face separate. The online documentation is confusing in this respect.

In my original report the "interior" lines (non-silhouette edges) did indeed disappear. However, that effect seems no longer reproducible.

I always thought that anti-aliasing would cause a perceived reduction or removal of the steps in a diagonal line normally associated with the underlying grid of pixels on the screen.

If you look in the sample I sent there are still jagged lines where I would have expected them to be a lot smoother. Also in some cases, particularly silhouette edges, the lines are broken with parts that are invisible - is this what you are referring to as the dashed edges issue?

Your sample image is also a lot lower resolution than my screen, and it looks like the lines are thicker. Is the fact that I'm on a 4K monitor a factor in this, perhaps?

Ha yes if you have DPI scalling to 2 or line thickness is big, the aliasing can be worse. But the dashed wire edges shouldn't be there which your images suggest it's not the case.

Other than that there is not issues.