Workbench x-ray, wireframe and anti-aliasing artifacts on NVIDIA / Linux #74243
Labels
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
11 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#74243
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
System Information
Operating system: Linux-5.3.0-40-generic-x86_64-with-debian-buster-sid 64 Bits
Graphics card: GeForce GTX 1080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 435.21
Blender Version
Broken: version: 2.83 (sub 5), branch: master, commit date: 2020-02-26 13:59, hash:
fe41c1ec0bWorked: 2.82a
Short description of error
Glitches in viewport in wireframe mode
Exact steps for others to reproduce the error
If you don't see the problem toggle shading between solid and wire
The problem disappear when Viewport Anti-Aliasing set to No or Single Anti-Aliasing
xray_wire_cube.blend
*For a heavier file check
01.anim.blendfrom the dweebs and go on wireframe mode.//
Added subscriber: @Dalkoom
#76447 was marked as duplicate of this issue
#76613 was marked as duplicate of this issue
#74735 was marked as duplicate of this issue
Added subscriber: @mano-wii
Changed status from 'Needs Triage' to: 'Needs User Info'
I don't know what to look for. I don't see any problem:
to see the artifacts you need to : first back to Object Mode then deselect the model .
the artifact gone when selecting any object . if the artifact disappear toggle shading mod between solid and wire.
this cube is subdivided with 100 cuts and
xray_wire_cube.blend
I still can't reproduce the problem.
But by the image, there is really something strange there.
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
System Information
Operating system: Linux-5.3.0-7629-generic-x86_64-with-debian-buster-sid 64 Bits
Graphics card: GeForce GTX 1080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 440.44
Blender Version
Broken: version: 2.83 (sub 7), branch: master, commit date: 2020-03-10 12:30, hash:
212660f467Worked: (optional)
Added subscriber: @Jewls
can confirm
build: 2020-03-11, hash:
33c6b269d1,windows 10xray 0- 0.99
xray value 1 solves the problem
xray_bug.blend
Changed status from 'Needs User Info' to: 'Needs Developer To Reproduce'
Added subscriber: @dfelinto
Changed status from 'Needs Developer To Reproduce' to: 'Confirmed'
I will keep this opens since the sample file is simpler.
Added subscriber: @Jeroen-Bakker
Problem in desplay wireframe while xray and Viewport Anti-Aliasing activatedto Problem in display wireframe while xray and Viewport Anti-Aliasing activatedPlayed with a heavier file and it seems to only affect occluded faces or something with depth.
Also changing wireframe in Viewport doesent change anything only Xray value 1 in Viewport Shading solves it.
Or if you set your user prefs Viewport Anti-aliasing to no Aliasing
(probably workbench refractor releated?)
Edit: it seems also to affect not occluded faces far away from viewport as you can see here:
Added subscriber: @brecht
Changed status from 'Confirmed' to: 'Needs User Info'
This looks similar to #75063 which appears to be fixed now, can anyone confirm?
Added subscriber: @ankitm
With the last branch it is More better , but the problem still with heavy scenes . to see the problem in a default cube : make a duplicate the subdivide it 100 cuts
Changed status from 'Needs User Info' to: 'Confirmed'
like salim3d said its a little bit better but not comleptely solved.
Changed status from 'Confirmed' to: 'Resolved'
This should be fixed by {a68bd94}, if not I can reopen the report.
I was happy with this fix . I couldn't reproduce the problem.
Until this build :
System Information
Operating system: Linux-5.3.0-7648-generic-x86_64-with-debian-buster-sid 64 Bits
Graphics card: GeForce GTX 1080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 440.64
Blender Version
Broken: version: 2.83 (sub 15), branch: master, commit date: 2020-04-27 19:14, hash:
133bf05b18with the previous scene : a simple cube and subdivided one with 100 cuts and toggle the shade mode between wire and solid
Added subscriber: @Alaska
@brecht To expand on @Dalkoom's comment, I can reproduce the same bug in 2.83
133bf05b18and 2.903ea67e08fewith Linux (5.3.0-7648 generic) and a GTX 1050ti 440.64.Steps to reproduce:
I also tested a few older builds I have on my computer:
2.90
fd0cb58122(2020-04-27 19:15) - Same visual glitch.2.83
d0d16eb7d3(2020-04-26 22:51) - Same visual glitch.2.83
a8441fc900(2020-04-24 15:23) - Same visual glitch.2.83
d712f1f83a(2020-04-23 21:07) - Same visual glitch.2.83
13e3a1c532(2020-04-21 17:59) - Same visual glitch.2.82a - Unable to reproduce as per the original report.
I did not test any further back as I don't have builds from before then.
I am unsure how to roll back video drivers on Linux, so I'm unable to test those. I will also be updating my Linux build to an Ubuntu 20.04 based distribution later this week with more up to date kernels. I will retest when I update.
Edit: Retested with a AMD GPU using the standard drivers that are built into the Linux kernel. Was unable to produce any errors.
This issue is either with the GPU driver or something with the Linux kernel we're using (My Nvidia and AMD system were using a different kernel).
I don't know if you would like to try and fix it on the Blender side of things or just wait until a new GPU driver/kernel comes out.
Interesting, retesting this I found something odd out about it. This only seems to affect meshes above Z=0. This includes part of a mesh. So if half of a cube is below Z=0 and the other half above Z=0, then only the top half is affected.
Changed status from 'Resolved' to: 'Needs Developer To Reproduce'
Retested. Here's what I've learned:
So I've narrowed it down to the Nvidia GPU driver. Which was already the suspicion.
@brecht Here's a video showing off the issue. As you can see, it's a bit hit and miss on whether the issue will occur. But so far it is most noticeable when:
Note: Most of the object context menus that pop up and me changing selection mode is because I loaded factory defaults which switched to left click select which I'm not used too.
2020-05-01 13-47-53.mp4
This comment was removed by @Dalkoom
I have tried to reproduce the issue in 2.90 version and found an interesting result :
The glitches appear just once the mouse is over the 3D cursor or one of the row axis
0001-0250.mp4
I haven't been able to reproduce the issue here with a Titan Xp, while I could reproduce similar glitches before.
@brecht Retested again in 2.83
ce76e17584(2020-05-08 14:49) and I still experience the issue.Are there any tests you would like me to run so you can collect the information needed to figure out what's going on? Or is this something that you just have to wait until it's reproducible on a computer you can access?
This bug is not in my area, I'm leaving it to another developer to figure out what the next steps are.
Okay.
To whomever it concerns. With 2.83 getting closer to release and more reports of issues like this (E.G. #76613), do you think it's a wise idea to set Blenders default anti-aliasing method to just single pass anti-aliasing until this is figured out? Also, to whoever makes that change, is it possible to force that setting to be changed for all users loading preferences from 2.82a? That way loads of bug reports can be avoided.
Added subscriber: @lastrodamo
Problem in display wireframe while xray and Viewport Anti-Aliasing activatedto Workbench x-ray, wireframe and anti-aliasing artifacts on NVIDIA / Linuxgood news @brecht your commit {a68bd94} seems to fixed the windows version with nvidea gpu, tested with the simple mountian scene also with a production ready.
And the glitched mountain scene from above is fixed after switching to edit mode and back.
Added subscriber: @MeshVoid
Don't know if it is related, experiencing some visual artifacts during weight painting in X-ray mode.
@MeshVoid It's related. It was reported with #76613 and merged with this task.
Added subscriber: @fclem
I cannot reproduce anymore either on GTX960 + Windows. So I think it's an issue in the linux version. We are using a special opengl extension to workaround this issue. So if the extension is not found, the workaround will not execute.
@Alaska Could you provide your
system_info.txthere?This is a screenshot of this bug on WIndows 10 64 bits, version: blender-2.83-eaee2b411935-windows64
It appears from certain angles only. Appears when you switch between the modes a lot and weight paint and select the bones etc., which you do quite a lot during rigging.
can confirm what @MeshVoid experienced on Windows 10 64 bit maybe we should reopen #76613 after renaming this to a linux task and due to the diffrent mode?
2020-05-11 17-05-41.mkv
Also found this :)
@MeshVoid & @Jewls Thanks for the feedback but please put your system_info.txt as attachment in your comment. We need the full infos.
Also note that the workaround is the default.
I'm going to test in weightpaint right away.
system-info.txt
@fclem could this be a hint of whats going wrong : in weight mode without xray and only wireframe shading the outlines are fractured
but if you turn on xray the outlines are normal again but the glitches happen.
youre a genius @fclem just compiled it again and see:
2020-05-11 18-08-42.mp4
Changed status from 'Needs Developer To Reproduce' to: 'Resolved'
Thanks to everyone involved!
Added subscribers: @viadvena, @iss, @antoniov
Wow thank you Clement
I can’t wait to test this new build
Excellent work .
It's been addressed with
542ff416e2Thank you @fclem, the patch seems to be working.