blender
/
blender
134
398
Fork 579
Code Issues 6.3k Pull Requests 754 Projects 19 Wiki Activity

4.0.0 Alpha - No shader storage buffer support #111587

New Issue
Closed
opened 2023-08-27 15:57:27 +02:00 by Peter Green · 23 comments
Peter Green commented 2023-08-27 15:57:27 +02:00
Copy Link

System Information
Operating system: WIN10
Graphics card: Intel HD 4600

Blender Version
Broken: blender-4.0.0-alpha+daily.6538a5872551
Worked: 4.0.0 from about a week ago (apologies for vagueness)

Short description of error
Error: No shader storage buffer support

Error message appears when in Viewport Shading, in both Eevee and Cycles.

Exact steps for others to reproduce the error
Simply open Blender.

**System Information** Operating system: WIN10 Graphics card: Intel HD 4600 **Blender Version** Broken: blender-4.0.0-alpha+daily.6538a5872551 Worked: 4.0.0 from about a week ago (apologies for vagueness) **Short description of error** Error: No shader storage buffer support Error message appears when in Viewport Shading, in both Eevee and Cycles. **Exact steps for others to reproduce the error** Simply open Blender.
blender_system_info.txt
16 KiB
blender_debug_output.txt
6.1 KiB
Peter Green added the
Type
Report
Priority
Normal
Status
Needs Triage
 labels 2023-08-27 15:57:28 +02:00
Iliya Katushenock added the
Interest
EEVEE & Viewport
 label 2023-08-27 20:17:13 +02:00
Jesse Yurkovich commented 2023-08-27 21:32:21 +02:00
Member
Copy Link

Marking as high to get clarification soon on the matter. These GPUs may now fall below the minimum requirements necessary but the release-notes/requirements pages haven't been updated so it's unclear.

CC @pragma37 @Jeroen-Bakker

Marking as high to get clarification soon on the matter. These GPUs may now fall below the minimum requirements necessary but the release-notes/requirements pages haven't been updated so it's unclear. CC @pragma37 @Jeroen-Bakker
Jeroen Bakker commented 2023-08-28 08:02:17 +02:00
Member
Copy Link

This topic is still under discussion. The GPU a lower number of ssbos per shader, than eevee-next requires. We are looking how to ensure workbench to be still used. Especially as 4.0 is still shipped with eevee. The trick is that this limitation is also part of workbench at the moment as some internal buffers are attached at higher binding numbers, but we might want to reduce the number of ssbos there.

This topic is still under discussion. The GPU a lower number of ssbos per shader, than eevee-next requires. We are looking how to ensure workbench to be still used. Especially as 4.0 is still shipped with eevee. The trick is that this limitation is also part of workbench at the moment as some internal buffers are attached at higher binding numbers, but we might want to reduce the number of ssbos there.
👍 1
Vladimir commented 2023-08-28 11:58:44 +02:00
Copy Link

Do you have the same problem with the Workbench or not? I openned an issue but its closed as duplicate

Screenshot_20230827_221228.png

Do you have the same problem with the Workbench or not? I openned [an issue](issues/111594) but its closed as duplicate ![Screenshot_20230827_221228.png](/attachments/9337d4c3-8ab8-475d-9c31-c0ab29d4d508)
Jeroen Bakker commented 2023-08-28 12:09:49 +02:00
Member
Copy Link

Yes both issues seems like the same, so it was merged into this one.

Yes both issues seems like the same, so it was merged into this one.
Peter Green commented 2023-08-28 13:01:52 +02:00
Author
Copy Link

I don't know if this helps, but...

I'm using Blender Launcher. If I do a Debug->Factory Startup, and then quit Blender it leaves me a recovery file in C:\Users\Peter\AppData\Local\Temp\quit.blend

If I then open this quit.blend file, I DON'T get the shader error message, and the shading looks OK.

I don't know if this helps, but... I'm using Blender Launcher. If I do a Debug->Factory Startup, and then quit Blender it leaves me a recovery file in C:\Users\Peter\AppData\Local\Temp\quit.blend If I then open this quit.blend file, I DON'T get the shader error message, and the shading looks OK.
Miguel Pozo commented 2023-08-28 18:05:55 +02:00
Member
Copy Link

While there may be indeed a problem with the max supported number of SSBOs binding points per shader.
(BTW, we should print that in the system info)
This issue happens earlier, since the Next engines check for SSBO support before initialization, and the Intel HD 4400 and 4600 are manually flagged as not supporting them:
60560c7da5/source/blender/gpu/opengl/gl_backend.cc (L446)

I think the reason they were flagged as such is not really an issue for Next engines.

Could you (@snibber and @Wovchick) check if these builds work for you?
https://builder.blender.org/download/patch/PR111616/

While there may be indeed a problem with the max supported number of SSBOs binding points per shader. (BTW, we should print that in the system info) This issue happens earlier, since the Next engines check for SSBO support before initialization, and the Intel HD 4400 and 4600 are manually flagged as not supporting them: https://projects.blender.org/blender/blender/src/commit/60560c7da55d4c9d141d3b4a963c63dd882cfe56/source/blender/gpu/opengl/gl_backend.cc#L446 I think the reason they were flagged as such is not really an issue for Next engines. Could you (@snibber and @Wovchick) check if these builds work for you? https://builder.blender.org/download/patch/PR111616/
👍 1
Peter Green commented 2023-08-28 18:37:28 +02:00
Author
Copy Link

I downloaded and installed PR111616. It launches, then immediately dies. I attach blender_debug_output.txt

My ancient "GPU" has been living on borrowed time for too long with respect to Blender. It looks like I've now truly reached the end of the road. But thanks to the whole community for many years of fun.

I downloaded and installed PR111616. It launches, then immediately dies. I attach blender_debug_output.txt My ancient "GPU" has been living on borrowed time for too long with respect to Blender. It looks like I've now truly reached the end of the road. But thanks to the whole community for many years of fun.
blender_debug_output.txt
3.3 KiB
Blender Bot added
Status
Archived
 and removed
Status
Confirmed
 labels 2023-08-28 18:37:33 +02:00
Blender Bot added
Status
Needs Triage
 and removed
Status
Archived
 labels 2023-08-28 18:38:07 +02:00
Peter Green commented 2023-08-28 18:38:47 +02:00
Author
Copy Link

Finger trouble. I didn't mean to close the issue. That's a decision for others.

Finger trouble. I didn't mean to close the issue. That's a decision for others.
Iliya Katushenock added
Status
Confirmed
 and removed
Status
Needs Triage
 labels 2023-08-28 18:47:55 +02:00
Miguel Pozo commented 2023-08-28 19:25:19 +02:00
Member
Copy Link

The debug output doesn't show any related info. If it's crashing, could you attach the crash report?
https://docs.blender.org/manual/en/latest/troubleshooting/crash.html

The debug output doesn't show any related info. If it's crashing, could you attach the crash report? https://docs.blender.org/manual/en/latest/troubleshooting/crash.html
Vladimir commented 2023-08-28 20:14:04 +02:00
Copy Link

The debug output doesn't show any related info. If it's crashing, could you attach the crash report?

Hi! Blender crashes on start. I launched Blender with --debug-all option

console:

....
[SCScene :: View Layer]: BKE_object_eval_light_linking on OBCamera (0x7fc333355e38)
Depsgraph updated in 0.001425 seconds.
Depsgraph evaluation FPS: -nan
loading preset: /mnt/work/BlenderWorkedBuilds/blender-4.0.0-alpha+main-PR111616.1e5cdea54f8d-linux.x86_64-release/4.0/scripts/presets/keyconfig/Blender.py
FRS_set_context: context 0x0x7fc36a260d18 scene 0x0x7fc36468ec38
UI_menutype_draw: opening menu "WM_MT_splash"
ghost_event_proc: ghost redraw 1
ghost_event_proc: ghost redraw 1
ED_screen_refresh: set screen
UI_menutype_draw: opening menu "TOPBAR_MT_editor_menus"
UI_menutype_draw: opening menu "TIME_MT_editor_menus"
UI_menutype_draw: opening menu "VIEW3D_MT_editor_menus"
Writing: /mnt/work/cache/blender/tmp/blender.crash.txt
Segmentation fault (core dumped)

blender.crash.txt:

# Blender 4.0.0, Commit date: 2023-08-28 13:49, Hash 1e5cdea54f8d
bpy.ops.wm.splash()  # Operator
bpy.ops.wm.tool_set_by_id(name="builtin.select_box", cycle=False, space_type='VIEW_3D')  # Operator

# backtrace
./blender() [0xf1a550]
./blender() [0x8b7575]
/usr/lib/libc.so.6(+0x3e710) [0x7fc36c63e710]
./blender() [0x11473e1]
./blender() [0x11a3845]
./blender() [0x119d783]
./blender() [0x10f1f08]
./blender() [0x10f38bd]
./blender() [0x1dd7223]
./blender() [0x151aad6]
./blender() [0xf2bf12]
./blender() [0xf284c0]
./blender() [0x7183e0]
/usr/lib/libc.so.6(+0x27cd0) [0x7fc36c627cd0]
/usr/lib/libc.so.6(__libc_start_main+0x8a) [0x7fc36c627d8a]
./blender() [0x8b347e]

# Python backtrace
> The debug output doesn't show any related info. If it's crashing, could you attach the crash report? Hi! Blender crashes on start. I launched Blender with `--debug-all` option `console`: ``` .... [SCScene :: View Layer]: BKE_object_eval_light_linking on OBCamera (0x7fc333355e38) Depsgraph updated in 0.001425 seconds. Depsgraph evaluation FPS: -nan loading preset: /mnt/work/BlenderWorkedBuilds/blender-4.0.0-alpha+main-PR111616.1e5cdea54f8d-linux.x86_64-release/4.0/scripts/presets/keyconfig/Blender.py FRS_set_context: context 0x0x7fc36a260d18 scene 0x0x7fc36468ec38 UI_menutype_draw: opening menu "WM_MT_splash" ghost_event_proc: ghost redraw 1 ghost_event_proc: ghost redraw 1 ED_screen_refresh: set screen UI_menutype_draw: opening menu "TOPBAR_MT_editor_menus" UI_menutype_draw: opening menu "TIME_MT_editor_menus" UI_menutype_draw: opening menu "VIEW3D_MT_editor_menus" Writing: /mnt/work/cache/blender/tmp/blender.crash.txt Segmentation fault (core dumped) ``` `blender.crash.txt`: ``` # Blender 4.0.0, Commit date: 2023-08-28 13:49, Hash 1e5cdea54f8d bpy.ops.wm.splash() # Operator bpy.ops.wm.tool_set_by_id(name="builtin.select_box", cycle=False, space_type='VIEW_3D') # Operator # backtrace ./blender() [0xf1a550] ./blender() [0x8b7575] /usr/lib/libc.so.6(+0x3e710) [0x7fc36c63e710] ./blender() [0x11473e1] ./blender() [0x11a3845] ./blender() [0x119d783] ./blender() [0x10f1f08] ./blender() [0x10f38bd] ./blender() [0x1dd7223] ./blender() [0x151aad6] ./blender() [0xf2bf12] ./blender() [0xf284c0] ./blender() [0x7183e0] /usr/lib/libc.so.6(+0x27cd0) [0x7fc36c627cd0] /usr/lib/libc.so.6(__libc_start_main+0x8a) [0x7fc36c627d8a] ./blender() [0x8b347e] # Python backtrace ```
Abdelaziz-Sharaf commented 2023-08-29 07:44:06 +02:00
Copy Link

Maybe this is what cased my issue #111619, but if so.. why not in any other view other than solid view ?
I've read your comments about the no. of SSBOs binding points per shader however I dont understand it.. if that the case it shouldn't work in other views or modes.. also rendering is done perfectly in my case.. I could tell it could be the way workbench only handle shaders

Maybe this is what cased my issue https://projects.blender.org/blender/blender/issues/111619, but if so.. why not in any other view other than solid view ? I've read your comments about the no. of SSBOs binding points per shader however I dont understand it.. if that the case it shouldn't work in other views or modes.. also rendering is done perfectly in my case.. I could tell it could be the way workbench only handle shaders
Abdelaziz-Sharaf commented 2023-08-29 10:35:16 +02:00
Copy Link

Thanks to @Jeroen-Bakker 's build that fixed the issue on my ubuntu system
Think it should do the same for you on windows

Thanks to @Jeroen-Bakker 's [build](https://builder.blender.org/download/patch/PR111643/) that fixed the issue on my **ubuntu** system Think it should do the same for you on **windows**
Peter Green commented 2023-08-29 10:39:04 +02:00
Author
Copy Link

Alas (when testing the 111643 build on WIN10), I get a crash before the splash screen. Debug log attached. Also attaching a little more debug from running with --debug-all

Alas (when testing the 111643 build on WIN10), I get a crash before the splash screen. Debug log attached. Also attaching a little more debug from running with `--debug-all`
blender_debug_output.txt
84 B
debug.txt
43 KiB
Vladimir commented 2023-08-29 12:59:59 +02:00
Copy Link

The build from #111643 fixed the issue on my PC

Screenshot_20230829_135446.png

The build from #111643 fixed the issue on my PC ![Screenshot_20230829_135446.png](/attachments/88f523eb-7632-475c-a3a3-ad1e5ee1a495)
Trevor H commented 2023-08-29 14:54:55 +02:00
Copy Link

Operating system: Windows 10 home : Laptop Lenovo G50-80
Graphics card: Intel(R) HD Graphics 5500 4.4.0 - Build 20.19.15.5171

The patch build PR111616 does not work with my system spec.
As before I had to use 'blender_debug_gpu_glitchworkaround' to load Blender, the Blender Icon Application just crashes.

The issue seems to be in Viewport Solid Mode, Material and Rendered are okay!

Operating system: Windows 10 home : Laptop Lenovo G50-80 Graphics card: Intel(R) HD Graphics 5500 4.4.0 - Build 20.19.15.5171 The patch build PR111616 does not work with my system spec. As before I had to use 'blender_debug_gpu_glitchworkaround' to load Blender, the Blender Icon Application just crashes. The issue seems to be in Viewport Solid Mode, Material and Rendered are okay!
blender_debug_output.txt
166 KiB
blender_system_info.txt
12 KiB
No Shader Storage Buffer Support.jpg
129 KiB
No Shader Storage Buffer Support.jpg
Miguel Pozo commented 2023-08-29 15:44:36 +02:00
Member
Copy Link

Ok, it looks like my fix didn't work because GPU_shader_storage_buffer_objects_support is still checked when creating the Draw Manager: 60560c7da5/source/blender/draw/intern/draw_view_data.cc (L46)

However, the original workaround was seemingly implemented because SSBO shader reflection caused crashes on those Intel cards, so simply removing it could cause some fires somewhere else?
60560c7da5/source/blender/gpu/opengl/gl_shader_interface.cc (L224)

Tagging @fclem since he's the one that implemented the workaround in the first place.

Ok, it looks like my fix didn't work because `GPU_shader_storage_buffer_objects_support` is still checked when creating the Draw Manager: https://projects.blender.org/blender/blender/src/commit/60560c7da55d4c9d141d3b4a963c63dd882cfe56/source/blender/draw/intern/draw_view_data.cc#L46 However, the original workaround was seemingly implemented because SSBO shader reflection caused crashes on those Intel cards, so simply removing it could cause some fires somewhere else? https://projects.blender.org/blender/blender/src/commit/60560c7da55d4c9d141d3b4a963c63dd882cfe56/source/blender/gpu/opengl/gl_shader_interface.cc#L224 Tagging @fclem since he's the one that implemented the workaround in the first place.
Peter Green commented 2023-08-29 16:02:45 +02:00
Author
Copy Link

Much as I would love this to be fixed, I'm a realist. You can apply a sticking plaster, and then a bandage, and then a plaster cast, and still find you can't run a marathon. Switching metaphors: this may well be the asteroid that kills the dinosaurs (like me).

Much as I would love this to be fixed, I'm a realist. You can apply a sticking plaster, and then a bandage, and then a plaster cast, and still find you can't run a marathon. Switching metaphors: this may well be the asteroid that kills the dinosaurs (like me).
Trevor H commented 2023-08-29 17:33:59 +02:00
Copy Link

@snibber Peter Green

The patch build PR111616 seems to work on Linux OS. We are both on Windows 10, and my Intel Graphics Card is HD Graphics 5500 4.4.0 - Build 20.19.15.5171.

I know it's still old, but I think a bit newer than the Linux Intel Graphic Card.

I get your point though....

@snibber Peter Green The patch build PR111616 seems to work on Linux OS. We are both on Windows 10, and my Intel Graphics Card is HD Graphics 5500 4.4.0 - Build 20.19.15.5171. I know it's still old, but I think a bit newer than the Linux Intel Graphic Card. I get your point though....
Jeroen Bakker commented 2023-08-30 09:04:45 +02:00
Member
Copy Link

@pragma37 Looking at the original patch we could remove the workaround for legacy intel iGPUs as it seems drivers are updated. If some configurations still don't work, we can look at them individually. (Like the HD5500 issue)

Mesa seems to work as expected.

@pragma37 Looking at the original patch we could remove the workaround for legacy intel iGPUs as it seems drivers are updated. If some configurations still don't work, we can look at them individually. (Like the HD5500 issue) Mesa seems to work as expected.
Miguel Pozo commented 2023-08-30 12:27:57 +02:00
Member
Copy Link

@Jeroen-Bakker Ok then! 👍

@Jeroen-Bakker Ok then! 👍
Blender Bot added
Status
Resolved
 and removed
Status
Confirmed
 labels 2023-08-31 20:28:03 +02:00
Frank Paul commented 2023-09-05 00:41:42 +02:00
Copy Link

  1. In "Solid view", only ovrlay/ wireframe responds to transform/ translation.
    image
    ...and "Wiraframe" view keeps showing wire of forementioned solid object (i.e: Cube above)
    (other two "Viewport shading methods" are fine)

  2. With "Viewport debug" & "Overlay Next" enabled, Blender crashes after any 'action' performed in viewport.

HW: MS Surface Pro 3 (Intel i5-4300U, Intel HD Graphics 4400, 8GB RAM, 256GB SSD)
OS: Windows 10 Pro (22H2)

1. In "Solid view", only ovrlay/ wireframe responds to transform/ translation. ![image](/attachments/bd11b459-a915-4f9c-a19a-ced2f673d839) ...and "Wiraframe" view keeps showing wire of forementioned solid object (i.e: Cube above) (other two "Viewport shading methods" are fine) 2. With "Viewport debug" & "Overlay Next" enabled, Blender crashes after any 'action' performed in viewport. HW: MS Surface Pro 3 (Intel i5-4300U, Intel HD Graphics 4400, 8GB RAM, 256GB SSD) OS: Windows 10 Pro (22H2)
image.png
699 KiB
debug_error_report.txt
9.3 KiB
blender.crash.txt
19 KiB
Vladimir commented 2023-09-05 07:56:41 +02:00
Copy Link
  1. In "Solid view", only ovrlay/ wireframe responds to transform/ translation.

I cannot confirm it with HD 4600 and Linux

  1. With "Viewport debug" & "Overlay Next" enabled, Blender crashes after any 'action' performed in viewport.

confirm

> 1. In "Solid view", only ovrlay/ wireframe responds to transform/ translation. I cannot confirm it with HD 4600 and Linux > 2. With "Viewport debug" & "Overlay Next" enabled, Blender crashes after any 'action' performed in viewport. confirm
Jeroen Bakker commented 2023-09-05 09:36:26 +02:00
Member
Copy Link

@cardboard-2 can you open two new reports, this is not related to SSBOs. If i have to guess the first one is related to Shader Draw Parameters. Can you also try running blender with the gpu workarounds enabled

@cardboard-2 can you open two new reports, this is not related to SSBOs. If i have to guess the first one is related to Shader Draw Parameters. Can you also try running blender with the gpu workarounds enabled
👍 1
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
main
brush-assets-project
universal-scene-description
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
8 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#111587
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?