Vertex groups for hair (length etc.): effect not always satisfactory #54069

Closed
opened 2018-02-14 09:14:18 +01:00 by Tom Telos · 10 comments

System Information
iMac 27-in late 2015; 16GB; AMD Radeon R9 M395X 4GB

Blender Version
Broken: recent builds of 2.80 and 2.79 (feb 2018); 2.78c; 2.75a. Worked: none yet

When you open the attached .blend file,
VgLen.blend you will see two objects with particle-based hair.

The lower one has a vertex group for length, that covers the entire object,
whose weights go linearly from 1 to almost 0, and its effect on hair length
is not quite what one would expect, but close:
weights of 0.9 and 0.8 appear to have the same effect as 1.0,
and the shortest hairs are about 1/4 the length of the longest, as opposed to almost 0,
but there is, clearly, a linear dropoff from vertex weight 0.8 on downwards.
This I observe with interpolated child particles, no kink,
or with kink = Curl, Radial, Wave, or Braid.
Note: Kink = Spiral does produce a length dropoff that looks impeccable!

The upper object is a simplified scalp from my WIP here: https://sta.sh/21968qcn7oqe

It also has vertex groups for density, length, and kink, but here the discrepancy
between the expected hair lengths and what one sees is much greater.
In this case, even kink = Spiral fails to satisfy length expectations; moreover,
less than half the hairs receive a spiral, even when I’m not using any vertex group for kink.

**System Information** iMac 27-in late 2015; 16GB; AMD Radeon R9 M395X 4GB **Blender Version** Broken: recent builds of 2.80 and 2.79 (feb 2018); 2.78c; 2.75a. Worked: none yet When you open the attached .blend file, [VgLen.blend](https://archive.blender.org/developer/F2270385/VgLen.blend) you will see two objects with particle-based hair. The lower one has a vertex group for length, that covers the entire object, whose weights go linearly from 1 to almost 0, and its effect on hair length is not quite what one would expect, but close: weights of 0.9 and 0.8 appear to have the same effect as 1.0, and the shortest hairs are about 1/4 the length of the longest, as opposed to almost 0, but there is, clearly, a linear dropoff from vertex weight 0.8 on downwards. This I observe with *interpolated child particles, no kink,* or with kink = Curl, Radial, Wave, or Braid. **Note**: Kink = Spiral does produce a length dropoff that looks impeccable! The upper object is a simplified scalp from my WIP here: https://sta.sh/21968qcn7oqe It also has vertex groups for density, length, and kink, but here the discrepancy between the expected hair lengths and what one sees is much greater. In this case, even kink = Spiral fails to satisfy length expectations; moreover, less than half the hairs receive a spiral, even when I’m not using any vertex group for kink.
Author

Added subscriber: @ttelos

Added subscriber: @ttelos
Member

Added subscriber: @MaiLavelle

Added subscriber: @MaiLavelle
Member

I'm not entirely sure what the cause is, but it seems to related to the number of hair segments interacting strangely with interpolation. There are plans to replace particles with a new system, so not sure if this will end up getting fixed in the current system or not. In the mean time increasing the 'steps' parameter should give you a better result.

I'm not entirely sure what the cause is, but it seems to related to the number of hair segments interacting strangely with interpolation. There are plans to replace particles with a new system, so not sure if this will end up getting fixed in the current system or not. In the mean time increasing the 'steps' parameter should give you a better result.
Author

Thank you, Mai.

The “Steps” parameter is specifically for kink=Spiral, and appears to affect only the presentation of the spiral,
but the “Segments” parameter that shows up near the top of the Particles Properties does influence hairs
in remarkable ways. My .blend file has it set at its default value, 5. If you select the scalp object
(named HeadLenTest) and bring Segments down to 4, you will see that, in response,
many hairs now extend their endpoints into the scalp, even though the object’s normals all point outward.
This effect is most obvious with kink=Spiral: you will then notice that all the hairs that extend inwards
have their spiral on the “in” side, which may provide a partial explanation to why, when Segments=5,
many hairs appear to have no spiral.

When Segments=2, no hairs project into the scalp, and the range of lengths appear to be ok.

Raising the Segments value from 5 to 10, or 20, appears to have no effect other than to shorten the hairs.

Thank you, Mai. The “Steps” parameter is specifically for kink=Spiral, and appears to affect only the presentation of the spiral, but the “Segments” parameter that shows up near the top of the Particles Properties does influence hairs in remarkable ways. My .blend file has it set at its default value, 5. If you select the scalp object (named HeadLenTest) and bring Segments down to 4, you will see that, in response, many hairs now extend their endpoints *into the scalp,* even though the object’s normals all point outward. This effect is most obvious with kink=Spiral: you will then notice that all the hairs that extend inwards have their spiral on the “in” side, which may provide a partial explanation to why, when Segments=5, many hairs appear to have no spiral. When Segments=2, no hairs project into the scalp, and the range of lengths appear to be ok. Raising the Segments value from 5 to 10, or 20, appears to have no effect other than to shorten the hairs.

Added subscriber: @zeauro

Added subscriber: @zeauro

The “Steps” parameter is specifically for kink=Spiral, and appears to affect only the presentation of the spiral,

Mai is not talking about this setting present in Children panel.

In Display panel and Render Panel, there is also a "Steps" parameter.
This steps are set to a value of 2 or 3. If you increase them to 10, you obtain a better render result.

Steps are controlling visual segments of hair path.
Step to 0, you obtain a straight line. Steps to 1, you see a polyline of 2 segments. Steps to 2, a polyline of 4 segments, Steps to 3, a polyline of 8 segments. etc.... It is a power of 2.

You can define 20 physical segments that can be edited in Particle Edit mode and would be used by hair dynamics simulation.
If number of steps stays equal to 2, path stays visually a polyline of 4 segments.
And any particle emitted from face is not emitted from a vert. It has a weight higher than 0. So, first step is shown for most of particles.

Increasing number of steps on a path of same length means reducing length of this first step.

Increasing default value for "Steps" parameter, everywhere, to 4 would probably be more pleasant for users and lead to less questions.

> The “Steps” parameter is specifically for kink=Spiral, and appears to affect only the presentation of the spiral, Mai is not talking about this setting present in Children panel. In Display panel and Render Panel, there is also a "Steps" parameter. This steps are set to a value of 2 or 3. If you increase them to 10, you obtain a better render result. Steps are controlling visual segments of hair path. Step to 0, you obtain a straight line. Steps to 1, you see a polyline of 2 segments. Steps to 2, a polyline of 4 segments, Steps to 3, a polyline of 8 segments. etc.... It is a power of 2. You can define 20 physical segments that can be edited in Particle Edit mode and would be used by hair dynamics simulation. If number of steps stays equal to 2, path stays visually a polyline of 4 segments. And any particle emitted from face is not emitted from a vert. It has a weight higher than 0. So, first step is shown for most of particles. Increasing number of steps on a path of same length means reducing length of this first step. Increasing default value for "Steps" parameter, everywhere, to 4 would probably be more pleasant for users and lead to less questions.

Added subscriber: @Sergey

Added subscriber: @Sergey
Sergey Sharybin self-assigned this 2018-02-19 17:54:11 +01:00

Caused by 4f1c0a1. Will give a closer look on what's wrong in that commit later.

Caused by 4f1c0a1. Will give a closer look on what's wrong in that commit later.

This issue was referenced by 87e37224c7

This issue was referenced by 87e37224c74a4336278e27b0de9e2223701439ae

Changed status from 'Open' to: 'Resolved'

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