blender
/
blender
133
398
Fork 578
Code Issues 6.3k Pull Requests 746 Projects 19 Wiki Activity

Overlapping geometry shows black faces on Cycles Blender 3.1 (Ray Tracing Precision) #96475

New Issue
Closed
opened 2022-03-15 02:56:10 +01:00 by Emi Martinez · 49 comments
Emi Martinez commented 2022-03-15 02:56:10 +01:00
Copy Link

System Information
Operating system: Windows-10-10.0.19041-SP0 64 Bits
Graphics card: NVIDIA GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 511.65

Blender Version
Broken: version: 3.1.0, branch: master, commit date: 2022-03-08 18:16, hash: c77597cd0e
Worked: 3.0.1

Short description of error
The new feature "Cycles RayTracing Precision"
https://wiki.blender.org/wiki/Reference/Release_Notes/3.1/Cycles#Ray_Tracing_Precision
Is producing black faces on Overlapping geometry. This not happend on Blender 3.0.1.

I think an on /off switch for the Cycles RayTracing Precision could solve the overlapping geometry problem.
Thanks!

Exact steps for others to reproduce the error
Just open the file on Blender 3.0.1 and 3.1 and you'll see the difference.

Here are some images:

F12928198 F12928200
Blender 3.0.1 Blender 3.1

cubes overlapping.blend

Here is a link to blender community for requesting an On /Off Switch to solve the overlapping geometry problem:
https://blender.community/c/rightclickselect/084V/

**System Information** Operating system: Windows-10-10.0.19041-SP0 64 Bits Graphics card: NVIDIA GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 511.65 **Blender Version** Broken: version: 3.1.0, branch: master, commit date: 2022-03-08 18:16, hash: `c77597cd0e` Worked: 3.0.1 **Short description of error** The new feature "Cycles RayTracing Precision" https://wiki.blender.org/wiki/Reference/Release_Notes/3.1/Cycles#Ray_Tracing_Precision Is producing black faces on Overlapping geometry. This not happend on Blender 3.0.1. I think an on /off switch for the Cycles RayTracing Precision could solve the overlapping geometry problem. Thanks! **Exact steps for others to reproduce the error** Just open the file on Blender 3.0.1 and 3.1 and you'll see the difference. Here are some images: |![F12928198](https://archive.blender.org/developer/F12928198/image.png)|![F12928200](https://archive.blender.org/developer/F12928200/image.png)| | -- | -- | |Blender 3.0.1|Blender 3.1| [cubes overlapping.blend](https://archive.blender.org/developer/F12928193/cubes_overlapping.blend) Here is a link to blender community for requesting an On /Off Switch to solve the overlapping geometry problem: https://blender.community/c/rightclickselect/084V/
Emi Martinez commented 2022-03-15 02:56:10 +01:00
Author
Copy Link

Added subscriber: @Emi_Martinez

Added subscriber: @Emi_Martinez
blender-admin commented 2022-03-15 02:56:10 +01:00
Copy Link

#102987 was marked as duplicate of this issue

#102987 was marked as duplicate of this issue
blender-admin commented 2022-03-15 02:56:10 +01:00
Copy Link

#101477 was marked as duplicate of this issue

#101477 was marked as duplicate of this issue
blender-admin commented 2022-03-15 02:56:10 +01:00
Copy Link

#100154 was marked as duplicate of this issue

#100154 was marked as duplicate of this issue
blender-admin commented 2022-03-15 02:56:10 +01:00
Copy Link

#99238 was marked as duplicate of this issue

#99238 was marked as duplicate of this issue
blender-admin commented 2022-03-15 02:56:10 +01:00
Copy Link

#99086 was marked as duplicate of this issue

#99086 was marked as duplicate of this issue
blender-admin commented 2022-03-15 02:56:10 +01:00
Copy Link

#98988 was marked as duplicate of this issue

#98988 was marked as duplicate of this issue
blender-admin commented 2022-03-15 02:56:10 +01:00
Copy Link

#98465 was marked as duplicate of this issue

#98465 was marked as duplicate of this issue
blender-admin commented 2022-03-15 02:56:10 +01:00
Copy Link

#97736 was marked as duplicate of this issue

#97736 was marked as duplicate of this issue
blender-admin commented 2022-03-15 02:56:10 +01:00
Copy Link

#97729 was marked as duplicate of this issue

#97729 was marked as duplicate of this issue
blender-admin commented 2022-03-15 02:56:10 +01:00
Copy Link

#97494 was marked as duplicate of this issue

#97494 was marked as duplicate of this issue
blender-admin commented 2022-03-15 02:56:10 +01:00
Copy Link

#97399 was marked as duplicate of this issue

#97399 was marked as duplicate of this issue
blender-admin commented 2022-03-15 02:56:10 +01:00
Copy Link

#96996 was marked as duplicate of this issue

#96996 was marked as duplicate of this issue
blender-admin commented 2022-03-15 02:56:10 +01:00
Copy Link

#96958 was marked as duplicate of this issue

#96958 was marked as duplicate of this issue
Emi Martinez changed title from Overlapping geometry shows black faces on Blender 3.1 to Overlapping geometry shows black faces on Cycles Blender 3.1 2022-03-15 03:02:09 +01:00
Alaska commented 2022-03-15 03:04:51 +01:00
Member
Copy Link

Added subscribers: @leesonw, @brecht, @Alaska

Added subscribers: @leesonw, @brecht, @Alaska
Alaska commented 2022-03-15 03:04:51 +01:00
Member
Copy Link

Changed status from 'Needs Triage' to: 'Needs Developer To Reproduce'

Changed status from 'Needs Triage' to: 'Needs Developer To Reproduce'
Alaska commented 2022-03-15 03:04:51 +01:00
Member
Copy Link

CC @brecht or @leesonw what should be done with this report? It seems like this is a known issue and I'm not sure how easy it is to fix.

In #96475#1323188, @Alaska wrote:
I just thought I would add an extra comment to help the developers make a decision.

From my own testing this issue does not effect OptiX. CUDA and CPU when testing on my computer both have issues. This issue was introduced by 74afc86d4b based on my own testing.

It looks like this is a known issue. As noted in the release notes:

There can still be artifacts with rendering overlapping geometry, in some cases more severe than before. Such overlapping geometry should be removed, or have a small distance added in between.

Could we have an on / off switch for this feature?
Thanks!

Please use other channels for user feedback and feature requests: https://wiki.blender.org/wiki/Communication/Contact#User_Feedback_and_Requests

CC @brecht or @leesonw what should be done with this report? It seems like this is a known issue and I'm not sure how easy it is to fix. > In #96475#1323188, @Alaska wrote: > I just thought I would add an extra comment to help the developers make a decision. > > From my own testing this issue does not effect OptiX. CUDA and CPU when testing on my computer both have issues. This issue was introduced by 74afc86d4b based on my own testing. --- It looks like this is a known issue. As noted in the release notes: > There can still be artifacts with rendering overlapping geometry, in some cases more severe than before. Such overlapping geometry should be removed, or have a small distance added in between. --- > Could we have an on / off switch for this feature? > Thanks! Please use other channels for user feedback and feature requests: https://wiki.blender.org/wiki/Communication/Contact#User_Feedback_and_Requests
Emi Martinez changed title from Overlapping geometry shows black faces on Cycles Blender 3.1 to Overlapping geometry shows black faces on Cycles Blender 3.1 (Ray Tracing Precision) 2022-03-15 03:16:42 +01:00
Alaska commented 2022-03-15 05:11:20 +01:00
Member
Copy Link

I just thought I would add an extra comment to help the developers make a decision.

From my own testing this issue does not effect OptiX. CUDA and CPU when testing on my computer both have issues. This issue was introduced by 74afc86d4b based on my own testing.

I just thought I would add an extra comment to help the developers make a decision. From my own testing this issue does not effect OptiX. CUDA and CPU when testing on my computer both have issues. This issue was introduced by 74afc86d4b based on my own testing.
lictex_ commented 2022-03-15 05:37:01 +01:00
Copy Link

Added subscriber: @lictex_1

Added subscriber: @lictex_1
Brecht Van Lommel commented 2022-03-15 16:00:04 +01:00
Owner
Copy Link

Changed status from 'Needs Developer To Reproduce' to: 'Archived'

Changed status from 'Needs Developer To Reproduce' to: 'Archived'
Brecht Van Lommel commented 2022-03-15 16:00:04 +01:00
Owner
Copy Link

This is not considered a bug currently, it's a documented trade-off of the new method.

This is not considered a bug currently, it's a documented trade-off of the new method.
Alaska commented 2022-03-15 21:57:24 +01:00
Member
Copy Link

In #96475#1323543, @brecht wrote:
This is not considered a bug currently, it's a documented trade-off of the new method.

Are the rendering differences between CPU/CUDA and OptiX in this scenario considered a bug?

> In #96475#1323543, @brecht wrote: > This is not considered a bug currently, it's a documented trade-off of the new method. Are the rendering differences between CPU/CUDA and OptiX in this scenario considered a bug?
Brecht Van Lommel commented 2022-03-16 12:51:09 +01:00
Owner
Copy Link

No.

No.
Emi Martinez commented 2022-03-17 02:03:56 +01:00
Author
Copy Link

In #96475#1323543, @brecht wrote:
This is not considered a bug currently, it's a documented trade-off of the new method.

I really don't know if this is the pleace to ask.
But there is a way to implement an on /off switch for this feature?
I know that blender 3.1 release was about performance, but this trade-off is huge!

> In #96475#1323543, @brecht wrote: > This is not considered a bug currently, it's a documented trade-off of the new method. I really don't know if this is the pleace to ask. But there is a way to implement an on /off switch for this feature? I know that blender 3.1 release was about performance, but this trade-off is huge!
Germano Cavalcante commented 2022-04-04 16:06:26 +02:00
Member
Copy Link

Added subscribers: @rawee-4, @Bhagath-Goud, @juang3d, @dupoxy, @PratikPB2123, @mano-wii

Added subscribers: @rawee-4, @Bhagath-Goud, @juang3d, @dupoxy, @PratikPB2123, @mano-wii
Alaska commented 2022-04-17 10:28:25 +02:00
Member
Copy Link

Added subscriber: @Icedcg

Added subscriber: @Icedcg
Alex commented 2022-04-17 10:34:39 +02:00
Copy Link

Sorry, Didn't find same bug submitted before. So what about the people that don't have GPU with OptiX tech? Previously it was so convenient to not bother with overlapping geometry to render something. But now you always have to merge this meshes into a single mesh... Just consumes time for no reason honestly.

Sorry, Didn't find same bug submitted before. So what about the people that don't have GPU with OptiX tech? Previously it was so convenient to not bother with overlapping geometry to render something. But now you always have to merge this meshes into a single mesh... Just consumes time for no reason honestly.
Emi Martinez commented 2022-04-17 18:06:45 +02:00
Author
Copy Link

In #96475#1342416, @Icedcg wrote:
Sorry, Didn't find same bug submitted before. So what about the people that don't have GPU with OptiX tech? Previously it was so convenient to not bother with overlapping geometry to render something. But now you always have to merge this meshes into a single mesh... Just consumes time for no reason honestly.

Completely agree.
Here is a link to blender community for requesting an On /Off Switch to solve the overlapping geometry problem:
https://blender.community/c/rightclickselect/084V/

> In #96475#1342416, @Icedcg wrote: > Sorry, Didn't find same bug submitted before. So what about the people that don't have GPU with OptiX tech? Previously it was so convenient to not bother with overlapping geometry to render something. But now you always have to merge this meshes into a single mesh... Just consumes time for no reason honestly. Completely agree. Here is a link to blender community for requesting an On /Off Switch to solve the overlapping geometry problem: https://blender.community/c/rightclickselect/084V/
Pratik Borhade commented 2022-04-21 05:22:17 +02:00
Member
Copy Link

Added subscriber: @zhanghua

Added subscriber: @zhanghua
Pratik Borhade commented 2022-04-30 07:11:08 +02:00
Member
Copy Link

Added subscriber: @Vyach

Added subscriber: @Vyach
Pratik Borhade commented 2022-05-02 19:24:32 +02:00
Member
Copy Link

Added subscriber: @Rincewind3D-1

Added subscriber: @Rincewind3D-1
Eugene Du commented 2022-06-19 16:22:45 +02:00
Copy Link

Added subscriber: @APEC

Added subscriber: @APEC
Eugene Du commented 2022-06-19 16:22:45 +02:00
Copy Link

Not acceptable "trade-off", for architectural modeling...

Not acceptable "trade-off", for architectural modeling...
Emi Martinez commented 2022-06-19 20:36:18 +02:00
Author
Copy Link

In #96475#1376513, @APEC wrote:
Not acceptable "trade-off", for architectural modeling...

Not acceptable at all, in any modelling work. There should be a way to swith this off..

> In #96475#1376513, @APEC wrote: > Not acceptable "trade-off", for architectural modeling... Not acceptable at all, in any modelling work. There should be a way to swith this off..
Omar Emara commented 2022-06-22 11:40:51 +02:00
Member
Copy Link

Added subscriber: @Damian-Trebilco

Added subscriber: @Damian-Trebilco
Brett Witty commented 2022-06-30 12:37:31 +02:00
Copy Link

Added subscriber: @Brett-Witty

Added subscriber: @Brett-Witty
Brett Witty commented 2022-06-30 22:29:34 +02:00
Copy Link

I found this behaviour continued independent of choosing CPU, CUDA or Optix rendering in Cycles.

If it's documented behaviour, it doesn't appear to come with tools to identify or deal with the "trade off". I had components that rendered fine individually, but exhibited the bug only in a geometry nodes combined object.

I found this behaviour continued independent of choosing CPU, CUDA or Optix rendering in Cycles. If it's documented behaviour, it doesn't appear to come with tools to identify or deal with the "trade off". I had components that rendered fine individually, but exhibited the bug only in a geometry nodes combined object.
Pratik Borhade commented 2022-08-03 03:54:15 +02:00
Member
Copy Link

Added subscribers: @bribi, @iss

Added subscribers: @bribi, @iss
Brett Witty commented 2022-08-03 04:06:55 +02:00
Copy Link

I noticed that this problem can be somewhat alleviated if the mesh is made out of geometry nodes. Realize Instances seems to fix the geometry for the renderer to not exhibit this behaviour.

I noticed that this problem can be somewhat alleviated if the mesh is made out of geometry nodes. *Realize Instances* seems to fix the geometry for the renderer to not exhibit this behaviour.
Vyacheslav Kobozev commented 2022-08-03 10:38:20 +02:00
Copy Link

In #96475#1399011, @Brett-Witty wrote:
I noticed that this problem can be somewhat alleviated if the mesh is made out of geometry nodes. Realize Instances seems to fix the geometry for the renderer to not exhibit this behaviour.

Short test. Not true. Please attach example.
66671837.png

> In #96475#1399011, @Brett-Witty wrote: > I noticed that this problem can be somewhat alleviated if the mesh is made out of geometry nodes. *Realize Instances* seems to fix the geometry for the renderer to not exhibit this behaviour. Short test. Not true. Please attach example. ![66671837.png](https://archive.blender.org/developer/F13333262/66671837.png)
Brett Witty commented 2022-08-03 12:06:56 +02:00
Copy Link

My apologies, issue #99238 was merged with this one. The geometry isn't as obviously overlapping as your example, (and seems to be mostly just intersecting) but seems to manifest in the same problem. In that issue, Realize Instances did fix it. In your example, the realized instances will be definitely overlapping, but in #99238 it was not the case.

These might be unrelated issues, but I didn't merge the issues.

My apologies, issue #99238 was merged with this one. The geometry isn't as obviously overlapping as your example, (and seems to be mostly just intersecting) but seems to manifest in the same problem. In that issue, *Realize Instances* did fix it. In your example, the realized instances will be definitely overlapping, but in #99238 it was not the case. These might be unrelated issues, but I didn't merge the issues.
Vyacheslav Kobozev commented 2022-08-03 15:28:24 +02:00
Copy Link

@Brett-Witty my guess that vertices have little shift (due to float error) after realizing. So z-fighting appears less.

@Brett-Witty my guess that vertices have little shift (due to float error) after realizing. So z-fighting appears less.
Eugene Du commented 2022-09-08 09:59:17 +02:00
Copy Link

Any solution or workaround on this problem?
I cant switch to blender 3+ because of this...

Any solution or workaround on this problem? I cant switch to blender 3+ because of this...
Vyacheslav Kobozev commented 2022-09-08 12:59:12 +02:00
Copy Link

In #96475#1413889, @APEC wrote:
Any solution or workaround on this problem?
I cant switch to blender 3+ because of this...

only to not make z-fighting polys.
Displace modifier or shrinkwrap-offset will help to fix,

> In #96475#1413889, @APEC wrote: > Any solution or workaround on this problem? > I cant switch to blender 3+ because of this... only to not make z-fighting polys. Displace modifier or shrinkwrap-offset will help to fix,
Eugene Du commented 2022-09-08 13:03:13 +02:00
Copy Link

In #96475#1413985, @Vyach wrote:
only to not make z-fighting polys.
Displace modifier or shrinkwrap-offset will help to fix,

not possible in architecture modeling with hundreds small elements (objects) or even in one single mesh to do that...

> In #96475#1413985, @Vyach wrote: > only to not make z-fighting polys. > Displace modifier or shrinkwrap-offset will help to fix, not possible in architecture modeling with hundreds small elements (objects) or even in one single mesh to do that...
Vyacheslav Kobozev commented 2022-09-08 22:20:04 +02:00
Copy Link

In #96475#1413998, @APEC wrote:

In #96475#1413985, @Vyach wrote:

not possible in architecture modeling with hundreds small elements (objects) or even in one single mesh to do that...

Now you just do not have ability to use cheat.
Try to randomize positions a little, then…
Example b3.3:
untitled.blend
изображение.png

> In #96475#1413998, @APEC wrote: >> In #96475#1413985, @Vyach wrote: > not possible in architecture modeling with hundreds small elements (objects) or even in one single mesh to do that... Now you just do not have ability to use cheat. Try to randomize positions a little, then… Example b3.3: [untitled.blend](https://archive.blender.org/developer/F13470460/untitled.blend) ![изображение.png](https://archive.blender.org/developer/F13470464/изображение.png)
Germano Cavalcante commented 2022-09-30 15:25:33 +02:00
Member
Copy Link

Added subscribers: @Piergiorgio_PG, @mod_moder

Added subscribers: @Piergiorgio_PG, @mod_moder
Alaska commented 2022-12-07 04:53:11 +01:00
Member
Copy Link

Added subscriber: @kalugra23

Added subscriber: @kalugra23
Thomas Dinges added this to the 3.1 milestone 2023-02-08 15:52:44 +01:00
Gioxyer commented 2024-04-18 07:20:00 +02:00
Copy Link

One question, using Blender 3.0.1 can cause some issue for the redesign and new features of Geometry Nodes from Blender 4.1?

One question, using Blender 3.0.1 can cause some issue for the redesign and new features of Geometry Nodes from Blender 4.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
3.1
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
13 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#96475
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?