Page MenuHome

Hair particles: Entering sculpt mode [dyntopo] changes hair particle distribution without warning
Confirmed, LowPublicKNOWN ISSUE


System Information
Operating system: Windows-10-10.0.18362 64 Bits
Graphics card: GeForce RTX 2060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 436.30

Blender Version
Broken: version: 2.81 (sub 12), branch: master, commit date: 2019-10-01 19:51, hash: rB3b23685c7dc1
Worked: Don't know

Short description of error
Entering Sculpt Mode can mess up particle settings without warning. See the attached gif.

Exact steps for others to reproduce the error
In the attached blend file, notice hair in the "x" pattern on the cube. Switch to Sculpt Mode, then back to the Particle Edit mode. Notice the hair pattern has changed.

To reproduce the issue from scratch, follow these steps:

  • Modify a mesh using sculpting tools with Dyntopo enabled.
  • Make sure the mesh has no vertex data that would cause Dyntopo to turn off when you switch away from and back to sculpting mode.
  • Make sure Dyntopo is on and switch away from sculpting mode.
  • Add a hair particle system to the mesh. Use the particle editor to add a recognizable shape to the hair.
  • Switch to sculpting mode.
  • Switch back to the particle editor and see the shape of the hair.

Event Timeline

I have managed to reproduce it as well.

I can confirm.
But since the particle system will be replaced, I think we can archive this report for now.
@Jacques Lucke (JacquesLucke), what do you think?

Philipp Oeser (lichtwerk) lowered the priority of this task from 90 to Low.Oct 17 2019, 6:30 PM

Same thing happens in 2.79.
I would still vote to generally keep hair reports (even if with low prio), since I dont see the new hair system arriving anytime soon.

Philipp Oeser (lichtwerk) renamed this task from Entering sculpt mode changes hair particle settings without warning to Hair particles: Entering sculpt mode [dyntopo] changes hair particle distribution without warning.Oct 17 2019, 6:30 PM
Germano Cavalcante (mano-wii) changed the subtype of this task from "Report" to "Known Issue".

Marking as Known Issue since there are no plans to work on this problem so soon.
Adding a warning seems to be a solution.