bake hair dynamics issues #62893

Open
opened 2019-03-24 12:34:24 +01:00 by dev369 · 12 comments

System Information
Operating system: wind 10
Graphics card: gtx 1070

Blender Version
Broken: blender-2.80-79f67acccb36-win64
Worked: idk

unable to bake hair dynamics. i click the button but nothing happens. in particle edit mode particle hair still looks as if it was not simulated.

**System Information** Operating system: wind 10 Graphics card: gtx 1070 **Blender Version** Broken: blender-2.80-79f67acccb36-win64 Worked: idk unable to bake hair dynamics. i click the button but nothing happens. in particle edit mode particle hair still looks as if it was not simulated.
Author

Added subscriber: @dev369

Added subscriber: @dev369
Member

Added subscriber: @JacquesLucke

Added subscriber: @JacquesLucke
Member

I can't reproduce the issue in my simple test.
Please provide an as-simple-as-possible .blend file that shows the issue.

I can't reproduce the issue in my simple test. Please provide an as-simple-as-possible .blend file that shows the issue.
Author

here i made a simple uv sphere, i made hair particle, i click bake, i try switch to perticle edit and it crashes blender. you can open this blend and try switch to particle edit, it will crash it

crash.blend

here i made a simple uv sphere, i made hair particle, i click bake, i try switch to perticle edit and it crashes blender. you can open this blend and try switch to particle edit, it will crash it [crash.blend](https://archive.blender.org/developer/F6881205/crash.blend)
Author

this is the same thing, except, before bake i enabled disk cache. now it does not crash with switching to particle edit, but particles are not visible in particle edit.

no particles in particle edit.blend

this is the same thing, except, before bake i enabled disk cache. now it does not crash with switching to particle edit, but particles are not visible in particle edit. [no particles in particle edit.blend](https://archive.blender.org/developer/F6881267/no_particles_in_particle_edit.blend)
dev369 changed title from bake hair dynamics doesnt do anything to bake hair dynamics issues 2019-03-25 15:38:18 +01:00
Author

should this not be at least high priority and be fixed for release of 2.8? hair dynamics is pretty important feature id say, currently i still cant get it to work its been a while. i mean, without hair dynamics we are severely limited to what we do by hand and rigging..

should this not be at least high priority and be fixed for release of 2.8? hair dynamics is pretty important feature id say, currently i still cant get it to work its been a while. i mean, without hair dynamics we are severely limited to what we do by hand and rigging..
Member

Added subscribers: @rjg, @lichtwerk

Added subscribers: @rjg, @lichtwerk
Member

On entering particle editmode in crash.blend I am getting :
BLI_assert failed: /blender/source/blender/draw/intern/draw_cache_impl_particles.c:1519, particle_batch_cache_ensure_edit_pos_and_seg(), at '!"Hairs are not in edit mode!"'
This I have definitely seen in other reports, will dig these up...

Looks like a duplicate of #59583, no?

I am not too familiar with the hair system, but may I ask what particle editing after caching dynamics is actually there for?
(is this used for cache editing like for cloth -- to fix penetrations?)
I can see 2.79b and 2.79 branch being able to do this, but even there it seems pretty much broken, at least for me the hair cache paths look nothing like the actual hair (when in particle edit mode...)
@rjg (the reporter of #59583) also mentioned in his report:

I'm not sure when or why you'd actually want to do that, but it shouldn't cause a crash...

The issue with not seeing the particles in particle editmode (no particles in particle edit.blend) might stem from the issue that these caches sometimes cannot be generated correctly (see reports like #62563 (Hair Dynamics: cannot generate a valid particle cache))

On entering particle editmode in crash.blend I am getting : ``BLI_assert failed: /blender/source/blender/draw/intern/draw_cache_impl_particles.c:1519, particle_batch_cache_ensure_edit_pos_and_seg(), at '!"Hairs are not in edit mode!"'`` This I have definitely seen in other reports, will dig these up... Looks like a duplicate of #59583, no? I am not too familiar with the hair system, but may I ask what particle editing **after** caching dynamics is actually there for? (is this used for cache editing like for cloth -- to fix penetrations?) I can see 2.79b and 2.79 branch being able to do this, but even there it seems pretty much broken, at least for me the hair cache paths look nothing like the actual hair (when in particle edit mode...) @rjg (the reporter of #59583) also mentioned in his report: > I'm not sure when or why you'd actually want to do that, but it shouldn't cause a crash... The issue with not seeing the particles in particle editmode (`no particles in particle edit.blend`) might stem from the issue that these caches sometimes cannot be generated correctly (see reports like #62563 (Hair Dynamics: cannot generate a valid particle cache))

Added subscriber: @grosgood

Added subscriber: @grosgood

@lichtwerk

... might stem from the issue that these caches sometimes cannot be generated correctly (see reports like #62563: Hair Dynamics: cannot generate a valid particle cache)

This might narrow your search scope. #62563 is grounded in a memory management tactic adopted for the rendering depsgraph, which, since November 2018, is deleted after use on every frame. The need to do that arises from the large memory consumption of the rendering depsgraph contending for the equally large memory requirements of the renderer, observed in some of the fairly immense scenes found in the Spring production. Unfortunately, hair dynamics code examines particle system state across multiple frames, and gets confused when the cleaning up of the rendering depsgraph also cleans up the cow'ed object and related particle system buffers. There are some text files which I wrote attached to that bug report which goes into gory details.
That issue doesn't figure in this bug, I don't think, because the depsgraph for the viewport has an indefinite lifetime; the disappearance of a depsgraph does not drive this bug in the manner that it does for #62563.
Per the User Guide particle editing by and large depends on a pre-existing in-memory baked cache: baking to disk does not support particle editing. The cache also needs to be frame-to-frame coherent. An in-memory cache with dropped or trashed frames can give rise to all kinds of interesting behavior but the issue would be difficult to notice until the particle system loads the queer data and tries to manipulate it. I suspect (but have not proved) the case of corruption after cache generation from time to time, making bugs of this type transient in nature. That's as far as I come with this. Thank you for your work in - at least - bringing some order to the bug reports surrounding the dark secrets of the particle and hair system.

@lichtwerk >... might stem from the issue that these caches sometimes cannot be generated correctly (see reports like #62563: Hair Dynamics: cannot generate a valid particle cache) This might narrow your search scope. #62563 is grounded in a memory management tactic adopted for the rendering depsgraph, which, since November 2018, is deleted after use on every frame. The need to do that arises from the large memory consumption of the rendering depsgraph contending for the equally large memory requirements of the renderer, observed in some of the fairly immense scenes found in the Spring production. Unfortunately, hair dynamics code examines particle system state across multiple frames, and gets confused when the cleaning up of the rendering depsgraph also cleans up the cow'ed object and related particle system buffers. There are some text files which I wrote attached to that bug report which goes into gory details. That issue doesn't figure in this bug, I don't think, because the depsgraph for the viewport has an indefinite lifetime; the disappearance of a depsgraph does not drive this bug in the manner that it does for #62563. Per the [User Guide](https://docs.blender.org/manual/en/latest/physics/particles/mode.html) particle editing by and large depends on a pre-existing in-memory baked cache: baking to disk does not support particle editing. The cache also needs to be frame-to-frame coherent. An in-memory cache with dropped or trashed frames can give rise to all kinds of interesting behavior but the issue would be difficult to notice until the particle system loads the queer data and tries to manipulate it. I suspect (but have not proved) the case of corruption after cache generation from time to time, making bugs of this type transient in nature. That's as far as I come with this. Thank you for your work in - at least - bringing some order to the bug reports surrounding the dark secrets of the particle and hair system.

Added subscriber: @yourhero

Added subscriber: @yourhero

is this ever get fixed?

is this ever get fixed?
Philipp Oeser removed the
Interest
Nodes & Physics
label 2023-02-10 08:47:58 +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
5 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#62893
No description provided.