blender
/
blender
128
396
Fork 568
Code Issues 6.2k Pull Requests 750 Projects 19 Wiki Activity

Geometry Node: Changing modifier input values with python no cause update #87006

New Issue
Closed
opened 2021-03-29 05:12:59 +02:00 by yonghao lv · 60 comments
yonghao lv commented 2021-03-29 05:12:59 +02:00
Copy Link

System Information
Operating system: Windows-10-10.0.18362-SP0 64 Bits
Graphics card: GeForce RTX 2080 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.72

Blender Version
Broken: version: 2.93.0 Alpha, branch: master, commit date: 2021-03-27 14:01, hash: a9e7d503dd

Short description of error
Changing modifier input values with python no cause update.
By code:

bpy.data.objects["Cube"].modifiers["GeometryNodes"]["Input_1"][0] = 13.8

Value in modifier property was changed. User interface no updated before modifiers panel are not redrawn. Result of modifier didn't updated.

image.png

Exact steps for others to reproduce the error

  • Open attached file
  • Run the code bpy.data.objects["Cube"].modifiers["GeometryNodes"]["Input_7"] = 1.0 in the python console
    The modifier UI may change, but the Viewport does not.
    geom_node_py_bug.blend
**System Information** Operating system: Windows-10-10.0.18362-SP0 64 Bits Graphics card: GeForce RTX 2080 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.72 **Blender Version** Broken: version: 2.93.0 Alpha, branch: master, commit date: 2021-03-27 14:01, hash: `a9e7d503dd` **Short description of error** Changing modifier input values with python no cause update. By code: ``` bpy.data.objects["Cube"].modifiers["GeometryNodes"]["Input_1"][0] = 13.8 ``` Value in modifier property was changed. User interface no updated before modifiers panel are not redrawn. Result of modifier didn't updated. ![image.png](https://archive.blender.org/developer/F9912961/image.png) **Exact steps for others to reproduce the error** - Open attached file - Run the code `bpy.data.objects["Cube"].modifiers["GeometryNodes"]["Input_7"] = 1.0` in the python console The modifier UI may change, but the Viewport does not. [geom_node_py_bug.blend](https://archive.blender.org/developer/F9922079/geom_node_py_bug.blend)
yonghao lv commented 2021-03-29 05:12:59 +02:00
Author
Copy Link

Added subscriber: @1029910278

Added subscriber: @1029910278
blender-admin commented 2021-03-29 05:12:59 +02:00
Copy Link

#88545 was marked as duplicate of this issue

#88545 was marked as duplicate of this issue
blender-admin commented 2021-03-29 05:12:59 +02:00
Copy Link

#87125 was marked as duplicate of this issue

#87125 was marked as duplicate of this issue
Falk David commented 2021-03-29 10:07:36 +02:00
Member
Copy Link

Added subscriber: @filedescriptor

Added subscriber: @filedescriptor
Falk David commented 2021-03-29 10:07:36 +02:00
Member
Copy Link

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

Changed status from 'Needs Triage' to: 'Needs User Info'
Falk David commented 2021-03-29 10:07:36 +02:00
Member
Copy Link

@1029910278 Could you add the .blend test file to the report? That would be helpful. Thanks.

@1029910278 Could you add the `.blend` test file to the report? That would be helpful. Thanks.
yonghao lv commented 2021-03-31 14:03:45 +02:00
Author
Copy Link

just record a video for this error. You can see that both the cube and line is not active in viewport. And the cube's property disappear.
2021-03-31 19-58-52.mp4

just record a video for this error. You can see that both the cube and line is not active in viewport. And the cube's property disappear. [2021-03-31 19-58-52.mp4](https://archive.blender.org/developer/F9915769/2021-03-31_19-58-52.mp4)
Falk David commented 2021-04-02 17:39:41 +02:00
Member
Copy Link

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

Changed status from 'Needs User Info' to: 'Needs Triage'
Germano Cavalcante commented 2021-04-06 20:05:19 +02:00
Member
Copy Link

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

Changed status from 'Needs Triage' to: 'Confirmed'
Germano Cavalcante commented 2021-04-06 20:05:19 +02:00
Member
Copy Link

Added subscriber: @mano-wii

Added subscriber: @mano-wii
Germano Cavalcante commented 2021-04-07 16:23:43 +02:00
Member
Copy Link

Added subscriber: @Pasang

Added subscriber: @Pasang
Himanshi Kalra commented 2021-05-25 06:54:55 +02:00
Member
Copy Link

Added subscriber: @VDC

Added subscriber: @VDC
Jacques Lucke commented 2021-06-14 12:35:29 +02:00
Member
Copy Link

Added subscriber: @JacquesLucke

Added subscriber: @JacquesLucke
Jacques Lucke commented 2021-06-14 12:35:29 +02:00
Member
Copy Link

Think the problem here will also be fixed by D11572, once we found a good solution.

Think the problem here will also be fixed by [D11572](https://archive.blender.org/developer/D11572), once we found a good solution.
Miro Horváth commented 2021-06-15 11:37:51 +02:00
Copy Link

Added subscriber: @MiroHorvath

Added subscriber: @MiroHorvath
Peter Nebelong commented 2021-10-03 12:39:14 +02:00
Copy Link

Added subscriber: @petneb

Added subscriber: @petneb
yonghao lv commented 2021-10-12 19:02:03 +02:00
Author
Copy Link

Is there any progress on fixing this problem? Since the field system will not display the attribute, I have to stick to use the old nodes(The only way to control them is to acess the node tree)

Is there any progress on fixing this problem? Since the field system will not display the attribute, I have to stick to use the old nodes(The only way to control them is to acess the node tree)
Jeran commented 2022-02-04 23:49:56 +01:00
Copy Link

Added subscriber: @TheJeran

Added subscriber: @TheJeran
Jeran commented 2022-02-04 23:50:34 +01:00
Copy Link

Oh no this has been here almost a year?

Oh no this has been here almost a year?
Jacob Merrill commented 2022-02-05 00:18:19 +01:00
Copy Link

Added subscriber: @JacobMerrill-1

Added subscriber: @JacobMerrill-1
Jacob Merrill commented 2022-02-05 00:18:19 +01:00
Copy Link

does this require .update_tag() ?

does this require .update_tag() ?
Jacob Merrill commented 2022-02-05 00:20:14 +01:00
Copy Link

just tested

bpy.data.objects["Cube"].update_tag()

is all that is required*

just tested bpy.data.objects["Cube"].update_tag() is all that is required*
Jacob Merrill commented 2022-02-05 00:20:31 +01:00
Copy Link

I think this can be closed actually

2022-02-04 15-20-35.mp4

I think this can be closed actually [2022-02-04 15-20-35.mp4](https://archive.blender.org/developer/F12847103/2022-02-04_15-20-35.mp4)
Ray commented 2022-02-05 06:07:27 +01:00
Copy Link

In #87006#1301986, @JacobMerrill-1 wrote:
I think this can be closed actually

The value of Z displayed in the modifier panel seems unchanged?

> In #87006#1301986, @JacobMerrill-1 wrote: > I think this can be closed actually The value of Z displayed in the modifier panel seems unchanged?
Jeran commented 2022-02-05 13:00:54 +01:00
Copy Link

For me, update_tag() only works if the frame changes manually again. So when I render out an animation nothing happens.

edit:
bpy.data.objects[name].update_tag()
bpy.data.scenes['Scene'].frame_current = currentFrame+1

This works for me, but it's not really what I want.

For me, update_tag() only works if the frame changes manually again. So when I render out an animation nothing happens. edit: bpy.data.objects[name].update_tag() bpy.data.scenes['Scene'].frame_current = currentFrame+1 This works for me, but it's not really what I want.
Jacob Merrill commented 2022-02-05 17:08:07 +01:00
Copy Link

yeah I just noted that it appears to be disabled somehow from being used continuously :(

a work around is to use a driver and move a empty and use it's X Y and Z as drivers

false alarm* - I was editing slot 1 which is 'geometry'

I think the main issue is we should able to access these inputs by name*

object.modifiers['GeometryNodes'].input['Name'] = Value

yeah I just noted that it appears to be disabled somehow from being used continuously :( a work around is to use a driver and move a empty and use it's X Y and Z as drivers false alarm* - I was editing slot 1 which is 'geometry' I think the main issue is we should able to access these inputs by name* object.modifiers['GeometryNodes'].input['Name'] = Value
Aurelien Vaillant commented 2022-02-21 11:19:10 +01:00
Copy Link

Added subscriber: @stilobique

Added subscriber: @stilobique
Aurelien Vaillant commented 2022-02-21 11:26:35 +01:00
Copy Link

In #87006#1301986, @JacobMerrill-1 wrote:
I think this can be closed actually

2022-02-04 15-20-35.mp4

Work to me, not really sure about the 'update_tag' function ; I'm stay here to follow this ticket.

> In #87006#1301986, @JacobMerrill-1 wrote: > I think this can be closed actually > > [2022-02-04 15-20-35.mp4](https://archive.blender.org/developer/F12847103/2022-02-04_15-20-35.mp4) Work to me, not really sure about the 'update_tag' function ; I'm stay here to follow this ticket.
Arthur Blaquart commented 2022-11-15 16:36:48 +01:00
Copy Link

Added subscriber: @Human_Robot

Added subscriber: @Human_Robot
Arthur Blaquart commented 2022-11-15 16:36:48 +01:00
Copy Link

The update_tag() trick doesn't fully work. Yes it will update the modifier once but then it won't dynamically update after that. For example my geometry nodes take a collection as input to drive multiple Set Position. If I change the location of an object in the input collection after running the script that tells blender to use this collection as input, it won't update the geometry nodes output to match the change.

The update_tag() trick doesn't fully work. Yes it will update the modifier once but then it won't dynamically update after that. For example my geometry nodes take a collection as input to drive multiple Set Position. If I change the location of an object in the input collection after running the script that tells blender to use this collection as input, it won't update the geometry nodes output to match the change.
Arthur Blaquart commented 2022-11-15 16:39:42 +01:00
Copy Link

This comment was removed by @Human_Robot

*This comment was removed by @Human_Robot*
Arthur Blaquart commented 2022-11-15 16:40:53 +01:00
Copy Link

2022-11-15 16-40-27.mp4

[2022-11-15 16-40-27.mp4](https://archive.blender.org/developer/F13917972/2022-11-15_16-40-27.mp4)
Falk David commented 2022-11-15 22:18:23 +01:00
Member
Copy Link

Removed subscriber: @filedescriptor

Removed subscriber: @filedescriptor
cake lover commented 2022-11-19 21:33:33 +01:00
Copy Link

Added subscriber: @Cake-Lover

Added subscriber: @Cake-Lover
cake lover commented 2022-11-19 21:33:33 +01:00
Copy Link

This issue really needs to be fixed!

but meanwhile, you can use obj.data.update() after you've changed the modifier value to display the changes

This issue really needs to be fixed! but meanwhile, you can use `obj.data.update()` after you've changed the modifier value to display the changes
Arthur Blaquart commented 2022-11-22 16:08:53 +01:00
Copy Link

If you watch the video the issue is still the same with obj.data.update().

In my code, adding drop_shadow_obj.data.update() before or after or instead of drop_shadow_obj.update_tag() doesn't change anything.

If you watch the video the issue is still the same with obj.data.update(). In my code, adding drop_shadow_obj.data.update() before or after or instead of drop_shadow_obj.update_tag() doesn't change anything.
Alma Undun commented 2022-11-29 23:30:04 +01:00
Copy Link

Added subscriber: @TestPilot02

Added subscriber: @TestPilot02
Alma Undun commented 2022-11-29 23:30:04 +01:00
Copy Link

+1 for experiencing this problem

+1 for experiencing this problem
AiSatan commented 2022-12-02 08:12:13 +01:00
Copy Link

Added subscriber: @aisatan.ne

Added subscriber: @aisatan.ne
AiSatan commented 2022-12-02 08:12:13 +01:00
Copy Link

I noticed, if you set it with the type, for example "1.0" instead of just "1", and .data update after

bpy.context.object.modifiers["TestGNMod"]["Input_2"] = 55.0
bpy.context.object.data.update()

I noticed, if you set it with the type, for example "1.0" instead of just "1", and .data update after bpy.context.object.modifiers["TestGNMod"]["Input_2"] = 55.0 bpy.context.object.data.update()
Philipp Oeser commented 2022-12-02 09:20:52 +01:00
Member
Copy Link

Added subscribers: @dr.sybren, @lichtwerk

Added subscribers: @dr.sybren, @lichtwerk
Philipp Oeser commented 2022-12-02 09:20:52 +01:00
Member
Copy Link

Just noting that #63793 (When set value of "custom property" by python , driver not up-date correctly) (which seems to be the same underlying thing) was closed by @dr.sybren back then.

Just noting that #63793 (When set value of "custom property" by python , driver not up-date correctly) (which seems to be the same underlying thing) was closed by @dr.sybren back then.
Daniele De Luca commented 2022-12-06 12:40:39 +01:00
Copy Link

Added subscriber: @Sparazza

Added subscriber: @Sparazza
Benjamin Sauder commented 2023-01-15 16:03:48 +01:00
Copy Link

Added subscriber: @kioku

Added subscriber: @kioku
CybranM commented 2023-01-26 19:32:41 +01:00
Copy Link

Added subscriber: @IihT2cWA9xiP30BsYphz3EiEISNoScoe

Added subscriber: @IihT2cWA9xiP30BsYphz3EiEISNoScoe
CybranM commented 2023-01-26 19:35:43 +01:00
Copy Link

bpy.context.object.data.update()

This doesnt work with curve objects since their data doesnt have an update function :(

> bpy.context.object.data.update() This doesnt work with curve objects since their data doesnt have an update function :(
Hans Goudey added
Module
Nodes & Physics
 and removed
Module
Animation & Rigging
 labels 2023-02-08 14:33:40 +01:00
Erik Abrahamsson commented 2023-02-08 14:34:19 +01:00
Member
Copy Link

I think it would make sense to have it the other way around. Update is always made like in other modifiers, but with the possibility to delay the update if multiple properties are to be modified.

Maybe one solution could be to have a defer-function like I've noticed while working on Windows apps, used like this:

using (dataView.DeferRefresh())
{
    // Make multiple changes to the data here
}

but in Python something like:

with node.defer_update():
    node.property1 += 1
    node.property2 -= 1

would first modify both parameters, then update.

I think it would make sense to have it the other way around. Update is always made like in other modifiers, but with the possibility to delay the update if multiple properties are to be modified. Maybe one solution could be to have a defer-function like I've noticed while working on Windows apps, used like this: ``` using (dataView.DeferRefresh()) { // Make multiple changes to the data here } ``` but in Python something like: ``` with node.defer_update(): node.property1 += 1 node.property2 -= 1 ``` would first modify both parameters, then update.
Jacques Lucke commented 2023-02-08 16:07:05 +01:00
Member
Copy Link

@erik85 While I'm not generally against deferring updates, it something that has to be done with great care because it's a bit against current principles of the RNA/Python API. In this specific case I'm not convinced that it is worth it.

I didn't look into this problem for quite some time now, but please make sure you've seen the discussion in https://archive.blender.org/developer/D11572.

@erik85 While I'm not generally against deferring updates, it something that has to be done with great care because it's a bit against current principles of the RNA/Python API. In this specific case I'm not convinced that it is worth it. I didn't look into this problem for quite some time now, but please make sure you've seen the discussion in https://archive.blender.org/developer/D11572.
Philipp Oeser removed the
Interest
Nodes & Physics
 label 2023-02-10 08:45:00 +01:00
Sybren A. Stüvel commented 2023-02-10 12:41:49 +01:00
Member
Copy Link

Short description of error

This report doesn't even describe what's going wrong.+

Can we at least get a description of what we're discussing here?

Ok, there's a video that explains quite a bit more. For the next time, please update the description and put such critical there.

> Short description of error ~~This report doesn't even describe what's going wrong.~~+ ~~Can we at least get a description of what we're discussing here?~~ Ok, there's a video that explains quite a bit more. For the next time, please update the description and put such critical there.
Iliya Katushenock changed title from geo nodes not update immediately with python to Geometry Node: Changing modifier input values with python no cause update 2023-02-10 13:45:56 +01:00
Jacob Merrill commented 2023-02-14 19:28:24 +01:00
Copy Link

if we try and change values of geometry node inputs, we can't continuously change the inputs only some of the input values appear to be evaluated / trigger depsgraph to remake the evaluated data.

in upbge I had to move to using drivers as inputs as object.modifiers['GoemetryNodes'].inputs['input_2'] proved unreliable

if we try and change values of geometry node inputs, we can't continuously change the inputs only some of the input values appear to be evaluated / trigger depsgraph to remake the evaluated data. in upbge I had to move to using drivers as inputs as object.modifiers['GoemetryNodes'].inputs['input_2'] proved unreliable
Dominique-Gantois commented 2023-04-14 22:12:39 +02:00
Copy Link

Is this the same problem?? Blender 3.4
Switching between NodeTrees, the Input Attribute Toggles in the Geo-Node modifier panel get set to their default values of 1.0000. They somehow forget the assigned Input. In my case, see the two images; I have my two vertex selections: named 'Scatter' for a Density Factor and 'WPaint2' for a Value, they changed back to their default 1.0000 values after browsing another node tree . This can easily be duplicated, with either input (happens not only with vertex selections).

Is this the same problem?? Blender 3.4 Switching between NodeTrees, the Input Attribute Toggles in the Geo-Node modifier panel get set to their default values of 1.0000. They somehow forget the assigned Input. In my case, see the two images; I have my two vertex selections: named 'Scatter' for a Density Factor and 'WPaint2' for a Value, they changed back to their default 1.0000 values after browsing another node tree . This can easily be duplicated, with either input (happens not only with vertex selections).
OK.png
72 KiB
After.png
71 KiB
OK.png After.png
Iliya Katushenock commented 2023-05-01 12:22:30 +02:00
Member
Copy Link

cc rna_access.cc:

    /* Disclaimer: this logic is not applied consistently, causing some confusing behavior.
     *
     * - When animated (which skips update functions).
     * - When ID-properties are edited via Python (since RNA properties aren't used in this case).
     *
     * Adding updates will add a lot of overhead in the case of animation.
     * For Python it may cause unexpected slow-downs for developers using ID-properties
     * for data storage. Further, the root ID isn't available with nested data-structures.
     *
     * So editing custom properties only causes updates in the UI,
     * keep this exception because it happens to be useful for driving settings.
     * Python developers on the other hand will need to manually 'update_tag', see: #74000. */
cc `rna_access.cc`: ```Cpp /* Disclaimer: this logic is not applied consistently, causing some confusing behavior. * * - When animated (which skips update functions). * - When ID-properties are edited via Python (since RNA properties aren't used in this case). * * Adding updates will add a lot of overhead in the case of animation. * For Python it may cause unexpected slow-downs for developers using ID-properties * for data storage. Further, the root ID isn't available with nested data-structures. * * So editing custom properties only causes updates in the UI, * keep this exception because it happens to be useful for driving settings. * Python developers on the other hand will need to manually 'update_tag', see: #74000. */ ```
Andrej commented 2023-06-24 16:48:38 +02:00
Contributor
Copy Link

So what's the more preferred workaround for now?
I've found that either object.updat_tag() or object.data.update() works. Is there any difference between them?

Attached some quick example for tests.

So what's the more preferred workaround for now? I've found that either `object.updat_tag()` or `object.data.update()` works. Is there any difference between them? Attached some quick example for tests.
geonodes_change_prop_from_python.blend
939 KiB
Nisim Joseph commented 2023-12-23 13:29:52 +01:00
Copy Link

I also have the same issue.
Using Blender v4 none of the above solutions work. I found a solution that works by running 2 actions:

  1. run a Python script that does an actual change in the Blender file and use the bpy.ops.wm.save_mainfile() to save the file.
  2. run the rendering command again, without the Python script param and the file update and all working.

Because of the non-update action, I had all the Geometry Nodes updated, but the Cloth modifier, that came after, doesn't compute the new geometry animation.

To solve this problem, I added remove all bake commands and re-bake the file.

    bpy.ops.ptcache.free_bake_all()
    bpy.ops.ptcache.bake_all(bake=True)

also, I enabled the bpy.context.object.modifiers["Cloth"].point_cache.use_disk_cache = True for my cloth modifier, and done it before the bake.
I see all the animation working well.

I also have the same issue. Using Blender v4 none of the above solutions work. I found a solution that works by running 2 actions: 1. run a Python script that does an actual change in the Blender file and use the `bpy.ops.wm.save_mainfile()` to save the file. 2. run the rendering command again, without the Python script param and the file update and all working. Because of the non-update action, I had all the Geometry Nodes updated, but the Cloth modifier, that came after, doesn't compute the new geometry animation. To solve this problem, I added remove all bake commands and re-bake the file. ``` bpy.ops.ptcache.free_bake_all() bpy.ops.ptcache.bake_all(bake=True) ``` also, I enabled the `bpy.context.object.modifiers["Cloth"].point_cache.use_disk_cache = True` for my cloth modifier, and done it before the bake. I see all the animation working well.
😕 1
Edward-Savage commented 2024-03-04 21:54:13 +01:00
Copy Link

i found that turning off and on the viewport visibility will also refresh it, and cause the changes to appear

bpy.ops.object.toggle_apply_modifiers_view()
bpy.ops.object.toggle_apply_modifiers_view()

you can do it manually, or use this code to do it automatically

i found that turning off and on the viewport visibility will also refresh it, and cause the changes to appear ``` bpy.ops.object.toggle_apply_modifiers_view() bpy.ops.object.toggle_apply_modifiers_view() ``` you can do it manually, or use this code to do it automatically
MACHIN3 commented 2024-03-07 00:36:14 +01:00
Copy Link

Just run mod.node_group.interface_update(context)

Takes care of this issue where the displayed unit is lost too: https://www.youtube.com/watch?v=WMwDZ0NFZ08

I do mode changes in the video bc it's faster then obj.update_tag(), but interface_update() actually gets rid of that need too.

Just run `mod.node_group.interface_update(context)` Takes care of this issue where the displayed unit is lost too: https://www.youtube.com/watch?v=WMwDZ0NFZ08 I do mode changes in the video bc it's faster then `obj.update_tag()`, but `interface_update()` actually gets rid of that need too.
MACHIN3 commented 2024-03-07 20:49:45 +01:00
Copy Link

Well, you need to create that reference to your mod of course.

mod = obj.modifiers.get('Smooth by Angle', None)

if mod:
    mod.node_group.interface_update(context)

or

for mod in obj.modifiers:
    if mod.type == 'NODES' and mod.node_group and mod.node_group.name == 'Smooth by Angle':
        mod.node_group.interface_update(context)
Well, you need to create that reference to your mod of course. ``` mod = obj.modifiers.get('Smooth by Angle', None) if mod: mod.node_group.interface_update(context) ``` or ``` for mod in obj.modifiers: if mod.type == 'NODES' and mod.node_group and mod.node_group.name == 'Smooth by Angle': mod.node_group.interface_update(context) ```
Edward-Savage commented 2024-03-08 10:00:02 +01:00
Copy Link

@MACHIN3 thanks, im gonna delete this soon so that this page is easier to read

@MACHIN3 thanks, im gonna delete this soon so that this page is easier to read
yonghao lv commented 2024-03-11 07:11:25 +01:00
Author
Copy Link

@MACHIN3 seem this new api work.

@MACHIN3 seem this new api work.
👍 1
Sybren A. Stüvel commented 2024-03-18 12:31:52 +01:00
Member
Copy Link

seem this new api work.

In that case I'll close this report. Thanks for the solution @MACHIN3 !

> seem this new api work. In that case I'll close this report. Thanks for [the solution](https://projects.blender.org/blender/blender/issues/87006#issuecomment-1140113) @MACHIN3 !
👍 1
Blender Bot added
Status
Archived
 and removed
Status
Confirmed
 labels 2024-03-18 12:32:30 +01:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
main
brush-assets-project
blender-v4.1-release
blender-v3.3-release
blender-v3.6-release
universal-scene-description
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
28 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#87006
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?