Graphic glitches while editing curves - Apple M2 #110372

New Issue

System Information
Operating system: macOS-13.4.1-arm64-arm-64bit 64 Bits
Graphics card: Metal API Apple M2 1.2

Blender Version
Broken: version: 3.6.1, branch: blender-v3.6-release, commit date: 2023-07-17 12:50, hash: 8bda729ef4dc
Worked: (3.6)

Short description of error
[When editing a curve there are graphic glitches when one vertex is selected. The viewport flashes random colours, often a quarter of the screen at a time. The glitches happens in all viewport modes.]

Exact steps for others to reproduce the error
[Open a new scene, add any curve object, enter edit mode, select 1 vertex and pan or zoom around, doesn't happen when all vertices are selected]
[Based on the default startup or an attached .blend file (as simple as possible)]

**System Information** Operating system: macOS-13.4.1-arm64-arm-64bit 64 Bits Graphics card: Metal API Apple M2 1.2 **Blender Version** Broken: version: 3.6.1, branch: blender-v3.6-release, commit date: 2023-07-17 12:50, hash: `8bda729ef4dc` Worked: (3.6) **Short description of error** [When editing a curve there are graphic glitches when one vertex is selected. The viewport flashes random colours, often a quarter of the screen at a time. The glitches happens in all viewport modes.] **Exact steps for others to reproduce the error** [Open a new scene, add any curve object, enter edit mode, select 1 vertex and pan or zoom around, doesn't happen when all vertices are selected] [Based on the default startup or an attached .blend file (as simple as possible)]

Screenshot 2023-07-22 at 12.36.41.png

545 KiB

Curve_Edit_Glitch.blend

884 KiB

I have no problem on a slightly more recent version with such characteristics of the system

System Information
Operating system: Windows-10-10.0.19045-SP0 64 Bits
Graphics card: NVIDIA GeForce RTX 2070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 531.79

Blender Version
Broken: version: 3.6.1, branch: blender-v3.6-release, commit date: 2023-07-21 12:59, hash: c284cfcd08
Worked: (newest version of Blender that worked as expected)

I have no problem on a slightly more recent version with such characteristics of the system System Information Operating system: Windows-10-10.0.19045-SP0 64 Bits Graphics card: NVIDIA GeForce RTX 2070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 531.79 Blender Version Broken: version: 3.6.1, branch: blender-v3.6-release, commit date: 2023-07-21 12:59, hash: c284cfcd0830 Worked: (newest version of Blender that worked as expected)

I have the same issues and can confirm this for the Apple M2 Pro:

System Information:
Operating system: macOS-13.4.1-arm64-arm-64bit 64 Bits
Graphics card: Metal API Apple M2 Pro 1.2

Blender:

Version: 3.6.1, branch: blender-v3.6-release, commit date: 2023-07-17 12:50, hash: 8bda729ef4, type: release
build date: 2023-07-17, 23:43:50

I have the same issues and can confirm this for the Apple M2 Pro: System Information: Operating system: macOS-13.4.1-arm64-arm-64bit 64 Bits Graphics card: Metal API Apple M2 Pro 1.2 Blender: Version: 3.6.1, branch: blender-v3.6-release, commit date: 2023-07-17 12:50, hash: 8bda729ef4dc, type: release build date: 2023-07-17, 23:43:50

This problem also occurs on my Apple M1 iMac.

system-info.txt

7.3 KiB

Looks like there's enough consensus to confirm what looks like a Mac specific issue.

Looks like there's enough consensus to confirm what looks like a Mac specific issue.

FYI Looks like a Apple Silicon issues as error DOES NOT happen on macOS Monterey 12.5 - Intel i7 9700k - Radeon RX580 8GB

Sorry I accidentally closed the issue, first time in the forum apologies

> Looks like there's enough consensus to confirm what looks like a Mac specific issue. FYI Looks like a Apple Silicon issues as error DOES NOT happen on macOS Monterey 12.5 - Intel i7 9700k - Radeon RX580 8GB Sorry I accidentally closed the issue, first time in the forum apologies

@deadpin Is this related to an outdated hardware version?

I tried the x64 version of Blender 3.6.1 on my Apple M1 iMac, running under Rosetta. It works fine, without any graphics glitches. Only the native arm64 version exhibits the glitches on my system.

Could it be due to some add-on which has incompatible shader code for Metal backend: #109034
Does this happen after factory reset: File > Defaults > Load Factory Settings
Also, which viewport backend is showing this results?: OpenGL/Metal

Could it be due to some add-on which has incompatible shader code for Metal backend: #109034 Does this happen after factory reset: `File > Defaults > Load Factory Settings` Also, which viewport backend is showing this results?: `OpenGL/Metal`

Could it be due to some add-on which has incompatible shader code for Metal backend: #109034
Does this happen after factory reset: File > Defaults > Load Factory Settings
Also, which viewport backend is showing this results?: OpenGL/Metal

The error occurs after a factory reset with viewport backend set to metal.
If I change to Open GL the error goes away.

> Could it be due to some add-on which has incompatible shader code for Metal backend: #109034 > Does this happen after factory reset: `File > Defaults > Load Factory Settings` > Also, which viewport backend is showing this results?: `OpenGL/Metal` The error occurs after a factory reset with viewport backend set to metal. If I change to Open GL the error goes away.

cc @Michael-Parkin-White-Apple

Thanks for the report, I'm attempting to reproduce this but so far unable to. I can imagine this is a Metal-specific issue relating to the geometry shader alternative path, but exactly why this occurs may be hard to determine.

There was a previous report which was similar, though that appeared to be caused by an add-on. In this case, if its happening as said with factory reset, then I'll see if I can reproduce and root-cause this.

Thanks for the report, I'm attempting to reproduce this but so far unable to. I can imagine this is a Metal-specific issue relating to the geometry shader alternative path, but exactly why this occurs may be hard to determine. There was a previous report which was similar, though that appeared to be caused by an add-on. In this case, if its happening as said with factory reset, then I'll see if I can reproduce and root-cause this.

I have the same problem with Apple M1 Max / macOS 13.4.1.
Just installed 3.6.1 today, didn't have this issue with 3.6.0

I have the same problem with Apple M1 Max / macOS 13.4.1. Just installed 3.6.1 today, didn't have this issue with 3.6.0

I face with the same issue on my m1max Ventura and Sonoma no matter I change to OpenGL and metal, it all appears, unless I use intel version with rosetta...

I find that if I use stable version of 3.6 blender apple silicon the glitch is far more less than the glicher on 3.6LTS and for 4.0 beta the glicher is also less than 3.6LTS version

Have now identified the culprit, patch coming in soon.

There were two separate issues occurring here:

With some other recent changes to curve handles, an early exit was added when the handles should not display, however, this early exit was not discarding geometry in the Metal implentation, but leaving values undefined. Resulting in random geometry flickering on screen. This may not previously have happened in certain modes if the vertex buffers were zero-initialised up-front (which only happens with certain debug flags).
Curve handle geometry generation would render incorrectly when outputting triangleStrips IF the transparent border was disabled.

Have now identified the culprit, patch coming in soon. There were two separate issues occurring here: 1) With some other recent changes to curve handles, an early exit was added when the handles should not display, however, this early exit was not discarding geometry in the Metal implentation, but leaving values undefined. Resulting in random geometry flickering on screen. This may not previously have happened in certain modes if the vertex buffers were zero-initialised up-front (which only happens with certain debug flags). 2) Curve handle geometry generation would render incorrectly when outputting triangleStrips IF the transparent border was disabled.

cool, so we can later reinstall the new beta 3.6.1LTS version to fix the issue or we need to download the patch and patch it by ourselves

@elise123 hi, Clément has added the commit in backporting list. So it'll be available to you in next LTS release, i.e. 3.6.2
You can even try this today in 4.0 build: https://builder.blender.org/download/daily/

@elise123 hi, Clément has added the commit in backporting list. So it'll be available to you in next LTS release, i.e. 3.6.2 You can even try this today in 4.0 build: https://builder.blender.org/download/daily/

cool I find it now work for my Mac of the new 4.0 alpha apple silicon

Yeah it is fine now with blender 4.0 alpha Apple silicon

All working now with 3.6.2, excellent! Thanks developers and all who support :-)

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Graphic glitches while editing curves - Apple M2 #110372