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

New Issue

and removed

2023-07-07 07:32:31 +02:00

labels 2023-07-07 06:02:05 +02:00

aperitero commented

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 ?

Pratik Borhade commented

2023-07-07 07:45:45 +02:00

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)

aperitero commented

2023-07-08 08:45:09 +02:00

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

Pratik Borhade commented

2023-07-10 04:14:50 +02:00

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

Pratik Borhade added

and removed

2023-07-10 07:34:30 +02:00

labels 2023-07-10 04:15:01 +02:00

YimingWu commented

@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

YimingWu referenced this issue

2023-07-11 11:25:50 +02:00

Regression: Loop overlay are not displayed when using Loop Cut #109955

Pratik Borhade referenced this issue

2023-07-11 11:30:24 +02:00

Regression: Loop overlay are not displayed when using Loop Cut #109955

aperitero commented

2023-07-12 19:56:41 +02:00

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

Jesse Yurkovich referenced this issue

2023-07-12 23:13:56 +02:00

seams are not visible when I do uv mapping #110024

Philipp Oeser commented

2023-07-20 11:30:27 +02:00

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

and removed

2023-07-20 14:00:17 +02:00

labels 2023-07-20 11:30:58 +02:00

aperitero commented

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.

Philipp Oeser commented

2023-07-20 14:05:40 +02:00

That would be interesting, yes

Jesse Yurkovich referenced this issue

2023-07-31 01:51:19 +02:00

Mark seam and mark sharp does not display edge colors red and cyan in Blender 3.6.1 Linux 64bit #110640

Philipp Oeser commented

2023-08-15 12:18:59 +02:00

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?

aperitero commented

2023-08-20 12:33:07 +02:00

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.

diff-glsl.txt

1.4 KiB

build-sans-Cycles.txt

19 KiB

YimingWu referenced this issue

2023-08-20 15:32:03 +02:00

Overlay drawing issues on Intel HD4400/4600 (Only?) #111162

YimingWu commented

2023-08-20 15:34:07 +02:00

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.

Francisco-Ortiz-de-Carvalho commented

2023-08-25 15:35:42 +02:00

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

YimingWu commented

2023-08-31 11:01:58 +02:00

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?

aperitero commented

2023-08-31 15:18:08 +02:00

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

Francisco-Ortiz-de-Carvalho commented

2023-08-31 19:00:19 +02:00

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)

YimingWu commented

2023-09-01 04:46:40 +02:00

@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?

YimingWu referenced this issue

2023-09-01 04:48:11 +02:00

Overlay drawing issues on Intel HD4400/4600 (Only?) #111162

Francisco-Ortiz-de-Carvalho commented

2023-09-01 14:35:37 +02:00

@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/ ) ?

Philipp Oeser commented

2023-10-11 11:23:42 +02:00

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

Francisco-Ortiz-de-Carvalho commented

2023-10-11 16:29:59 +02:00

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

and removed