Overlays not displayed for UV seams, freestyle edges and sharp edges #109780

Closed
opened 2023-07-06 14:47:07 +02:00 by aperitero · 23 comments

System Information
Operating system: Linux-5.4.244-2-MANJARO-x86_64-with-glibc2.37 64 Bits, X11 UI
Graphics card: Mesa Intel(R) HD Graphics 4600 (HSW GT2) Intel 4.6 (Core Profile) Mesa 23.0.4

Blender Version
Broken: version: 3.6.0, branch: blender-v3.6-release, commit date: 2023-06-27 08:08, hash: c7fc78b81ecb
Worked: (newest version of Blender that worked as expected)

Short description of error

When marking edges as UV seams, these edges' display does not change accordingly, even though the option "Seams" is activated in "Viewport Overlays".

Exact steps for others to reproduce the error

[Based on the default startup]

  • Select the cube and switch to edit mode.
  • Select some edges and mark them as seams for UV unwrapping.
  • These edges are not displayed differently than the others.

See the attached image where some edges have been marked as seams. I also attached the blend file used for this screenshot.

**System Information** Operating system: Linux-5.4.244-2-MANJARO-x86_64-with-glibc2.37 64 Bits, X11 UI Graphics card: Mesa Intel(R) HD Graphics 4600 (HSW GT2) Intel 4.6 (Core Profile) Mesa 23.0.4 **Blender Version** Broken: version: 3.6.0, branch: blender-v3.6-release, commit date: 2023-06-27 08:08, hash: `c7fc78b81ecb` Worked: (newest version of Blender that worked as expected) **Short description of error** When marking edges as UV seams, these edges' display does not change accordingly, even though the option "Seams" is activated in "Viewport Overlays". **Exact steps for others to reproduce the error** [Based on the default startup] - Select the cube and switch to edit mode. - Select some edges and mark them as seams for UV unwrapping. - These edges are not displayed differently than the others. See the attached image where some edges have been marked as seams. I also attached the blend file used for this screenshot.
aperitero added the
Type
Report
Status
Needs Triage
Priority
Normal
labels 2023-07-06 14:47:07 +02:00
Author

I've just tested a bit further: the UV seams were correctly displayed until Blender 3.3.0 but not anymore in Blender 3.4.0. I'm also attaching my system info.

I've just tested a bit further: the UV seams were correctly displayed until Blender 3.3.0 but not anymore in Blender 3.4.0. I'm also attaching my system info.
Member

Hi, thanks for the report. Unable to confirm this on windows (3.6)
Does this happen after factory reset?: File > Defaults > Load Factory Settings
Perhaps an old intel GPU is responsible for these missing "UV seam" overlay?

Hi, thanks for the report. Unable to confirm this on windows (3.6) Does this happen after factory reset?: `File > Defaults > Load Factory Settings` Perhaps an old intel GPU is responsible for these missing "UV seam" overlay?
Pratik Borhade added
Status
Needs Information from User
and removed
Status
Needs Triage
labels 2023-07-07 06:02:05 +02:00
Author

Hi, yes it still does happen with the default factory settings. Indeed, it might be related to my GPU. It being old, do you mean that it's not officially supported by Blender ?

Hi, yes it still does happen with the default factory settings. Indeed, it might be related to my GPU. It being old, do you mean that it's not officially supported by Blender ?
Member

Thanks. GPU is still supported.
Do you see any error in terminal due to missing UV-seam drawing? (you may notice OpenGL warnings)

Thanks. GPU is still supported. Do you see any error in terminal due to missing UV-seam drawing? (you may notice OpenGL warnings)
Author

Hi, so I dug a bit further into the issue:

  • I don't get any OpenGL warnings (I've tried using --debug --debug-gpu flags).
  • It not only affects UV seams overlays, but also freestyle edges and sharp edges overlays (while bevel and crease overlays work well).
  • The overlays work fine when I compile blender myself (v3.6.0) (I eventually had to clear the GLSL cache but I don't quite understand why).

Being unable to reproduce the bug after compiling makes it even harder to debug, so I will stop my investigation for now.

Hi, so I dug a bit further into the issue: - I don't get any OpenGL warnings (I've tried using --debug --debug-gpu flags). - It not only affects UV seams overlays, but also freestyle edges and sharp edges overlays (while bevel and crease overlays work well). - The overlays work fine when I compile blender myself (v3.6.0) (I eventually had to clear the GLSL cache but I don't quite understand why). Being unable to reproduce the bug after compiling makes it even harder to debug, so I will stop my investigation for now.
aperitero changed title from UV seams not visible to Overlays not displayed for UV seams, freestyle edges and sharp edges 2023-07-08 10:24:46 +02:00
Member

Thanks. @ChengduLittleA , can you check? I think you've intel GPU.

Thanks. @ChengduLittleA , can you check? I think you've intel GPU.
Pratik Borhade added
Status
Needs Triage
and removed
Status
Needs Information from User
labels 2023-07-10 04:15:01 +02:00
Member

@PratikPB2123 Works fine here on my UHD 620 and Ubuntu 20.04. From the version string it looks like should be fine.

@aperitero Do you have other apparent visual artefact on this hardware? It is also possible that using a slightly different Mesa driver can help. I'm not that familiar with Manjaro but Ubuntu has some other PPAs providing newer drivers, Manjaro probably has the same thing.

@PratikPB2123 Works fine here on my `UHD 620` and `Ubuntu 20.04`. From the version string it looks like should be fine. @aperitero Do you have other apparent visual artefact on this hardware? It is also _possible_ that using a slightly different Mesa driver can help. I'm not that familiar with Manjaro but Ubuntu has some other PPAs providing newer drivers, Manjaro probably has the same thing.
Pratik Borhade added the
Platform
Linux
label 2023-07-11 06:58:26 +02:00
Author

@ChengduLittleA No I don't any other apparent visual artefact.

There is a new version of Mesa in the testing branch of Manjaro (23.1.3 instead of 23.0.4), I'll test it when it's released. There is also the Mesa-git package that I may try if nothing else works.

As I mentioned before, the version of Blender I've compiled myself works fine. So there might be something with the libraries used for the compilation.

Thank you both for your help.

@ChengduLittleA No I don't any other apparent visual artefact. There is a new version of Mesa in the testing branch of Manjaro (23.1.3 instead of 23.0.4), I'll test it when it's released. There is also the Mesa-git package that I may try if nothing else works. As I mentioned before, the version of Blender I've compiled myself works fine. So there might be something with the libraries used for the compilation. Thank you both for your help.
Member

The overlays work fine when I compile blender myself

Are you using the version from your linux distro then?
Or downloaded form blender.org?
Are the builds from https://builder.blender.org/download/daily/ fine?

>The overlays work fine when I compile blender myself Are you using the version from your linux distro then? Or downloaded form blender.org? Are the builds from https://builder.blender.org/download/daily/ fine?
Philipp Oeser added
Status
Needs Information from User
and removed
Status
Needs Triage
labels 2023-07-20 11:30:58 +02:00
Author

Are you using the version from your linux distro then?
Or downloaded form blender.org?
Are the builds from https://builder.blender.org/download/daily/ fine?

I have tried all of them and in all of them the bug appears: 3.6.0 shipped with Manjaro, 3.6.0 from Blender's official releases, 3.6.1-stable+v36.8bda729ef4dc and 4.0.0-alpha+main.08f4f1f41e52 from Blender's daily builds.

Only when I compile myself does the bug disappear. However, when I do so, I don't use the same flags and libs than the ones used by Manjaro or Blender. So eventually I may try to do an exact release build and see if it works.

> Are you using the version from your linux distro then? > Or downloaded form blender.org? > Are the builds from https://builder.blender.org/download/daily/ fine? I have tried all of them and in all of them the bug appears: 3.6.0 shipped with Manjaro, 3.6.0 from Blender's official releases, 3.6.1-stable+v36.8bda729ef4dc and 4.0.0-alpha+main.08f4f1f41e52 from Blender's daily builds. Only when I compile myself does the bug disappear. However, when I do so, I don't use the same flags and libs than the ones used by Manjaro or Blender. So eventually I may try to do an exact release build and see if it works.
Member

That would be interesting, yes

That would be interesting, yes
Member

That would be interesting, yes

@aperitero : did you have a chance to test?

> That would be interesting, yes @aperitero : did you have a chance to test?
Author

Hi,

@lichtwerk So I've tried a release build from Manjaro/Arch PKGBUILD (Blender 17:3.6.0-4). However I've got errors with Intel oneapi LLVM compiler, so I had to disable "WITH_CYCLES". Apart from this, I hope the build is as similar as possible to the one officially released by my distrib. I've attached the beginning of the output, that shows the libs and the flags used.

Anyway, the overlays work well in the resulting binaries.

@ChengduLittleA The bug still appears with new Mesa drivers shipped with Manjaro (23.1.3).

Another thing I tried a while ago was to compare the shaders code from a working version and a not working one (as I mentioned before, I've got cases where I had to clear Mesa shaders' cache to clear/expose the bug). The only difference I've got was not relevant to explain the bug, but maybe it could explain its origin?: in OCIO_to_display, texture2D is used on my self-compiled version while texture is used in the official release (see attached file). The compiled shaders seem to differ a lot though, but I don't know how to compare this compiled code properly.

So I'm still very lost. If you have further ideas of how I could debug this, please let me know.

Hi, @lichtwerk So I've tried a release build from Manjaro/Arch PKGBUILD (Blender 17:3.6.0-4). However I've got errors with Intel oneapi LLVM compiler, so I had to disable "WITH_CYCLES". Apart from this, I hope the build is as similar as possible to the one officially released by my distrib. I've attached the beginning of the output, that shows the libs and the flags used. Anyway, **the overlays work well in the resulting binaries**. @ChengduLittleA The bug still appears with new Mesa drivers shipped with Manjaro (23.1.3). Another thing I tried a while ago was to compare the shaders code from a working version and a not working one (as I mentioned before, I've got cases where I had to clear Mesa shaders' cache to clear/expose the bug). The only difference I've got was not relevant to explain the bug, but maybe it could explain its origin?: in _OCIO_to_display_, _texture2D_ is used on my self-compiled version while _texture_ is used in the official release (see attached file). The compiled shaders seem to differ a lot though, but I don't know how to compare this compiled code properly. So I'm still very lost. If you have further ideas of how I could debug this, please let me know.
Member

HD4400/4600 seems to be exceptionally broken recently, see #111162 are all from this particular hardware.

Might need to report this to Mesa upstream because it seems that only this hardware is broken by their new driver.

HD4400/4600 seems to be exceptionally broken recently, see #111162 are all from this particular hardware. Might need to report this to Mesa upstream because it seems that only this hardware is broken by their new driver.

Hi Guys! There are some complementary information here that can be useful:

#110640

Hi Guys! There are some complementary information here that can be useful: https://projects.blender.org/blender/blender/issues/110640
Member

Hi @aperitero @Francisco-Ortiz-de-Carvalho could you try the build here #111162 (comment) to see if this problem have been resolved?

Hi @aperitero @Francisco-Ortiz-de-Carvalho could you try the build here https://projects.blender.org/blender/blender/issues/111162#issuecomment-1009633 to see if this problem have been resolved?
Author

@ChengduLittleA Yes it works! Thanks!

A note for @Francisco-Ortiz-de-Carvalho if you want to try the build too : on my machine there is another visual problems that had appeared in the meantime in 4.0 alpha (the objects are not displayed anymore in object mode with solid shading) but it's not related to this issue. I will open a ticket for this other problem if one doesn't already exist.

@ChengduLittleA Yes it works! Thanks! A note for @Francisco-Ortiz-de-Carvalho if you want to try the build too : on my machine there is another visual problems that had appeared in the meantime in 4.0 alpha (the objects are not displayed anymore in object mode with solid shading) but it's not related to this issue. I will open a ticket for this other problem if one doesn't already exist.

Hi Guys! For me I think it's time to buy a new machine for the upcoming Blender 4.0 xD
I was not able to run this Blender patch ( https://builder.blender.org/download/patch/PR111708/ ) version in my sys (Ubuntu 22.04 inside a eleven years old machine).

Terminal entries:

Wayland:

chicortiz@chicortiz:~/Downloads/blender-4.0.0-alpha+main-PR111708.fa9bf4a65c4d-linux.x86_64-release$ ./blender
EGL Error (0x3009): EGL_BAD_MATCH: Arguments are inconsistent (for example, a valid context requires buffers not supplied by a valid surface).
EGL Error (0x3009): EGL_BAD_MATCH: Arguments are inconsistent (for example, a valid context requires buffers not supplied by a valid surface).
EGL Error (0x3009): EGL_BAD_MATCH: Arguments are inconsistent (for example, a valid context requires buffers not supplied by a valid surface).
EGL Error (0x3009): EGL_BAD_MATCH: Arguments are inconsistent (for example, a valid context requires buffers not supplied by a valid surface).
Warning: No OpenGL vendor detected.
blender: ../external_epoxy/src/dispatch_common.c:872: epoxy_get_proc_address: Assertion `0 && "Couldn't find current GLX or EGL context.\n"' failed.
Aborted (core dumped)
chicortiz@chicortiz:~/Downloads/blender-4.0.0-alpha+main-PR111708.fa9bf4a65c4d-linux.x86_64-release$

Xorg:

chicortiz@chicortiz:~/Downloads/blender-4.0.0-alpha+main-PR111708.fa9bf4a65c4d-linux.x86_64-release$ ./blender
GHOST: Wayland: unable to connect to display!
Writing: /tmp/blender.crash.txt
Segmentation fault (core dumped)

Hi Guys! For me I think it's time to buy a new machine for the upcoming Blender 4.0 xD I was not able to run this Blender patch ( https://builder.blender.org/download/patch/PR111708/ ) version in my sys (Ubuntu 22.04 inside a eleven years old machine). Terminal entries: Wayland: chicortiz@chicortiz:~/Downloads/blender-4.0.0-alpha+main-PR111708.fa9bf4a65c4d-linux.x86_64-release$ ./blender EGL Error (0x3009): EGL_BAD_MATCH: Arguments are inconsistent (for example, a valid context requires buffers not supplied by a valid surface). EGL Error (0x3009): EGL_BAD_MATCH: Arguments are inconsistent (for example, a valid context requires buffers not supplied by a valid surface). EGL Error (0x3009): EGL_BAD_MATCH: Arguments are inconsistent (for example, a valid context requires buffers not supplied by a valid surface). EGL Error (0x3009): EGL_BAD_MATCH: Arguments are inconsistent (for example, a valid context requires buffers not supplied by a valid surface). Warning: No OpenGL vendor detected. blender: ../external_epoxy/src/dispatch_common.c:872: epoxy_get_proc_address: Assertion `0 && "Couldn't find current GLX or EGL context.\n"' failed. Aborted (core dumped) chicortiz@chicortiz:~/Downloads/blender-4.0.0-alpha+main-PR111708.fa9bf4a65c4d-linux.x86_64-release$ Xorg: chicortiz@chicortiz:~/Downloads/blender-4.0.0-alpha+main-PR111708.fa9bf4a65c4d-linux.x86_64-release$ ./blender GHOST: Wayland: unable to connect to display! Writing: /tmp/blender.crash.txt Segmentation fault (core dumped)
Member

@aperitero great!

@Francisco-Ortiz-de-Carvalho This looks to be a driver/wayland issue. Can you run blender under X11? Also does official blender run there?

@aperitero great! @Francisco-Ortiz-de-Carvalho This looks to be a driver/wayland issue. Can you run blender under X11? Also does official blender run there?

@Francisco-Ortiz-de-Carvalho This looks to be a driver/wayland issue. Can you run blender under X11? Also does official blender run there?

Hi YimingWu. As you can see from my last message there is also the Xorg/X11 terminal output. Here it goes again (And yes it refers to Wayland, don't ask me why...) :

###########

chicortiz@chicortiz:~/Downloads/blender-4.0.0-alpha+main-PR111708.fa9bf4a65c4d-linux.x86_64-release$ ./blender
GHOST: Wayland: unable to connect to display!
Writing: /tmp/blender.crash.txt
Segmentation fault (core dumped)

###########

I can´t locate blender.crash.txt since blender-4.0.0-alpha+main-PR111708.fa9bf4a65c4d-linux.x86_64-release does not create a folder inside .config/blender.

Could you tell me what do you mean by "official blender"? Is it Blender 3.6.2 at Blender.org? ( https://www.blender.org/download/release/Blender3.6/blender-3.6.2-linux-x64.tar.xz/ ) ?

> @Francisco-Ortiz-de-Carvalho This looks to be a driver/wayland issue. Can you run blender under X11? Also does official blender run there? Hi YimingWu. As you can see from my last message there is also the Xorg/X11 terminal output. Here it goes again (And yes it refers to Wayland, don't ask me why...) : ########### chicortiz@chicortiz:~/Downloads/blender-4.0.0-alpha+main-PR111708.fa9bf4a65c4d-linux.x86_64-release$ ./blender GHOST: Wayland: unable to connect to display! Writing: /tmp/blender.crash.txt Segmentation fault (core dumped) ########### I can´t locate blender.crash.txt since blender-4.0.0-alpha+main-PR111708.fa9bf4a65c4d-linux.x86_64-release does not create a folder inside .config/blender. Could you tell me what do you mean by "official blender"? Is it Blender 3.6.2 at Blender.org? ( https://www.blender.org/download/release/Blender3.6/blender-3.6.2-linux-x64.tar.xz/ ) ?
Member

There was a fix regarding this, see 09df1f4caf, so please try 3.6.3 or upwards (and report back if it still an issue

There was a fix regarding this, see 09df1f4cafb996802af4c89ab8af0630f750d599, so please try 3.6.3 or upwards (and report back if it still an issue

There was a fix regarding this, see 09df1f4caf, so please try 3.6.3 or upwards (and report back if it still an issue

Hi Philipp for me, in Ubuntu Linux is still an issue with the official 3.6.4

Maybe you should talk to UPBGE devs to see how they are handling this for Blender 3.6 series because there the overlays appears in the linux version...

And I also can see the overlays in Blender 0.36 series via Wine. Really weird...

> There was a fix regarding this, see 09df1f4cafb996802af4c89ab8af0630f750d599, so please try 3.6.3 or upwards (and report back if it still an issue Hi Philipp for me, in Ubuntu Linux is still an issue with the official 3.6.4 Maybe you should talk to UPBGE devs to see how they are handling this for Blender 3.6 series because there the overlays appears in the linux version... And I also can see the overlays in Blender 0.36 series via Wine. Really weird...
Philipp Oeser added
Status
Needs Triage
and removed
Status
Needs Information from User
labels 2023-10-24 09:47:40 +02:00
Member

#109780 (comment) : Yes it works! Thanks!

Looks like 09df1f4caf fixed the issue , closing.
Feel free to comment/reopen if it still persists

> https://projects.blender.org/blender/blender/issues/109780#issuecomment-1010181 : Yes it works! Thanks! Looks like 09df1f4cafb996802af4c89ab8af0630f750d599 fixed the issue , closing. Feel free to comment/reopen if it still persists
Blender Bot added
Status
Archived
and removed
Status
Needs Triage
labels 2023-12-13 12:19:45 +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
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
5 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#109780
No description provided.