blender
/
blender
132
398
Fork 577
Code Issues 6.2k Pull Requests 746 Projects 19 Wiki Activity

Metal Backend causes UV editing to glitch out, crash Blender #112190

New Issue
Open
opened 2023-09-09 23:52:33 +02:00 by Tom Oliver · 17 comments
Tom Oliver commented 2023-09-09 23:52:33 +02:00
Copy Link

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

Blender Version
Broken: version: 3.5.1, 3.6.3, 4.0 alpha
Worked: (newest version of Blender that worked as expected)

Short description of error
Trying to do UV editing with the Metal backend causes unexpected UI behavior. Islands will glitch out, disappear, randomly stretch and contort, or Blender will crash entirely. It makes Metal useless for work and requires a switch to OpenGL to have expected performance. This happens on my M1 Air, M1 Pro MacBook Pro, and M1 Max Mac Studio. They all had to be switched back to OpenGL.


Exact steps for others to reproduce the error

  • Open the included Blender file with Metal backend
  • Make sure the 3D viewport has either Material Preview or Rendered View enabled.
  • Start UV editing on the Azumi object (go to Object Mode > Select the Azumi object > go to UV Editing Workspace)
  • Zoom, pan, scale, rotate...

It'll happen eventually.

EDIT: This issue seems to stem from having multiple UV Maps on the model somehow. If the additional UV Maps are removed, the issue stops occurring.

EDIT 2: Further digging seems to show that it specifically has to do with the texture atlas expression swapping using the UV Map and Mapping Nodes in the "Colors.001" material. Clearing the field in the UV Map node also immediately resolves the issue.

I've attached two screen recordings of some of the behavior, as well as the error log when Blender crashed, and the file I'm working with.

EDIT 3: Uploaded a simple test file with just a cube using the same material setup as my character file. It exhibits the exact same behavior.

**System Information** Operating system: macOS-13.5.2-arm64-arm-64bit 64 Bits Graphics card: Metal API Apple M1 1.2 **Blender Version** Broken: version: 3.5.1, 3.6.3, 4.0 alpha Worked: (newest version of Blender that worked as expected) **Short description of error** Trying to do UV editing with the Metal backend causes unexpected UI behavior. Islands will glitch out, disappear, randomly stretch and contort, or Blender will crash entirely. It makes Metal useless for work and requires a switch to OpenGL to have expected performance. This happens on my M1 Air, M1 Pro MacBook Pro, and M1 Max Mac Studio. They all had to be switched back to OpenGL. <video src="/attachments/7afa9664-0eda-4c05-ac82-29ef324de2fd" title="error.mov" controls></video> <video src="/attachments/f930dab3-0ad4-4215-adca-c4235f40df94" title="Screen Recording 2023-09-09 at 5.50.49 PM.mov" controls></video> **Exact steps for others to reproduce the error** - Open the included Blender file with Metal backend - Make sure the 3D viewport has either Material Preview or Rendered View enabled. - Start UV editing on the `Azumi` object (go to Object Mode > Select the Azumi object > go to UV Editing Workspace) - Zoom, pan, scale, rotate... It'll happen eventually. EDIT: This issue seems to stem from having multiple UV Maps on the model somehow. If the additional UV Maps are removed, the issue stops occurring. EDIT 2: Further digging seems to show that it specifically has to do with the texture atlas expression swapping using the UV Map and Mapping Nodes in the "Colors.001" material. Clearing the field in the UV Map node also immediately resolves the issue. I've attached two screen recordings of some of the behavior, as well as the error log when Blender crashed, and the file I'm working with. EDIT 3: Uploaded a simple test file with just a cube using the same material setup as my character file. It exhibits the exact same behavior.
Azumi_ARP.blend
67 MiB
crash log.rtf
106 KiB
test_file.blend
1.0 MiB
error.mov
19 MiB
Screen Recording 2023-09-09 at 5.50.49 PM.mov
24 MiB
Tom Oliver added the
Priority
Normal
Type
Report
Status
Needs Triage
 labels 2023-09-09 23:52:34 +02:00
Pratik Borhade commented 2023-09-11 08:15:36 +02:00
Member
Copy Link

Hi, thanks for the report. Any improvements in fresh 3.6.3/4.0 build?: https://builder.blender.org/download/daily/
3.5 is now archived

Hi, thanks for the report. Any improvements in fresh 3.6.3/4.0 build?: https://builder.blender.org/download/daily/ 3.5 is now archived
Pratik Borhade added
Status
Needs Information from User
 and removed
Status
Needs Triage
 labels 2023-09-11 08:15:43 +02:00
Tom Oliver commented 2023-09-11 08:16:51 +02:00
Author
Copy Link

Hey. It still happens in 3.6. Haven't tried 4.0 yet. But I'll give it a shot and get back to you

Hey. It still happens in 3.6. Haven't tried 4.0 yet. But I'll give it a shot and get back to you
Tom Oliver commented 2023-09-11 08:26:17 +02:00
Author
Copy Link

Yep. Still happens in 4.0. Same glitch and then Blender crashed. Error log is attached.

Couldn't test if OpenGL was still okay since it looks like OpenGL was removed in 4.0, or was at least moved.

Yep. Still happens in 4.0. Same glitch and then Blender crashed. Error log is attached. Couldn't test if OpenGL was still okay since it looks like OpenGL was removed in 4.0, or was at least moved.
error log.rtf
87 KiB
Pratik Borhade commented 2023-09-11 08:35:45 +02:00
Member
Copy Link

Thanks. @mano-wii , can you verify on Mac M1?
OpenGL support is removed in 4.0 for Mac because some newer feature requires 4.3 GL version :)

Thanks. @mano-wii , can you verify on Mac M1? OpenGL support is removed in 4.0 for Mac because some newer feature requires 4.3 GL version :)
Pratik Borhade added
Status
Needs Triage
 and removed
Status
Needs Information from User
 labels 2023-09-11 08:37:10 +02:00
Germano Cavalcante commented 2023-09-11 16:12:16 +02:00
Member
Copy Link

Based on the video, I edited the description to include clearer steps.
But I still can't replicate the problem. Whether in Blender 3.5 or Blender 4.0

@tommyoliversays, could you please clarify a few things:

  • Does the problem also happen when textures are not available? (the attached file does not have the textures).
  • Are there any specific actions to perform for the issue to happen?
System Information
  • Operating system: macOS-13.5.1-x86_64-i386-64bit 64 Bits
  • Graphics card: Metal API Apple M1 1.2
Based on the video, I edited the description to include clearer steps. But I still can't replicate the problem. Whether in Blender 3.5 or Blender 4.0 @tommyoliversays, could you please clarify a few things: - Does the problem also happen when textures are not available? (the attached file does not have the textures). - Are there any specific actions to perform for the issue to happen? <details> <summary>System Information</summary> <ul> <li>Operating system: macOS-13.5.1-x86_64-i386-64bit 64 Bits</li> <li>Graphics card: Metal API Apple M1 1.2</li> </ul> </details>
Germano Cavalcante added
Status
Needs Information from User
 and removed
Status
Needs Triage
 labels 2023-09-11 16:12:28 +02:00
Tom Oliver commented 2023-09-11 16:21:08 +02:00
Author
Copy Link

Based on the video, I edited the description to include clearer steps.
But I still can't replicate the problem. Whether in Blender 3.5 or Blender 4.0

@tommyoliversays, could you please clarify a few things:

  • Does the problem also happen when textures are not available? (the attached file does not have the textures).
  • Are there any specific actions to perform for the issue happen?
System Information
  • Operating system: macOS-13.5.1-x86_64-i386-64bit 64 Bits
  • Graphics card: Metal API Apple M1 1.2

My apologizes. I thought the textures were packed. I've uploaded the file again with the packed textures.

However, in doing more tests, I've been able to narrow down that the issue only occurs when the 3D viewport in in Material Preview or Rendering Preview. Wireframe and Solid don't seem to have the issue, or at least less frequently that I can't easily reproduce it. I'll edit the description to reflect this as well.

> Based on the video, I edited the description to include clearer steps. > But I still can't replicate the problem. Whether in Blender 3.5 or Blender 4.0 > > @tommyoliversays, could you please clarify a few things: > - Does the problem also happen when textures are not available? (the attached file does not have the textures). > - Are there any specific actions to perform for the issue happen? > > <details> > <summary>System Information</summary> > <ul> > <li>Operating system: macOS-13.5.1-x86_64-i386-64bit 64 Bits</li> > <li>Graphics card: Metal API Apple M1 1.2</li> > </ul> > </details> My apologizes. I thought the textures were packed. I've uploaded the file again with the packed textures. However, in doing more tests, I've been able to narrow down that the issue only occurs when the 3D viewport in in Material Preview or Rendering Preview. Wireframe and Solid don't seem to have the issue, or at least less frequently that I can't easily reproduce it. I'll edit the description to reflect this as well.
Azumi_ARP.blend
67 MiB
Tom Oliver commented 2023-09-11 16:44:04 +02:00
Author
Copy Link

Okay. More info. It has something to do with the additional UV Maps. If you remove them and just leave the base UV Map, this issue is immediately resolved.

Okay. More info. It has something to do with the additional UV Maps. If you remove them and just leave the base UV Map, this issue is immediately resolved.
Richard Antalik commented 2023-09-11 17:23:20 +02:00
Member
Copy Link

There are still bunch of textures missing. I wasn't able to reproduce crash on intel Mac, but I was able to reproduce "glitching" as in your second video.
I suspect these are 2 different bugs, so it would be best to split this report and make new one for crash perhaps.

There are still bunch of textures missing. I wasn't able to reproduce crash on intel Mac, but I was able to reproduce "glitching" as in your second video. I suspect these are 2 different bugs, so it would be best to split this report and make new one for crash perhaps.
Germano Cavalcante commented 2023-09-11 17:48:48 +02:00
Member
Copy Link

I can also confirm the glitch.
I think we can confirm for now because of the glitch.
But the crash actually needs more details.

I can also confirm the glitch. I think we can confirm for now because of the glitch. But the crash actually needs more details.
Tom Oliver commented 2023-09-11 17:59:31 +02:00
Author
Copy Link

There are still bunch of textures missing. I wasn't able to reproduce crash on intel Mac, but I was able to reproduce "glitching" as in your second video.
I suspect these are 2 different bugs, so it would be best to split this report and make new one for crash perhaps.

I just updated the file again, again making sure to pack the images (as well as try and clear out some redundant materials, been working in this file for a while). It should be good now.

Further messing around seems to show that the UV glitch error specifically has to do with the texture atlas expression swap using the UV Map and Mapping Nodes in the "Colors.001" material. Clearing the field in the UV Map node here also immediately resolves the issue.

> There are still bunch of textures missing. I wasn't able to reproduce crash on intel Mac, but I was able to reproduce "glitching" as in your second video. > I suspect these are 2 different bugs, so it would be best to split this report and make new one for crash perhaps. I just updated the file again, again making sure to pack the images (as well as try and clear out some redundant materials, been working in this file for a while). It should be good now. Further messing around seems to show that the UV glitch error specifically has to do with the texture atlas expression swap using the UV Map and Mapping Nodes in the "Colors.001" material. Clearing the field in the UV Map node here also immediately resolves the issue.
Richard Antalik commented 2023-09-12 17:48:28 +02:00
Member
Copy Link

@tommyoliversays If you understand the cause of the issue, can you perhaps simplify the file as much as possible?

@tommyoliversays If you understand the cause of the issue, can you perhaps simplify the file as much as possible?
Tom Oliver commented 2023-09-12 18:28:24 +02:00
Author
Copy Link

@tommyoliversays If you understand the cause of the issue, can you perhaps simplify the file as much as possible?

Sure. Here is a simple file with the same material setup that exhibits the same issue. I'll also add it to the main post.

Edit: also added the texture files separately. I've been packing them but the files sometimes don't work

> @tommyoliversays If you understand the cause of the issue, can you perhaps simplify the file as much as possible? Sure. Here is a simple file with the same material setup that exhibits the same issue. I'll also add it to the main post. _Edit: also added the texture files separately. I've been packing them but the files sometimes don't work_
test_file.blend
1.0 MiB
1f1d9ff0ef2b4c66e7bcf44d5e12a409.jpg
133 KiB
test_overlay.png
5.3 KiB
1f1d9ff0ef2b4c66e7bcf44d5e12a409.jpg test_overlay.png
Germano Cavalcante added the
Interest
UV Editing
 label 2023-09-18 16:31:04 +02:00
Tom Oliver commented 2023-12-07 17:59:46 +01:00
Author
Copy Link

Just figured I'd chime back in and say that the issue is still present in 4.0.2

Just figured I'd chime back in and say that the issue is still present in 4.0.2
Michael Parkin-White commented 2023-12-28 18:06:52 +01:00
Copy Link

So while this is only crashing in the Metal backend, it looks like it is caused by one of the vertex buffers having the GPU_VERTBUF_INVALID flag., and thus attempts to allocate it while containing no data.

It looks like this is an unexpected scenario. In this case, the OpenGL backend allocates an empty buffer. The error would be avoided by binding an empty buffer in Metal too however, but this feels like it would cause issues on read.

It feels like this problem lies higher up. Being unfamiliar with UV editing, my guess is that this is because the GPUBatch being drawn for UV editing has two vertex buffers bound, one for each UV layer, however, only one of these layers is displayed at a time in the editor.

So while this is only crashing in the Metal backend, it looks like it is caused by one of the vertex buffers having the `GPU_VERTBUF_INVALID` flag., and thus attempts to allocate it while containing no data. It looks like this is an unexpected scenario. In this case, the OpenGL backend allocates an empty buffer. The error would be avoided by binding an empty buffer in Metal too however, but this feels like it would cause issues on read. It feels like this problem lies higher up. Being unfamiliar with UV editing, my guess is that this is because the GPUBatch being drawn for UV editing has two vertex buffers bound, one for each UV layer, however, only one of these layers is displayed at a time in the editor.
Michael Parkin-White commented 2023-12-28 18:20:08 +01:00
Copy Link

Adding a guard around the asserting code (asserts on VertBuf::size_used_get) removes the crash, but for whatever reason in the provided test file, when the equivalent invalid binding is hit, defaulting to binding an invalid buffer results in erroneous display:

  if (flag & GPU_VERTBUF_DATA_DIRTY || flag & GPU_VERTBUF_INIT) {
    required_size_raw = sizeof(uchar) * this->size_used_get();
  }

Deleting the original UV maps and adding two new ones however appears okay, so not sure where this bad data/state is coming from in the first place.

Adding a guard around the asserting code (asserts on VertBuf::size_used_get) removes the crash, but for whatever reason in the provided test file, when the equivalent invalid binding is hit, defaulting to binding an invalid buffer results in erroneous display: ``` if (flag & GPU_VERTBUF_DATA_DIRTY || flag & GPU_VERTBUF_INIT) { required_size_raw = sizeof(uchar) * this->size_used_get(); } ``` Deleting the original UV maps and adding two new ones however appears okay, so not sure where this bad data/state is coming from in the first place.
Michael Parkin-White commented 2023-12-28 19:41:40 +01:00
Copy Link

This may be one that @Jeroen-Bakker has a better idea about.

FYI far easier to reproduce if disabling VAO caching in Metal, as this will assert very consistently when editing UVs if the GPUVertBuf is in invalid state at draw time:

Can comment out lines 714-718 in source/blender/gpu/metal/mtl_batch.mm:

if (!this->vao_cache.insert(pair)) {
      printf(
          "[Performance Warning] cache is full (Size: %d), vertex descriptor will not be cached\n",
          GPU_VAO_STATIC_LEN);
    }

Meaning vertex attribute fetching happens each time. After some time of editing UVs, you will get a situation where this fails, and the offending VBO has GPU_VERTBUF_INVALID as its state, and usually nonsense data.

Other investigations seem that at the time the mesh batch cache fetching is complete, the status is always valid. Not sure where this is getting stomped, whether an issue with some other part of the code stomping the pointer, or if it is prematurely cleared.

This may be one that @Jeroen-Bakker has a better idea about. FYI far easier to reproduce if disabling VAO caching in Metal, as this will assert very consistently when editing UVs if the GPUVertBuf is in invalid state at draw time: Can comment out lines 714-718 in `source/blender/gpu/metal/mtl_batch.mm`: ``` if (!this->vao_cache.insert(pair)) { printf( "[Performance Warning] cache is full (Size: %d), vertex descriptor will not be cached\n", GPU_VAO_STATIC_LEN); } ``` Meaning vertex attribute fetching happens each time. After some time of editing UVs, you will get a situation where this fails, and the offending VBO has GPU_VERTBUF_INVALID as its state, and usually nonsense data. Other investigations seem that at the time the mesh batch cache fetching is complete, the status is always valid. Not sure where this is getting stomped, whether an issue with some other part of the code stomping the pointer, or if it is prematurely cleared.
Jeroen Bakker was assigned by Jason Fielder 2024-01-11 12:53:58 +01:00
Michael-VAISSIERE commented 2024-03-12 08:24:13 +01:00
Copy Link

Hi all !

Regarding mention of #119340 I am not sure it is the same bug because the latter is far more simpler to reproduce and does not depend on texture or material.

Simple test to reproduce:

  • open blender with metal backend
  • select cube
  • edit mode
  • subdivide w/ count = 10 >>> the bug occurs only when the # of faces reaches 64
  • create new UV and select it
  • in UV editor select faces and move them around

If you reopen blender with OpenGL backend the bug is not there.

Hope that helps !
Cheers !

Hi all ! Regarding mention of #119340 I am not sure it is the same bug because the latter is far more simpler to reproduce and does not depend on texture or material. Simple test to reproduce: - open blender with metal backend - select cube - edit mode - subdivide w/ count = 10 >>> the bug occurs only when **the # of faces reaches 64** - create new UV and select it - in UV editor select faces and move them around If you reopen blender with OpenGL backend the bug is not there. Hope that helps ! Cheers !
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
main
universal-scene-description
brush-assets-project
fix-121021
blender-v4.1-release
blender-v3.3-release
blender-v3.6-release
blender-v3.6-temp_wmoss_animrig_public
temp-sculpt-dyntopo
gpencil-next
anim/animation-id-113594
blender-v4.0-release
blender-projects-basics
bridge-curves
sculpt-blender
asset-browser-frontend-split
asset-shelf
tmp-usd-python-mtl
tmp-usd-3.6
blender-v3.5-release
blender-v2.93-release
realtime-clock
sculpt-dev
bevelv2
xr-dev
v4.1.1
v3.6.11
v3.3.18
v4.1.0
v3.3.17
v3.6.10
v3.6.9
v3.3.16
v3.6.8
v3.6.7
v3.3.14
v4.0.2
v4.0.1
v4.0.0
v3.6.5
v3.3.12
v3.6.4
v3.6.3
v3.3.11
v3.6.2
v3.3.10
v3.6.1
v3.3.9
v3.6.0
v3.3.8
v3.3.7
v2.93.18
v3.5.1
v3.3.6
v2.93.17
v3.5.0
v2.93.16
v3.3.5
v3.3.4
v2.93.15
v2.93.14
v3.3.3
v2.93.13
v2.93.12
v3.4.1
v3.3.2
v3.4.0
v3.3.1
v2.93.11
v3.3.0
v3.2.2
v2.93.10
v3.2.1
v3.2.0
v2.83.20
v2.93.9
v3.1.2
v3.1.1
v3.1.0
v2.83.19
v2.93.8
v3.0.1
v2.93.7
v3.0.0
v2.93.6
v2.93.5
v2.83.18
v2.93.4
v2.93.3
v2.83.17
v2.93.2
v2.93.1
v2.83.16
v2.93.0
v2.83.15
v2.83.14
v2.83.13
v2.92.0
v2.83.12
v2.91.2
v2.83.10
v2.91.0
v2.83.9
v2.83.8
v2.83.7
v2.90.1
v2.83.6.1
v2.83.6
v2.90.0
v2.83.5
v2.83.4
v2.83.3
v2.83.2
v2.83.1
v2.83
v2.82a
v2.82
v2.81a
v2.81
v2.80
v2.80-rc3
v2.80-rc2
v2.80-rc1
v2.79b
v2.79a
v2.79
v2.79-rc2
v2.79-rc1
v2.78c
v2.78b
v2.78a
v2.78
v2.78-rc2
v2.78-rc1
v2.77a
v2.77
v2.77-rc2
v2.77-rc1
v2.76b
v2.76a
v2.76
v2.76-rc3
v2.76-rc2
v2.76-rc1
v2.75a
v2.75
v2.75-rc2
v2.75-rc1
v2.74
v2.74-rc4
v2.74-rc3
v2.74-rc2
v2.74-rc1
v2.73a
v2.73
v2.73-rc1
v2.72b
2.72b
v2.72a
v2.72
v2.72-rc1
v2.71
v2.71-rc2
v2.71-rc1
v2.70a
v2.70
v2.70-rc2
v2.70-rc
v2.69
v2.68a
v2.68
v2.67b
v2.67a
v2.67
v2.66a
v2.66
v2.65a
v2.65
v2.64a
v2.64
v2.63a
v2.63
v2.61
v2.60a
v2.60
v2.59
v2.58a
v2.58
v2.57b
v2.57a
v2.57
v2.56a
v2.56
v2.55
v2.54
v2.53
v2.52
v2.51
v2.50
v2.49b
v2.49a
v2.49
v2.48a
v2.48
v2.47
v2.46
v2.45
v2.44
v2.43
v2.42a
v2.42
v2.41
v2.40
v2.37a
v2.37
v2.36
v2.35a
v2.35
v2.34
v2.33a
v2.33
v2.32
v2.31a
v2.31
v2.30
v2.28c
v2.28a
v2.28
v2.27
v2.26
v2.25
Labels
Clear labels   
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
This issue affects/is about backward or forward 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
Issues relating to Wayland windowing support.

  
Interest
Workbench

  
Interest: X11

Issues relating to Xorg/X11 support.

  
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
Issues relating to security: https://wiki.blender.org/wiki/Process/Vulnerability_Reports

  
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 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
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
Jeroen Bakker
6 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#112190
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?