Page MenuHome

Vertex flickering on high grid density mesh
Needs Information from Developers, NormalPublicBUG

Description

System Information
Operating system: Windows-10-10.0.18362-SP0 64 Bits
Graphics card: GeForce GTX 780/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 442.59

Blender Version
Broken: version: 2.82 (sub 7), branch: master, commit date: 2020-03-12 05:06, hash: rB375c7dc4caf4
Worked: (optional)

Short description of error
When a relatively high grid density is reached the vertices flicker
2.81 does not have such problems
The method of creating a dense grid does not make a difference
https://yadi.sk/i/lrehEGrTkCXMvQ

Exact steps for others to reproduce the error
On default cube, tab. (edit mode)
right click on cube, subdivide.
adjust last operation, cuts = 20. shake mouse to see glitches.

video: F8414488

Event Timeline

ronsn changed the task status from Needs Triage to Needs Information from User.EditedMar 15 2020, 6:29 AM
ronsn added a subscriber: ronsn.

You didn't include any detailed issue in your report, nor exact steps to reproduce an issue. So please fill in the requested fields, so we can reproduce that issue. :)

Yes, in principle, everything is simple, when opening a file (all settings are standard and updated drivers), any object that has a fairly dense grid, in the video clip everything is clear when editing flickers.
https://yadi.sk/d/6DzRyEjDh5-dcQ

This starts right from opening the file , specifically in this example I did subdive using the context menu in the viewport, but it works with any grid subdivision method. It also happens only on my computer, I tested it on a desktop in the office and everything is fine there (1080 ti). 2.81 has no such problems

cannot redo despite 100 cuts with the steps in the video on *. Test on v2.82a and daily build at https://builder.blender.org

*rB82c51d0edbab45f014b4d0b4c0a96c000c46e232
Operating system: Darwin-18.7.0-x86_64-i386-64bit 64 Bits
Graphics card: Intel(R) HD Graphics 6000 Intel Inc. 4.1 INTEL-12.10.12

Ankit Meel (ankitm) renamed this task from Vertex flickering to Vertex flickering on high grid density mesh .Mar 18 2020, 9:37 PM
Ankit Meel (ankitm) updated the task description. (Show Details)
Ankit Meel (ankitm) added a comment.EditedMar 19 2020, 10:24 AM

Like

  • T74243 Problem in display wireframe while xray and Viewport Anti-Aliasing activated and
  • T74663 GPencil – Fills are Flickering
  • T74416 Background image and Xray mode produces checkered pattern

this could also be Nvidia GTX specific. (not sure about OS)

the latest posted version 2.83 has the same problem

I also cannot reproduce the problem.
Does this happen in mixed selection mode? Vertex + edge + face for example.

@Ankit Meel (ankitm), I don't think T74847 is the same bug.


Operating system: Windows-10-10.0.18941 64 Bits
Graphics card: Radeon (TM) RX 480 Graphics ATI Technologies Inc. 4.5.13586 Core Profile Context 19.50.01.05 26.20.15001.5006

Yes, but the error only applies to vertexes.
I tried removing vertex smoothing, tried in Cycles and so on, and the error persists.
Since there is no such error on 1080ti as in version 2.81, so most likely the problem is in some new vertex visualization methods in 2.82 that do not work for my video card, the latest alpha version 2.83 also has this error (downloaded today)

Please check on 2.83. https://builder.blender.org Also mention the hash when reporting back. Thanks

Tested the latest build, the error on the spot

I noticed this pattern: the pattern and location of broken vertexes change as soon as the viewport is updated, when the rotation stops, the viewport camera counts samples and the flicker freezes.
Flickering is only typical for vertexes.
The nature of changes to these vertexes is related to the color of the vertexes, which changes in the range from selected to unselected vertexes.

T75063: Wireframe Drawing Errors has been fixed, please check again. If not, it can be confirmed

The error remained

Ankit Meel (ankitm) changed the task status from Needs Information from User to Confirmed.Apr 1 2020, 12:45 PM

Since this problem is there in 2.82a, reported as working in T74243: Workbench x-ray, wireframe and anti-aliasing artifacts on NVIDIA / Linux , confirming separately.

https://skr.sh/v1ZEu9zP7vo

Good day, today I made retopology of another project and this bug with vertices looks like this interesting, it looks suspiciously like another glitch that is in conjunction with mine

Brecht Van Lommel (brecht) changed the task status from Confirmed to Needs Information from User.Apr 23 2020, 12:58 PM

@Evgeny (xvision), can you test if this still happens in the latest build?

There was a fix T75477 which may be related. But it may also not be, since the artifacts look different and there is no X-ray here.

Brecht Van Lommel (brecht) lowered the priority of this task from High to Normal.Apr 23 2020, 1:07 PM

Removing as 2.83 release blocker since I think this is the only report we've had with these artifacts, and no developer has been able to reproduce it so far. So we can't realistically promise this to be fixed.

Yes, the glitch remained

Clément Foucault (fclem) changed the task status from Needs Information from User to Needs Information from Developers.Apr 27 2020, 8:17 PM

What kind of information do you need? I could help.

This error only shows on versions after the 2.81a
Could be a driver or something?

But playing with the antilaising option I've noticed that the more you add (x16 for example) the more it appears before rendering completely.

After the full viewport render the error didn't show up. But, then I move the camera and appear again.

Anyway, this error only happens when you're in edit mode with "vertex select", this doesn't happen with "edge select" nor with "face select".

@Evgeny (xvision) Do you still have this problem? Lot of time has passed, it is possible this has been resolved already.

Lamia added a subscriber: Lamia.EditedMay 6 2021, 6:45 AM

I've had this issue for a very long time now. Currently using 3.0 and 2.93 and still have it. this was recorded on 3.0 with everything completely reset to default. same results on 2.8 and 2.9 as well.

Should probably also mention i have 780Ti x3 and a i7 3930k on latest windows 10.