Hair Particle System causes crash when Dynamic Baking is preformed, and edditing is attempted #44172

Closed
opened 2015-03-29 12:28:18 +02:00 by jorgen · 6 comments

System Information
Windows 7 Home Premium
GeForce GT 540M

Blender Version
Broken: 2.73a

By the way, i dont know if this is a Bug or something that is expected to happen. Thought it would not harm to report it anyway
If you go to [Particle Edit] after you enable [Hair Dynamics], you will see that blender will either crash, or run really really slowly.
Some times it just crashes right away, other times it gets into [Particle Edit], and i can rotate in the viewport just fine, but if i try to [Comb] the hair, then it gets stuck again.

Exact steps for others to reproduce the error
This can easily be reproduced:

  • Open up blender (Fresh)

  • Blender Internal / Cycles Render does not matter, it happens on both

  • Go to Particle system

  • Set Emition to Hair

  • Enable Hair Dynamics

  • Under Cache, click Bake

  • Go to Particle Edit

Blender should now either crash, or slow freez for a while. then if you get into particle edit, try to comb the hair.
Blender_Crash_Report.blend

**System Information** Windows 7 Home Premium GeForce GT 540M **Blender Version** Broken: 2.73a **By the way, i dont know if this is a Bug or something that is expected to happen. Thought it would not harm to report it anyway** If you go to [Particle Edit] after you enable [Hair Dynamics], you will see that blender will either crash, or run really really slowly. Some times it just crashes right away, other times it gets into [Particle Edit], and i can rotate in the viewport just fine, but if i try to [Comb] the hair, then it gets stuck again. **Exact steps for others to reproduce the error** This can easily be reproduced: * Open up blender (Fresh) * Blender Internal / Cycles Render does not matter, it happens on both * Go to Particle system * Set Emition to Hair * Enable Hair Dynamics * Under Cache, click Bake * Go to Particle Edit Blender should now either crash, or slow freez for a while. then if you get into particle edit, try to comb the hair. [Blender_Crash_Report.blend](https://archive.blender.org/developer/F156045/Blender_Crash_Report.blend)
Author

Changed status to: 'Open'

Changed status to: 'Open'
jorgen self-assigned this 2015-03-29 12:28:18 +02:00
Author

Added subscriber: @finalbarrage-2

Added subscriber: @finalbarrage-2
jorgen was unassigned by Julian Eisel 2015-03-29 15:23:04 +02:00
Lukas Tönne was assigned by Julian Eisel 2015-03-29 15:23:04 +02:00
Member

Added subscribers: @LukasTonne, @JulianEisel

Added subscribers: @LukasTonne, @JulianEisel
Member

For me it doesn't crash but it's reeeally slow. It also doesn't work better in 2.72 so I'm a bit afraid it's a more in deepth issue. Doesn't look like a memory issue, memory seems to be okay. Got ~13% CPU usage on my 8 threads machine, so I'd guess it just locks the main thread. If this is case this is definitely a todo.

@LukasTonne, what do you think? (We also better move this to the todo list if it's nothing you can look into soon, users should know that they can just press "Free Bake")

For me it doesn't crash but it's reeeally slow. It also doesn't work better in 2.72 so I'm a bit afraid it's a more in deepth issue. Doesn't look like a memory issue, memory seems to be okay. Got ~13% CPU usage on my 8 threads machine, so I'd guess it just locks the main thread. If this is case this is definitely a todo. @LukasTonne, what do you think? (We also better move this to the todo list if it's nothing you can look into soon, users should know that they can just press "Free Bake")
Member

The whole design here is totally unusable. Basically there are 2 modes of the "particle edit mode" (itself a misnomer already):

  • When the hair dynamics is not baked, it will enter the usual hair edit mode, i.e. you can do add, comb, cut etc. on hair strands. These strands are the static shapes that form the basis for bending and goal spring forces.
  • When the cache is in "baked" mode, the edit mode will instead use the "cache edit mode" as described above. This mode is not usable at all in it's current design, especially for hair strands. With regular particles it sort-of works by creating a path for each of the particles over time and allowing strand-like editing on these (note the difference between physical strand objects and interpolating point motion - using the same tool for both is only smart at first glance). With hair strands, however, the concept totally breaks down: it creates a new "time strand" for each of the hair vertices! With a bit of simple arithmetic one can see that the amount of data generated this way explodes and becomes too much to handle for any reasonable hardware. Even small amounts of hair also are not really editable due to the lack of visual detail anyway.

Long story short: this "feature" has to be removed.

The whole design here is totally unusable. Basically there are 2 modes of the "particle edit mode" (itself a misnomer already): * When the hair dynamics is not baked, it will enter the usual hair edit mode, i.e. you can do add, comb, cut etc. on hair strands. These strands are the static shapes that form the basis for bending and goal spring forces. * When the cache is in "baked" mode, the edit mode will instead use the "cache edit mode" as described above. This mode is not usable at all in it's current design, especially for hair strands. With regular particles it sort-of works by creating a path for each of the particles over time and allowing strand-like editing on these (note the difference between physical strand objects and interpolating point motion - using the same tool for both is only smart at first glance). With hair strands, however, the concept totally breaks down: it creates a new "time strand" for each of the hair vertices! With a bit of simple arithmetic one can see that the amount of data generated this way explodes and becomes too much to handle for any reasonable hardware. Even small amounts of hair also are not really editable due to the lack of visual detail anyway. Long story short: this "feature" has to be removed.
Member

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'
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
3 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#44172
No description provided.