GPU subdivision option with subdivision surface modifier collapses geometry (AMD GPU) #94936

Open
opened 2022-01-15 18:27:31 +01:00 by Garek · 100 comments

System Information
Operating system: Windows-10-10.0.19044-SP0 64 Bits
Graphics card: AMD Radeon HD 7800 Series ATI Technologies Inc. 4.5.14831 Core Profile Context 21.5.2 27.20.20903.8001

Blender Version
Broken: version: 3.1.0 Alpha, branch: master, commit date: 2022-01-11 23:26, hash: ef5d01d98f
Worked: (newest version of Blender that worked as expected)

Short description of error
Subdivision surface modifier with GPU Subdivision enabled produce geometry that appear to be lost

Exact steps for others to reproduce the error

  1. Open default scene.
  2. Add subdivision surface modifier to an object.
  3. Make sure GPU Subdivision option is enabled.
  4. Uncheck Use Limit Surface
  5. Disable GPU Subdivision to see correct result.
    Last two steps are not necessary for recreation of the bug since this change- 118a219e9d
    Subdiv GPU Use Limit Surface 2022-01-15 22-13-33.mp4

NOTE: This bug seems to only occur on AMD cards on Windows.

Reproducible on:

Operating System GPU Driver
Windows 10 AMD Radeon HD 7800 Series 4.5.14831 Core Profile Context 21.5.2 27.20.20903.8001
Windows 10 AMD Radeon (TM) RX 480 4.5.14760 Core Profile Context 20.45.37.01 27.20.14537.1001
Windows 10 AMD Radeon(TM) 535 4.5.14831 Core Profile Context 21.5.2 27.20.21003.8013

Not reproducible on:

Operating System GPU Driver Version
Linux Mint 20 AMD Radeon RX550 4.5.14800 Core Profile Context 21.40
Linux Mint 20 AMD Radeon RX550 4.6 (Core Profile) Mesa 21.3.0-devel
Windows 10 Intel(R) UHD Graphics 620
Windows 10 NVIDIA GeForce GTX 1050 472.39
Linux Mint 20 NVIDIA RTX 2070 510.47.03
Linux NVIDIA GeForce GTX 970M 495.44
Windows-10-10.0.19043-SP0 64 Bits Radeon (TM) RX 480 Graphics 21.30.23.01, 22.2.3, 21.10.2
**System Information** Operating system: Windows-10-10.0.19044-SP0 64 Bits Graphics card: AMD Radeon HD 7800 Series ATI Technologies Inc. 4.5.14831 Core Profile Context 21.5.2 27.20.20903.8001 **Blender Version** Broken: version: 3.1.0 Alpha, branch: master, commit date: 2022-01-11 23:26, hash: `ef5d01d98f` Worked: (newest version of Blender that worked as expected) **Short description of error** Subdivision surface modifier with GPU Subdivision enabled produce geometry that appear to be lost **Exact steps for others to reproduce the error** 1. Open default scene. 2. Add subdivision surface modifier to an object. 3. Make sure GPU Subdivision option is enabled. 4. ~~Uncheck Use Limit Surface~~ 5. ~~Disable GPU Subdivision to see correct result.~~ Last two steps are not necessary for recreation of the bug since this change- 118a219e9d [Subdiv GPU Use Limit Surface 2022-01-15 22-13-33.mp4](https://archive.blender.org/developer/F12806362/Subdiv_GPU_Use_Limit_Surface_2022-01-15_22-13-33.mp4) ------ NOTE: This bug seems to only occur on AMD cards on Windows. **Reproducible on:** | Operating System | GPU | Driver | | ----------------|-------------|---------| | Windows 10 | AMD Radeon HD 7800 Series | 4.5.14831 Core Profile Context 21.5.2 27.20.20903.8001 | | Windows 10 | AMD Radeon (TM) RX 480 | 4.5.14760 Core Profile Context 20.45.37.01 27.20.14537.1001 | | Windows 10 | AMD Radeon(TM) 535 | 4.5.14831 Core Profile Context 21.5.2 27.20.21003.8013 | **Not reproducible on:** | Operating System | GPU | Driver Version | | -----------------|-------------|---------| | Linux Mint 20 | AMD Radeon RX550 | 4.5.14800 Core Profile Context 21.40 | | Linux Mint 20 | AMD Radeon RX550 | 4.6 (Core Profile) Mesa 21.3.0-devel | | Windows 10 | Intel(R) UHD Graphics 620 | | | Windows 10 | NVIDIA GeForce GTX 1050 | 472.39 | | Linux Mint 20 | NVIDIA RTX 2070 | 510.47.03 | | Linux | NVIDIA GeForce GTX 970M | 495.44 |Windows-10-10.0.19043-SP0 64 Bits|Radeon (TM) RX 480 Graphics| 21.30.23.01, 22.2.3, 21.10.2 |
Author

Added subscriber: @Garek

Added subscriber: @Garek

#104311 was marked as duplicate of this issue

#104311 was marked as duplicate of this issue

#103168 was marked as duplicate of this issue

#103168 was marked as duplicate of this issue

#102104 was marked as duplicate of this issue

#102104 was marked as duplicate of this issue

#101935 was marked as duplicate of this issue

#101935 was marked as duplicate of this issue

#101047 was marked as duplicate of this issue

#101047 was marked as duplicate of this issue

#100964 was marked as duplicate of this issue

#100964 was marked as duplicate of this issue

#100124 was marked as duplicate of this issue

#100124 was marked as duplicate of this issue

#100080 was marked as duplicate of this issue

#100080 was marked as duplicate of this issue

#99351 was marked as duplicate of this issue

#99351 was marked as duplicate of this issue

#99056 was marked as duplicate of this issue

#99056 was marked as duplicate of this issue

#98854 was marked as duplicate of this issue

#98854 was marked as duplicate of this issue

#98569 was marked as duplicate of this issue

#98569 was marked as duplicate of this issue

#98242 was marked as duplicate of this issue

#98242 was marked as duplicate of this issue

#97825 was marked as duplicate of this issue

#97825 was marked as duplicate of this issue

#97725 was marked as duplicate of this issue

#97725 was marked as duplicate of this issue

#97493 was marked as duplicate of this issue

#97493 was marked as duplicate of this issue

#97381 was marked as duplicate of this issue

#97381 was marked as duplicate of this issue

#97358 was marked as duplicate of this issue

#97358 was marked as duplicate of this issue

#97336 was marked as duplicate of this issue

#97336 was marked as duplicate of this issue

#97325 was marked as duplicate of this issue

#97325 was marked as duplicate of this issue

#97178 was marked as duplicate of this issue

#97178 was marked as duplicate of this issue

#97113 was marked as duplicate of this issue

#97113 was marked as duplicate of this issue

#96362 was marked as duplicate of this issue

#96362 was marked as duplicate of this issue

#96658 was marked as duplicate of this issue

#96658 was marked as duplicate of this issue

#96665 was marked as duplicate of this issue

#96665 was marked as duplicate of this issue

#96571 was marked as duplicate of this issue

#96571 was marked as duplicate of this issue

#96277 was marked as duplicate of this issue

#96277 was marked as duplicate of this issue

#96506 was marked as duplicate of this issue

#96506 was marked as duplicate of this issue

#96374 was marked as duplicate of this issue

#96374 was marked as duplicate of this issue

#96343 was marked as duplicate of this issue

#96343 was marked as duplicate of this issue

#96104 was marked as duplicate of this issue

#96104 was marked as duplicate of this issue
Member

Added subscriber: @PratikPB2123

Added subscriber: @PratikPB2123
Member

Changed status from 'Needs Triage' to: 'Confirmed'

Changed status from 'Needs Triage' to: 'Confirmed'

Added subscriber: @kevindietrich

Added subscriber: @kevindietrich

Changed status from 'Confirmed' to: 'Needs User Info'

Changed status from 'Confirmed' to: 'Needs User Info'

Could you try again to reproduce in a build with c5dcfb63d9 applied? (If you cannot compile Blender on your own, you can wait about 24 hours from the time of this comment until the buildbots have delivered a new experimental build). It could be that the bug is actually the same as #94881 but exposed in a different code path. At least I cannot reproduce, but it could be a driver thing.

Could you try again to reproduce in a build with c5dcfb63d9 applied? (If you cannot compile Blender on your own, you can wait about 24 hours from the time of this comment until the buildbots have delivered a new experimental build). It could be that the bug is actually the same as #94881 but exposed in a different code path. At least I cannot reproduce, but it could be a driver thing.
Member

@kevindietrich, can still reproduce on latest buildbot build (9153bf24cb)
I suspect it occurs on AMD GPU only.

@kevindietrich, can still reproduce on latest buildbot build (9153bf24cbf2) I suspect it occurs on AMD GPU only.
Author

Yeah still happening with that build.

Yeah still happening with that build.

In #94936#1309670, @PratikPB2123 wrote:
@kevindietrich, can still reproduce on latest buildbot build (9153bf24cb)
I suspect it occurs on AMD GPU only.

I am using my AMD card, and I still cannot reproduce.

From system-info.txt:

renderer:	'Radeon RX550/550 Series (POLARIS12, DRM 3.43.0, 5.4.0-99-generic, LLVM 12.0.1)'
vendor:		'AMD'
version:	'4.6 (Core Profile) Mesa 21.3.0-devel'
> In #94936#1309670, @PratikPB2123 wrote: > @kevindietrich, can still reproduce on latest buildbot build (9153bf24cbf2) > I suspect it occurs on AMD GPU only. I am using my AMD card, and I still cannot reproduce. From `system-info.txt`: ``` renderer: 'Radeon RX550/550 Series (POLARIS12, DRM 3.43.0, 5.4.0-99-generic, LLVM 12.0.1)' vendor: 'AMD' version: '4.6 (Core Profile) Mesa 21.3.0-devel' ```
Member

Can reproduce on Graphics card : AMD Radeon(TM) 535
But doesn't happen with: Graphics card : Intel(R) UHD Graphics 620
Operating system : Windows-10-10.0.19043-SP0 64 Bits

Can reproduce on `Graphics card : AMD Radeon(TM) 535` But doesn't happen with: `Graphics card : Intel(R) UHD Graphics 620` `Operating system : Windows-10-10.0.19043-SP0 64 Bits`
Member

Added subscriber: @lichtwerk

Added subscriber: @lichtwerk
Member

Cannot reproduce here

**System Information**
Operating system: Linux-5.13.0-0.rc6.45.fc35.x86_64-x86_64-with-glibc2.34.9000 64 Bits
Graphics card: NVIDIA GeForce GTX 970M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 495.44
version: 3.2.0 Alpha, branch: master, commit date: 2022-02-18 07:30, hash: `rB4ad4d8a59c0a`
Cannot reproduce here ``` **System Information** Operating system: Linux-5.13.0-0.rc6.45.fc35.x86_64-x86_64-with-glibc2.34.9000 64 Bits Graphics card: NVIDIA GeForce GTX 970M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 495.44 version: 3.2.0 Alpha, branch: master, commit date: 2022-02-18 07:30, hash: `rB4ad4d8a59c0a` ```
Member

Added subscriber: @wannes.malfait

Added subscriber: @wannes.malfait
Member

Can't reproduce here either:

**System Information**
Operating system: Windows-10-10.0.19043-SP0 64 Bits
Graphics card: NVIDIA GeForce GTX 1050/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.39

Using latest build (61aaeb3745)

Can't reproduce here either: ``` **System Information** Operating system: Windows-10-10.0.19043-SP0 64 Bits Graphics card: NVIDIA GeForce GTX 1050/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.39 ``` Using latest build (61aaeb3745)

Added subscriber: @mano-wii

Added subscriber: @mano-wii

Can reproduce on:

**System Information**
Operating system: Windows-10-10.0.22000-SP0 64 Bits
Graphics card: Radeon (TM) RX 480 Graphics ATI Technologies Inc. 4.5.14760 Core Profile Context 20.45.37.01 27.20.14537.1001
Can reproduce on: ``` **System Information** Operating system: Windows-10-10.0.22000-SP0 64 Bits Graphics card: Radeon (TM) RX 480 Graphics ATI Technologies Inc. 4.5.14760 Core Profile Context 20.45.37.01 27.20.14537.1001 ```
Author

I think it's pretty evident at this point that bug is only for old AMD cards on Windows. Unless someone on MacOS with AMD can reproduce, that's only thing left.

I think it's pretty evident at this point that bug is only for old AMD cards on Windows. Unless someone on MacOS with AMD can reproduce, that's only thing left.

I tried again with the proprietary driver, but is still not reproduced:

renderer:	'Radeon RX550/550 Series'
vendor:		'ATI Technologies Inc.'
version:	'4.5.14800 Core Profile Context 21.40'

Some people can reproduce on both older and newer drivers. So maybe Windows drivers are indeed the culprits.

I tried again with the proprietary driver, but is still not reproduced: ``` renderer: 'Radeon RX550/550 Series' vendor: 'ATI Technologies Inc.' version: '4.5.14800 Core Profile Context 21.40' ``` Some people can reproduce on both older and newer drivers. So maybe Windows drivers are indeed the culprits.
Member

I think we could mark this as "Confirmed" since few of us can reproduce (With necessary edits in task description)

I think we could mark this as "Confirmed" since few of us can reproduce (With necessary edits in task description)

Changed status from 'Needs User Info' to: 'Confirmed'

Changed status from 'Needs User Info' to: 'Confirmed'

Can someone who is to reproduce run blender with --debug-gpu and paste the output? Maybe that can give some useful information.

Can someone who is to reproduce run blender with `--debug-gpu` and paste the output? Maybe that can give some useful information.
Author

I ran blender_debug_gpu_glitchworkaround.cmd and was unable to reproduce issue.
blender_debug_output.txt
blender_system_info.txt
Running blender_debug_gpu.cmd still produces issue.
blender_debug_output.txt
blender_system_info.txt

I ran `blender_debug_gpu_glitchworkaround.cmd` and was unable to reproduce issue. [blender_debug_output.txt](https://archive.blender.org/developer/F12885226/blender_debug_output.txt) [blender_system_info.txt](https://archive.blender.org/developer/F12885227/blender_system_info.txt) Running `blender_debug_gpu.cmd` still produces issue. [blender_debug_output.txt](https://archive.blender.org/developer/F12885229/blender_debug_output.txt) [blender_system_info.txt](https://archive.blender.org/developer/F12885230/blender_system_info.txt)

@Garek, using the glitchworkaround command actually disables GPU subdivision so that's why it worked :) For another bug fix, I removed the code that is only executed when limit surface is on, at least on the GPU side. Can you try in a new build if it works or not? If that was the cause of the issue, then it should also be broken when limit surface is on and #96104 would probably be the same issue as this.

@Garek, using the `glitchworkaround` command actually disables GPU subdivision so that's why it worked :) For another bug fix, I removed the code that is only executed when limit surface is on, at least on the GPU side. Can you try in a new build if it works or not? If that was the cause of the issue, then it should also be broken when limit surface is on and #96104 would probably be the same issue as this.
Member

Added subscriber: @Jeroen-Bakker

Added subscriber: @Jeroen-Bakker
Member

@mano-wii can you confirm if this is still reproduceable when using the latest AMD drivers?

@mano-wii can you confirm if this is still reproduceable when using the latest AMD drivers?
Member

looking at the reports we might want to disable compute shaders for 21.5.2 drivers. The driver is a WQHL driver for legacy platforms. I suspect an error there, but I cannot be certain as I don't have the platform to test the driver. We might also want to add the 20.* drivers as well. for the release.

All current drivers for Polaris based GPU have been validated.

looking at the reports we might want to disable compute shaders for 21.5.2 drivers. The driver is a WQHL driver for legacy platforms. I suspect an error there, but I cannot be certain as I don't have the platform to test the driver. We might also want to add the 20.* drivers as well. for the release. All current drivers for Polaris based GPU have been validated.

In #94936#1315977, @Jeroen-Bakker wrote:
@mano-wii can you confirm if this is still reproduceable when using the latest AMD drivers?

The problem was resolved after I updated to the latest available driver.


Operating system: Windows-10-10.0.22000-SP0 64 Bits
Graphics card: Radeon (TM) RX 480 Graphics ATI Technologies Inc. 4.5.14802 Core Profile/Debug Context 22.2.3 30.0.14029.5006

> In #94936#1315977, @Jeroen-Bakker wrote: > @mano-wii can you confirm if this is still reproduceable when using the latest AMD drivers? The problem was resolved after I updated to the latest available driver. --- Operating system: Windows-10-10.0.22000-SP0 64 Bits Graphics card: Radeon (TM) RX 480 Graphics ATI Technologies Inc. 4.5.14802 Core Profile/Debug Context 22.2.3 30.0.14029.5006
Author

@kevindietrich since buildbot wasn't working until recently I could not test new changes.

Using 3.1 with hash: 9c2e385509 bug is present even without unchecking Use Limit Surface, it's appearance is same (shows only one line in wireframe, like in original report video)
Same with 3.2 hash: eabdcdcd44.
I didn't updated drivers yet, actually I'm not sure if I can at all.

@kevindietrich since buildbot wasn't working until recently I could not test new changes. Using 3.1 with hash: `9c2e385509` bug is present even without unchecking `Use Limit Surface`, it's appearance is same (shows only one line in wireframe, like in original report video) Same with 3.2 hash: `eabdcdcd44`. I didn't updated drivers yet, actually I'm not sure if I can at all.

@Garek, thanks for testing. So #96104 is indeed the same issue (the only code path affected by "Use Limit Surface" was removed).

@Garek, thanks for testing. So #96104 is indeed the same issue (the only code path affected by "Use Limit Surface" was removed).
Pratik Borhade changed title from Subdivision: GPU option without Use Limit Surface collapses geometry to Subdivision: GPU option with subdivision surface modifier collapses geometry 2022-03-04 10:38:16 +01:00

Added subscriber: @Ghost_Snake

Added subscriber: @Ghost_Snake
Member

Added subscriber: @Rzyas

Added subscriber: @Rzyas
Member

Added subscribers: @Alfred-Borg, @iss

Added subscribers: @Alfred-Borg, @iss
Member

Added subscriber: @A-T

Added subscriber: @A-T

Added subscriber: @Fuxna

Added subscriber: @Fuxna

Changed status from 'Confirmed' to: 'Resolved'

Changed status from 'Confirmed' to: 'Resolved'
Alfred Borg self-assigned this 2022-03-18 12:49:13 +01:00

The issue was resolved when the GPU Subdivision was turned off in the Preferences as was suggested by your team. It seems that my PC has an old AMD since there have not been any Driver updates. I also have installed Windows 11 a while back and it has been kept up to date.
Thanks for resolving the issue for me.

The issue was resolved when the GPU Subdivision was turned off in the Preferences as was suggested by your team. It seems that my PC has an old AMD since there have not been any Driver updates. I also have installed Windows 11 a while back and it has been kept up to date. Thanks for resolving the issue for me.

Changed status from 'Resolved' to: 'Confirmed'

Changed status from 'Resolved' to: 'Confirmed'
Alfred Borg was unassigned by Germano Cavalcante 2022-03-18 13:07:39 +01:00

Even though the problem isn't directly in Blender, let's keep the report open a little longer in order to track reports about the same problem.

Note that disabling GPU Subdivision is not actually a bug fix.

Updating GPU drivers fixed it even in cases of older GPUs (like Radeon RX 480). It's good to investigate why it didn't solve in your case.

Even though the problem isn't directly in Blender, let's keep the report open a little longer in order to track reports about the same problem. Note that disabling `GPU Subdivision` is not actually a bug fix. Updating GPU drivers fixed it even in cases of older GPUs (like Radeon RX 480). It's good to investigate why it didn't solve in your case.
Member

Added subscriber: @ErickNyanduKabongo

Added subscriber: @ErickNyanduKabongo
Member

Added subscriber: @SDDice

Added subscriber: @SDDice

In my case even though I have updated my drivers, I m still getting the problem, but turning off GPU subdivision in the preferences solved it.

In my case even though I have updated my drivers, I m still getting the problem, but turning off GPU subdivision in the preferences solved it.
Member

Added subscribers: @Rony1012, @Alaska

Added subscribers: @Rony1012, @Alaska
Member

In #94936#1326584, @ErickNyanduKabongo wrote:
In my case even though I have updated my drivers, I m still getting the problem, but turning off GPU subdivision in the preferences solved it.

Hi, GPU model of AMD Radeon R7 200 Series has been moved to legacy support: https://www.amd.com/en/support/kb/faq/gpu-630
So upgrading them is less likely to fix the problem.

I don't think there is any proper fix yet.

> In #94936#1326584, @ErickNyanduKabongo wrote: > In my case even though I have updated my drivers, I m still getting the problem, but turning off GPU subdivision in the preferences solved it. Hi, GPU model of AMD Radeon R7 200 Series has been moved to legacy support: https://www.amd.com/en/support/kb/faq/gpu-630 So upgrading them is less likely to fix the problem. I don't think there is any proper fix yet.

Added subscriber: @cheniercabrera

Added subscriber: @cheniercabrera
Member

Added subscriber: @George-Solodkov

Added subscriber: @George-Solodkov
Member

Talked to @kevindietrich , setting to High prio (since it is a bug in a new feature according to the playbook

Talked to @kevindietrich , setting to High prio (since it is a bug in a new feature according to the [playbook ](https://wiki.blender.org/wiki/Process/Bug_Reports/Triaging_Playbook)
Philipp Oeser changed title from Subdivision: GPU option with subdivision surface modifier collapses geometry to GPU subdivision option with subdivision surface modifier collapses geometry 2022-04-13 11:16:33 +02:00
Member

Added subscribers: @byjalal, @ThomasDinges

Added subscribers: @byjalal, @ThomasDinges

Added subscriber: @jason1

Added subscriber: @jason1

In #94936#1313102, @kevindietrich wrote:
Can someone who is to reproduce run blender with --debug-gpu and paste the output? Maybe that can give some useful information.

I humbly offer what I think is a related issue I reported here:

https://developer.blender.org/T97330

I don't see a geometry collapse, rather a crash. In a comment on my issue, I included the requested output.

> In #94936#1313102, @kevindietrich wrote: > Can someone who is to reproduce run blender with `--debug-gpu` and paste the output? Maybe that can give some useful information. I humbly offer what I think is a related issue I reported here: https://developer.blender.org/T97330 I don't see a geometry collapse, rather a crash. In a comment on my issue, I included the requested output.

Added subscriber: @Rrosales04

Added subscriber: @Rrosales04
Member

Added subscriber: @yan-1

Added subscriber: @yan-1
Member

Added subscriber: @Whelfons

Added subscriber: @Whelfons
Member

Added subscriber: @vicen

Added subscriber: @vicen
Member

Added subscriber: @Zseto

Added subscriber: @Zseto
Member

Added subscriber: @javicoro99

Added subscriber: @javicoro99

Lowering the priority on this one as no one in the module team seem to have the right hardware to reproduce and fix this.

Lowering the priority on this one as no one in the module team seem to have the right hardware to reproduce and fix this.
Member

Added subscriber: @Sebas

Added subscriber: @Sebas
Member

Added subscriber: @Icygamer876

Added subscriber: @Icygamer876

Added subscriber: @lightbl

Added subscriber: @lightbl
Member

Added subscriber: @MistyWhisp

Added subscriber: @MistyWhisp
Member

Added subscriber: @myla-strevens

Added subscriber: @myla-strevens
Member

Added subscriber: @the_kay_one

Added subscriber: @the_kay_one
Pratik Borhade changed title from GPU subdivision option with subdivision surface modifier collapses geometry to GPU subdivision option with subdivision surface modifier collapses geometry (AMD GPU) 2022-07-31 15:28:00 +02:00

Added subscribers: @insebard, @TheRekrab

Added subscribers: @insebard, @TheRekrab
Member

Added subscriber: @kripog

Added subscriber: @kripog
Member

Added subscriber: @charlyrdz

Added subscriber: @charlyrdz
Member

Added subscriber: @Mare-2

Added subscriber: @Mare-2
Member

Added subscribers: @Aggelos, @OmarEmaraDev

Added subscribers: @Aggelos, @OmarEmaraDev
Member

Added subscriber: @Radik

Added subscriber: @Radik
Member

Added subscriber: @RoyMarVal

Added subscriber: @RoyMarVal
Philipp Oeser removed the
Interest
EEVEE & Viewport
label 2023-02-09 15:12:57 +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
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
No Milestone
No project
No Assignees
12 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#94936
No description provided.