Vertex flickering on high grid density mesh #74766

Open
opened 2020-03-14 21:22:47 +01:00 by Evgeny · 38 comments

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: 375c7dc4ca
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.
{F8414482, layout = inline}{F8414484, layout = inline}
video: F8414488

**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: `375c7dc4ca` 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. {[F8414482](https://archive.blender.org/developer/F8414482/Скриншот_16-03-2020_133135.png), layout = inline}{[F8414484](https://archive.blender.org/developer/F8414484/Скриншот_16-03-2020_133204.png), layout = inline} video: [F8414488](https://archive.blender.org/developer/F8414488/Видео_14-03-2020_23_11_01.mp4)
Author

Added subscriber: @xvision

Added subscriber: @xvision

#76515 was marked as duplicate of this issue

#76515 was marked as duplicate of this issue

#74847 was marked as duplicate of this issue

#74847 was marked as duplicate of this issue

Added subscriber: @ronsn

Added subscriber: @ronsn

Changed status from 'Needs Triage' to: 'Needs User Info'

Changed status from 'Needs Triage' to: 'Needs User Info'

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. :)

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. :)
Author

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

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
Member

Added subscriber: @ankitm

Added subscriber: @ankitm
Member

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

*82c51d0edb
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

cannot redo despite 100 cuts with the steps in the video on *. Test on v2.82a and daily build at https://builder.blender.org *`82c51d0edb` 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 changed title from Vertex flickering to Vertex flickering on high grid density mesh 2020-03-18 21:37:27 +01:00
Member

Like

  • #74243 Problem in display wireframe while xray and Viewport Anti-Aliasing activated and
  • #74663 GPencil – Fills are Flickering
  • #74416 Background image and Xray mode produces checkered pattern
    this could also be Nvidia GTX specific. (not sure about OS)
Like - #74243 Problem in display wireframe while xray and Viewport Anti-Aliasing activated and - #74663 GPencil – Fills are Flickering - #74416 Background image and Xray mode produces checkered pattern this could also be Nvidia GTX specific. (not sure about OS)
Member

Added subscribers: @JulienKaspar, @mano-wii

Added subscribers: @JulienKaspar, @mano-wii
Author

the latest posted version 2.83 has the same problem

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.

@ankitm, I don't think #74847 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

I also cannot reproduce the problem. Does this happen in mixed selection mode? Vertex + edge + face for example. @ankitm, I don't think #74847 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
Author

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)

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)
Member

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

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

Tested the latest build, the error on the spot

Tested the latest build, the error on the spot
Author

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.

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.
Author
https://skr.sh/v1P0QmCYlXt
Member

#75063 (Wireframe Drawing Errors) has been fixed, please check again. If not, it can be confirmed

#75063 (Wireframe Drawing Errors) has been fixed, please check again. If not, it can be confirmed
Author

The error remained

The error remained
Member

Changed status from 'Needs User Info' to: 'Confirmed'

Changed status from 'Needs User Info' to: 'Confirmed'
Member

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

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

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

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

Added subscriber: @brecht
Removed subscriber: @JulienKaspar

Added subscriber: @brecht Removed subscriber: @JulienKaspar

Changed status from 'Confirmed' to: 'Needs User Info'

Changed status from 'Confirmed' to: 'Needs User Info'

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

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

@xvision, can you test if this still happens in the latest build? There was a fix #75477 which may be related. But it may also not be, since the artifacts look different and there is no X-ray here.

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.

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.
Author

Yes, the glitch remained

Yes, the glitch remained

Changed status from 'Needs User Info' to: 'Needs Developer To Reproduce'

Changed status from 'Needs User Info' to: 'Needs Developer To Reproduce'

Added subscriber: @Inkcloud

Added subscriber: @Inkcloud

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

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?

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.

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".

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**".

Added subscriber: @iss

Added subscriber: @iss

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

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

Added subscriber: @MaybeLamia

Added subscriber: @MaybeLamia

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.

2021-05-06_14-42-25.mp4

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. [2021-05-06_14-42-25.mp4](https://archive.blender.org/developer/F10055879/2021-05-06_14-42-25.mp4)
Philipp Oeser removed the
Interest
EEVEE & Viewport
label 2023-02-09 15:15:00 +01:00
Sign in to join this conversation.
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
10 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#74766
No description provided.