Hair Dynamics: entering particle edit mode with baked cache crashes blender #59583

New Issue

Robert Guetzkow · 2018-12-18T20:47:51+01:00

Robert Guetzkow commented

2018-12-18 20:47:51 +01:00

System Information
Operating system: Windows 10 64-Bit
Graphics card: Nvidia GeForce GTX 1080Ti

Blender Version
Broken: cef41d0144

Short description of error
Switching to particle edit mode on an object with baked hair dynamics crashes blender. I'm not sure when or why you'd actually want to do that, but it shouldn't cause a crash.

Exact steps for others to reproduce the error
Open the provided .blend file and switch to particle edit mode. Otherwise you can recreate the MWE:

Add a particle system to the an object
Activate hair dynamics
Bake the physics
Switch to particle edit mode

mwe.blend

**System Information** Operating system: Windows 10 64-Bit Graphics card: Nvidia GeForce GTX 1080Ti **Blender Version** Broken: cef41d0144e **Short description of error** Switching to particle edit mode on an object with baked hair dynamics crashes blender. I'm not sure when or why you'd actually want to do that, but it shouldn't cause a crash. **Exact steps for others to reproduce the error** Open the provided .blend file and switch to particle edit mode. Otherwise you can recreate the MWE: - Add a particle system to the an object - Activate hair dynamics - Bake the physics - Switch to particle edit mode [mwe.blend](https://archive.blender.org/developer/F5995953/mwe.blend)

Robert Guetzkow commented

2018-12-18 20:47:51 +01:00

Added subscriber: @rjg

blender-admin commented

2018-12-18 20:47:51 +01:00

#62948 was marked as duplicate of this issue

Sebastian Parborg commented

2018-12-19 12:13:55 +01:00

Added subscribers: @dfelinto, @ZedDB

Dalai Felinto was assigned by Sebastian Parborg

2018-12-19 12:13:55 +01:00

Sebastian Parborg commented

2018-12-19 12:13:55 +01:00

Backtrace:

Thread 1 "blender" received signal SIGSEGV, Segmentation fault.
0x0000555557fdd280 in psys_copy_particles (psys_dst=0x0, psys_src=0x0)
    at /home/zed/programmering/blender_master/blender/source/blender/blenkernel/intern/particle.c:668
668		if (psys_dst->particles != psys_src->particles) {
(gdb) bt
#0  0x0000555557fdd280 in psys_copy_particles (psys_dst=0x0, psys_src=0x0)
    at /home/zed/programmering/blender_master/blender/source/blender/blenkernel/intern/particle.c:668
#1  0x000055555762a84b in PE_create_particle_edit (depsgraph=0x7fffdc83ca08, scene=0x7fffeab73008, ob=0x7fffefbe9a08, cache=0x7fffd4fe7a08, psys=0x0)
    at /home/zed/programmering/blender_master/blender/source/blender/editors/physics/particle_edit.c:4703
#2  0x000055555761aea6 in pe_get_current (depsgraph=0x7fffdc83ca08, scene=0x7fffeab73008, ob=0x7fffefbe9a08, create=1)
    at /home/zed/programmering/blender_master/blender/source/blender/editors/physics/particle_edit.c:289
#3  0x000055555761b2ff in PE_create_current (depsgraph=0x7fffdc83ca08, scene=0x7fffeab73008, ob=0x7fffefbe9a08)
    at /home/zed/programmering/blender_master/blender/source/blender/editors/physics/particle_edit.c:353
#4  0x000055555762af4f in particle_edit_toggle_exec (C=0x7fffefc30288, op=0x7fffd23fd188)
    at /home/zed/programmering/blender_master/blender/source/blender/editors/physics/particle_edit.c:4833
#5  0x000055555704e00d in wm_operator_invoke (C=0x7fffefc30288, ot=0x7fffea958b48, event=0x0, properties=0x0, reports=0x0, poll_only=false,
    use_last_properties=true) at /home/zed/programmering/blender_master/blender/source/blender/windowmanager/intern/wm_event_system.c:1337
#6  0x000055555704e6aa in wm_operator_call_internal (C=0x7fffefc30288, ot=0x7fffea958b48, properties=0x0, reports=0x0, context=7, poll_only=false, event=0x0)
    at /home/zed/programmering/blender_master/blender/source/blender/windowmanager/intern/wm_event_system.c:1534
#7  0x000055555704e8cd in WM_operator_name_call_ptr (C=0x7fffefc30288, ot=0x7fffea958b48, context=7, properties=0x0)
    at /home/zed/programmering/blender_master/blender/source/blender/windowmanager/intern/wm_event_system.c:1582
#8  0x0000555557559742 in ED_object_mode_toggle (C=0x7fffefc30288, mode=OB_MODE_PARTICLE_EDIT)
    at /home/zed/programmering/blender_master/blender/source/blender/editors/object/object_modes.c:174
#9  0x00005555575582c3 in object_mode_set_exec (C=0x7fffefc30288, op=0x7fffd23fe8c8)
    at /home/zed/programmering/blender_master/blender/source/blender/editors/object/object_edit.c:1691
#10 0x000055555704e00d in wm_operator_invoke (C=0x7fffefc30288, ot=0x7fffea8de9c8, event=0x7fffe8e22c88, properties=0x7fffffffd660, reports=0x0,
    poll_only=false, use_last_properties=true) at /home/zed/programmering/blender_master/blender/source/blender/windowmanager/intern/wm_event_system.c:1337
#11 0x000055555704e6aa in wm_operator_call_internal (C=0x7fffefc30288, ot=0x7fffea8de9c8, properties=0x7fffffffd660, reports=0x0, context=1, poll_only=false,
    event=0x7fffe8e22c88) at /home/zed/programmering/blender_master/blender/source/blender/windowmanager/intern/wm_event_system.c:1534
#12 0x000055555704e8cd in WM_operator_name_call_ptr (C=0x7fffefc30288, ot=0x7fffea8de9c8, context=1, properties=0x7fffffffd660)
    at /home/zed/programmering/blender_master/blender/source/blender/windowmanager/intern/wm_event_system.c:1582
#13 0x0000555557386394 in ui_apply_but_funcs_after (C=0x7fffefc30288)
    at /home/zed/programmering/blender_master/blender/source/blender/editors/interface/interface_handlers.c:769
#14 0x000055555739eee8 in ui_handler_region_menu (C=0x7fffefc30288, event=0x7fffd4dd4b08, UNUSED_userdata=0x7fffd4f40508)
    at /home/zed/programmering/blender_master/blender/source/blender/editors/interface/interface_handlers.c:9801
#15 0x000055555704bd6e in wm_handler_ui_call (C=0x7fffefc30288, handler=0x7fffd23fe988, event=0x7fffd4dd4b08, always_pass=0)
    at /home/zed/programmering/blender_master/blender/source/blender/windowmanager/intern/wm_event_system.c:573
#16 0x0000555557050938 in wm_handlers_do_intern (C=0x7fffefc30288, event=0x7fffd4dd4b08, handlers=0x7fffeaacb9a0)
    at /home/zed/programmering/blender_master/blender/source/blender/windowmanager/intern/wm_event_system.c:2374
#17 0x0000555557051301 in wm_handlers_do (C=0x7fffefc30288, event=0x7fffd4dd4b08, handlers=0x7fffeaacb9a0)
    at /home/zed/programmering/blender_master/blender/source/blender/windowmanager/intern/wm_event_system.c:2607
#18 0x00005555570526b8 in wm_event_do_handlers (C=0x7fffefc30288)
    at /home/zed/programmering/blender_master/blender/source/blender/windowmanager/intern/wm_event_system.c:2997
- 19 0x0000555557047429 in WM_main (C=0x7fffefc30288) at /home/zed/programmering/blender_master/blender/source/blender/windowmanager/intern/wm.c:427
- 20 0x0000555557041d8e in main (argc=1, argv=0x7fffffffdd28) at /home/zed/programmering/blender_master/blender/source/creator/creator.c:521

@dfelinto I think you worked with the caching system before? If not, feel free to reassign.

Backtrace: ``` Thread 1 "blender" received signal SIGSEGV, Segmentation fault. 0x0000555557fdd280 in psys_copy_particles (psys_dst=0x0, psys_src=0x0) at /home/zed/programmering/blender_master/blender/source/blender/blenkernel/intern/particle.c:668 668 if (psys_dst->particles != psys_src->particles) { (gdb) bt #0 0x0000555557fdd280 in psys_copy_particles (psys_dst=0x0, psys_src=0x0) at /home/zed/programmering/blender_master/blender/source/blender/blenkernel/intern/particle.c:668 #1 0x000055555762a84b in PE_create_particle_edit (depsgraph=0x7fffdc83ca08, scene=0x7fffeab73008, ob=0x7fffefbe9a08, cache=0x7fffd4fe7a08, psys=0x0) at /home/zed/programmering/blender_master/blender/source/blender/editors/physics/particle_edit.c:4703 #2 0x000055555761aea6 in pe_get_current (depsgraph=0x7fffdc83ca08, scene=0x7fffeab73008, ob=0x7fffefbe9a08, create=1) at /home/zed/programmering/blender_master/blender/source/blender/editors/physics/particle_edit.c:289 #3 0x000055555761b2ff in PE_create_current (depsgraph=0x7fffdc83ca08, scene=0x7fffeab73008, ob=0x7fffefbe9a08) at /home/zed/programmering/blender_master/blender/source/blender/editors/physics/particle_edit.c:353 #4 0x000055555762af4f in particle_edit_toggle_exec (C=0x7fffefc30288, op=0x7fffd23fd188) at /home/zed/programmering/blender_master/blender/source/blender/editors/physics/particle_edit.c:4833 #5 0x000055555704e00d in wm_operator_invoke (C=0x7fffefc30288, ot=0x7fffea958b48, event=0x0, properties=0x0, reports=0x0, poll_only=false, use_last_properties=true) at /home/zed/programmering/blender_master/blender/source/blender/windowmanager/intern/wm_event_system.c:1337 #6 0x000055555704e6aa in wm_operator_call_internal (C=0x7fffefc30288, ot=0x7fffea958b48, properties=0x0, reports=0x0, context=7, poll_only=false, event=0x0) at /home/zed/programmering/blender_master/blender/source/blender/windowmanager/intern/wm_event_system.c:1534 #7 0x000055555704e8cd in WM_operator_name_call_ptr (C=0x7fffefc30288, ot=0x7fffea958b48, context=7, properties=0x0) at /home/zed/programmering/blender_master/blender/source/blender/windowmanager/intern/wm_event_system.c:1582 #8 0x0000555557559742 in ED_object_mode_toggle (C=0x7fffefc30288, mode=OB_MODE_PARTICLE_EDIT) at /home/zed/programmering/blender_master/blender/source/blender/editors/object/object_modes.c:174 #9 0x00005555575582c3 in object_mode_set_exec (C=0x7fffefc30288, op=0x7fffd23fe8c8) at /home/zed/programmering/blender_master/blender/source/blender/editors/object/object_edit.c:1691 #10 0x000055555704e00d in wm_operator_invoke (C=0x7fffefc30288, ot=0x7fffea8de9c8, event=0x7fffe8e22c88, properties=0x7fffffffd660, reports=0x0, poll_only=false, use_last_properties=true) at /home/zed/programmering/blender_master/blender/source/blender/windowmanager/intern/wm_event_system.c:1337 #11 0x000055555704e6aa in wm_operator_call_internal (C=0x7fffefc30288, ot=0x7fffea8de9c8, properties=0x7fffffffd660, reports=0x0, context=1, poll_only=false, event=0x7fffe8e22c88) at /home/zed/programmering/blender_master/blender/source/blender/windowmanager/intern/wm_event_system.c:1534 #12 0x000055555704e8cd in WM_operator_name_call_ptr (C=0x7fffefc30288, ot=0x7fffea8de9c8, context=1, properties=0x7fffffffd660) at /home/zed/programmering/blender_master/blender/source/blender/windowmanager/intern/wm_event_system.c:1582 #13 0x0000555557386394 in ui_apply_but_funcs_after (C=0x7fffefc30288) at /home/zed/programmering/blender_master/blender/source/blender/editors/interface/interface_handlers.c:769 #14 0x000055555739eee8 in ui_handler_region_menu (C=0x7fffefc30288, event=0x7fffd4dd4b08, UNUSED_userdata=0x7fffd4f40508) at /home/zed/programmering/blender_master/blender/source/blender/editors/interface/interface_handlers.c:9801 #15 0x000055555704bd6e in wm_handler_ui_call (C=0x7fffefc30288, handler=0x7fffd23fe988, event=0x7fffd4dd4b08, always_pass=0) at /home/zed/programmering/blender_master/blender/source/blender/windowmanager/intern/wm_event_system.c:573 #16 0x0000555557050938 in wm_handlers_do_intern (C=0x7fffefc30288, event=0x7fffd4dd4b08, handlers=0x7fffeaacb9a0) at /home/zed/programmering/blender_master/blender/source/blender/windowmanager/intern/wm_event_system.c:2374 #17 0x0000555557051301 in wm_handlers_do (C=0x7fffefc30288, event=0x7fffd4dd4b08, handlers=0x7fffeaacb9a0) at /home/zed/programmering/blender_master/blender/source/blender/windowmanager/intern/wm_event_system.c:2607 #18 0x00005555570526b8 in wm_event_do_handlers (C=0x7fffefc30288) at /home/zed/programmering/blender_master/blender/source/blender/windowmanager/intern/wm_event_system.c:2997 - 19 0x0000555557047429 in WM_main (C=0x7fffefc30288) at /home/zed/programmering/blender_master/blender/source/blender/windowmanager/intern/wm.c:427 - 20 0x0000555557041d8e in main (argc=1, argv=0x7fffffffdd28) at /home/zed/programmering/blender_master/blender/source/creator/creator.c:521 ``` @dfelinto I think you worked with the caching system before? If not, feel free to reassign.

Dalai Felinto commented

2018-12-19 12:35:19 +01:00

Added subscriber: @Sergey

Dalai Felinto commented

2018-12-19 12:35:19 +01:00

Not really, and @Sergey is the one who worked the most on particles in 2.80. Anyways, later this week I can dig further and try to pinpoint the issue or even fix it.

Brecht Van Lommel commented

2019-03-26 14:16:32 +01:00

Added subscribers: @gabe2252, @grosgood, @nacioss

Philipp Oeser changed title from ~~Particle edit mode on object with baked hair dynamics crashes blender~~ to Hair Dynamics: entering particle edit mode with baked cache crashes blender

2019-09-04 20:20:48 +02:00

Dalai Felinto was unassigned by Philipp Oeser

2019-09-04 20:20:48 +02:00

Garry R. Osgood commented

2019-11-11 14:59:34 +01:00

Added subscribers: @lichtwerk, @brecht

Garry R. Osgood commented

2019-11-11 14:59:34 +01:00

@lichtwerk
TL;DR:
A minor oversight, methinks, but please consider updating e02ecd599b to cover the possibility of ##edit->psys## being NULL, which can be the case. Perhaps use the standard sanity check common in the immediate vicinity of this code path:

 [1597]/* Only do this for emitter particles because drawing PE_FADE_TIME is not respected in 2.8 yet
 [1598] * and flagging with PEK_HIDE will prevent selection. This might get restored once this is
 [1599] * supported in drawing (but doesn't make much sense for hair anyways). */
 [1600] if (edit->psys) {
 [1601]   if (edit->psys->part->type == PART_EMITTER) {
 [1602]     PE_hide_keys_time(scene, edit, CFRA);
 [1603]   }
 [1604] }

T59583_fix.txt
Too Long To Read Stuff:

@brecht addressed the underlying cause of the stack dump reported by @ZedDB on 12-December-2018 with 5ac7675f4c on 16-April-2019 to address #62849, fixing this bug as well - an unnoticed duplicate, I gather - so missing the occasion to close this bug along with that.

Alas, in addressing #70259, trust was placed in the 24x7 existence of a ##ParticleSystem *## pointer, giving rise to this new, improved backtrace:
T59583_backtrace.txt
You see, no doubt, that this suggestion is more expedient than inventive, just to prevent the OS from sending a SIGSEGV lightning bolt our way - which hurts and upsets people. With this suggestion in play, the user can enter a particle editing session and do ... what? I don't know. Every guide hair is baked, frozen, invisible. There is nothing sensible to do in ParticleEdit for baked hair particles here in the 2.8x series AFAIK. Have to delete the bake first.
In any case, if this suggestion plays out, perhaps this bug can be closed now for real.

Even More Too Long To Read Stuff Because It's Ancient History
You may recall that in the 2.79 era, entering a particle edit session with a baked hair did not lead to a dead end. In that era, entering a particle edit session with baked hair allowed one to edit the hair key time histories instead.

Shades of Marcel Duchamp's Nude Descending a Staircase . The path that a hair key travels through time can itself be treated as a "hair", using the same editing tools. Why would anyone want to rewrite the history of a hair key? Well - why not?!? One could make a hair thrash around in really cool, geeky ways. Alas, the 2.8xx absence of editing the baked time series of hair keys was noted in #53780. I bring this up because the Fade Time checkbox allowed one to "fade away" the time series after so many frames from the initial animation - necessary, because it doesn't take too many keys before an absolute sphagetti mess of key histories shows up. This, I think, is the context that makes Fade Time sensible in the case of hair editing.

Very much appreciate your efforts in cleaning up this ancient hair particle code and keeping it stumbling along, more or less, until the Brand New Particle System Arrives!!! Take care.

Addenda
All of this with respect to Blender 2.82 (sub 1) (hash 19c44ae087 built 2019-11-11 11:37:09)
solohair_T59583.blend
Triggers #59583 in its current form.

Open the file.
Switch from Object to Particle Edit
Back trace should be the same as T59583_backtrace.txt

@lichtwerk **TL;DR:** A minor oversight, methinks, but please consider updating e02ecd599b to cover the possibility of ##edit->psys## being NULL, which can be the case. Perhaps use the standard sanity check common in the immediate vicinity of this code path: ``` [1597]/* Only do this for emitter particles because drawing PE_FADE_TIME is not respected in 2.8 yet [1598] * and flagging with PEK_HIDE will prevent selection. This might get restored once this is [1599] * supported in drawing (but doesn't make much sense for hair anyways). */ [1600] if (edit->psys) { [1601] if (edit->psys->part->type == PART_EMITTER) { [1602] PE_hide_keys_time(scene, edit, CFRA); [1603] } [1604] } ``` [T59583_fix.txt](https://archive.blender.org/developer/F8032618/T59583_fix.txt) **Too Long To Read Stuff:** @brecht addressed the underlying cause of the stack dump reported by @ZedDB on 12-December-2018 with 5ac7675f4c on 16-April-2019 to address #62849, fixing this bug as well - an unnoticed duplicate, I gather - so missing the occasion to close this bug along with that. Alas, in addressing #70259, trust was placed in the 24x7 existence of a ##ParticleSystem *## pointer, giving rise to this new, improved backtrace: [T59583_backtrace.txt](https://archive.blender.org/developer/F8032427/T59583_backtrace.txt) You see, no doubt, that this suggestion is more expedient than inventive, just to prevent the OS from sending a SIGSEGV lightning bolt our way - which hurts and upsets people. With this suggestion in play, the user can enter a particle editing session and do ... what? I don't know. Every guide hair is baked, frozen, invisible. There is nothing sensible to do in ParticleEdit for baked hair particles here in the 2.8x series AFAIK. Have to delete the bake first. In any case, if this suggestion plays out, perhaps this bug can be closed now for real. **Even More Too Long To Read Stuff Because It's Ancient History** You may recall that in the 2.79 era, entering a particle edit session with a baked hair did not lead to a dead end. In that era, entering a particle edit session with baked hair allowed one to edit the *hair key time histories* instead. ![edit_bake_279.png](https://archive.blender.org/developer/F8032475/edit_bake_279.png) Shades of Marcel Duchamp's [Nude Descending a Staircase ](https://www.philamuseum.org/collections/permanent/51449.html). The path that a hair key travels through time can itself be treated as a "hair", using the same editing tools. Why would anyone want to rewrite the history of a hair key? Well - why not?!? One could make a hair thrash around in really cool, geeky ways. Alas, the 2.8xx absence of editing the baked time series of hair keys was noted in #53780. I bring this up because the Fade Time checkbox allowed one to "fade away" the time series after so many frames from the initial animation - necessary, because it doesn't take too many keys before an absolute sphagetti mess of key histories shows up. This, I think, is the context that makes Fade Time sensible in the case of hair editing. ![edit_bakefade_279.png](https://archive.blender.org/developer/F8032502/edit_bakefade_279.png) Very much appreciate your efforts in cleaning up this ancient hair particle code and keeping it stumbling along, more or less, until the Brand New Particle System Arrives!!! Take care. **Addenda** All of this with respect to Blender 2.82 (sub 1) (hash 19c44ae0870b built 2019-11-11 11:37:09) [solohair_T59583.blend](https://archive.blender.org/developer/F8032516/solohair_T59583.blend) Triggers #59583 in its current form. 1. Open the file. 2. Switch from Object to Particle Edit 3. Back trace should be the same as **T59583_backtrace.txt**

Philipp Oeser self-assigned this 2019-11-11 15:27:13 +01:00

Philipp Oeser commented

2019-11-11 15:27:13 +01:00

Can confirm the new advent of the issue caused by unthoughtfully letting e02ecd599b act on non-existing psys.
[ and even dropping a comment there that is debatable :) ]
Appreciate your efforts in tracking down the stumbling blocks here!

note we are still entering the assert realm, even if we fix the above (but this is an old friend, we've seen it in #62893, #64843 -- so this is on another page...)

BLI_assert failed: /blender/draw/intern/draw_cache_impl_particles.c:1510, particle_batch_cache_ensure_edit_pos_and_seg(), at '!"Hairs are not in edit mode!"'

Can confirm the new advent of the issue caused by unthoughtfully letting e02ecd599b act on non-existing psys. [ and even dropping a comment there that is debatable :) ] Appreciate your efforts in tracking down the stumbling blocks here! note we are still entering the assert realm, even if we fix the above (but this is an old friend, we've seen it in #62893, #64843 -- so this is on another page...) ``` BLI_assert failed: /blender/draw/intern/draw_cache_impl_particles.c:1510, particle_batch_cache_ensure_edit_pos_and_seg(), at '!"Hairs are not in edit mode!"' ```

Marco commented

2019-11-11 17:41:22 +01:00

Removed subscriber: @nacioss

Garry R. Osgood commented

2019-11-11 19:40:37 +01:00

Added subscriber: @zeauro

Garry R. Osgood commented

2019-11-11 19:40:37 +01:00

Yes. Confirm that ##assert()## with a debug build. The assert has it's heart in the right place. There is nothing actually in the line of baked hair particles to edit in 2.8x. Ideally, in the presence of baked hair dynamics, I shouldn't even have the ParticleEdit mode available to me. It should stay off the menu until such time as the bake has been dropped. (but that is more than a few lines fix). I think in #53780 @zeauro raised a good point: neat, geeky trick aside, how useful is it to edit particle key histories? Eh - not sure on that one.

Yes. Confirm that ##assert()## with a debug build. The assert has it's heart in the right place. There is nothing actually in the line of baked hair particles to edit in 2.8x. Ideally, in the presence of baked hair dynamics, I shouldn't even have the ParticleEdit mode available to me. It should stay off the menu until such time as the bake has been dropped. (but that is more than a few lines fix). I think in #53780 @zeauro raised a good point: neat, geeky trick aside, how *useful* is it to edit particle key histories? Eh - not sure on that one.

Philipp Oeser was unassigned by Dalai Felinto

2019-12-23 16:35:36 +01:00

blender-admin commented

2020-01-08 13:11:18 +01:00

This issue was referenced by 75f82d28e3

This issue was referenced by 75f82d28e38f2bcfa9a261a39bbc4da82c65e7d3

Philipp Oeser commented

2020-01-08 13:39:19 +01:00

Changed status from 'Confirmed' to: 'Resolved'

Philipp Oeser closed this issue

2020-01-08 13:39:19 +01:00

Philipp Oeser self-assigned this 2020-01-08 13:39:19 +01:00

ronan ducluzeau commented

2020-01-19 18:12:15 +01:00

how useful is it to edit particle key histories?

The idea was to have an extra tweaking step to polish things.
It was really complicated to understand what will be the result for hair. But for emitter particles that could be rendered as growing paths : it was relevant.

It looks like entering Particle Edit mode is no more crashing. But if somebody goes into Options panel, Viewport Display subpanel and click on Particles option, there is still a crash.
It would probably be more frank to remove ability to enter into Particle Edit mode of a baked system.
Anyways, there is currently nothing visible, nothing to work on. There is no reason to let access to the mode, if feature is not supported.

> how useful is it to edit particle key histories? The idea was to have an extra tweaking step to polish things. It was really complicated to understand what will be the result for hair. But for emitter particles that could be rendered as growing paths : it was relevant. It looks like entering Particle Edit mode is no more crashing. But if somebody goes into Options panel, Viewport Display subpanel and click on Particles option, there is still a crash. It would probably be more frank to remove ability to enter into Particle Edit mode of a baked system. Anyways, there is currently nothing visible, nothing to work on. There is no reason to let access to the mode, if feature is not supported.

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Hair Dynamics: entering particle edit mode with baked cache crashes blender #59583