blender
/
blender
128
396
Fork 568
Code Issues 6.2k Pull Requests 749 Projects 19 Wiki Activity

Interpolated hair curves clipping into meshes with subdivision modifiers unapplied #107856

New Issue
Open
opened 2023-05-12 01:27:17 +02:00 by Ducktor · 10 comments
Ducktor commented 2023-05-12 01:27:17 +02:00
Copy Link

System Information
Operating system: Windows 10
Graphics card: RTX 2080 Super Max-Q

Blender Version
Broken: 3.51
Worked: N/A

Short description of error
Interpolated hair curves clip into meshes with unapplied subdivision modifiers. Will stop clipping once subdivision is applied.

Exact steps for others to reproduce the error

  1. Create a mesh (i.e. suzanne) and add a subdivision modifier with any amount of subdivision.
  2. Add 'fur' hair curves and do a basic groom
  3. Notice (hopefully) that there a bald spots. No amount of extra guide curves will remove these bald spots
  4. Applying the subdivision modifier should remove these bald spots.
**System Information** Operating system: Windows 10 Graphics card: RTX 2080 Super Max-Q **Blender Version** Broken: 3.51 Worked: N/A **Short description of error** Interpolated hair curves clip into meshes with unapplied subdivision modifiers. Will stop clipping once subdivision is applied. **Exact steps for others to reproduce the error** 1. Create a mesh (i.e. suzanne) and add a subdivision modifier with any amount of subdivision. 2. Add 'fur' hair curves and do a basic groom 3. Notice (hopefully) that there a bald spots. No amount of extra guide curves will remove these bald spots 4. Applying the subdivision modifier should remove these bald spots.
SUZANNE fur groom clipping.blend
3.7 MiB
Ducktor added the
Priority
Normal
Type
Report
Status
Needs Triage
 labels 2023-05-12 01:27:18 +02:00
YimingWu commented 2023-05-12 08:24:02 +02:00
Member
Copy Link

Update:

rest_position seem to specifically only represent surface without applying modifiers and shape keys, so this might not be considered as a bug. However if I change the node into using position, or turn off rest_position, most furs will go underneath the mesh, but applying modifier seems to bring them back up without changing the placement.

Can confirm. From the look of it, rest_position field doesn't seem to align with the subdivided result.

Unable to test earlier version since nodes and curves doesn't work the same way. From 3.5.0~3.6 all consistent behaviour.

图片

Update: `rest_position` seem to specifically only represent surface without applying modifiers and shape keys, so this might not be considered as a bug. However if I change the node into using `position`, or turn off `rest_position`, most furs will go underneath the mesh, but applying modifier seems to bring them back up without changing the placement. ------- ~~Can confirm. From the look of it, `rest_position` field doesn't seem to align with the subdivided result.~~ Unable to test earlier version since nodes and curves doesn't work the same way. From 3.5.0~3.6 all consistent behaviour. ![图片](/attachments/3be77859-d7f4-4fcf-bb23-dab75403d70c)
图片.png
147 KiB
YimingWu added
Module
Nodes & Physics
Status
Confirmed
Interest
Geometry Nodes
 and removed
Status
Needs Triage
 labels 2023-05-12 08:25:15 +02:00
YimingWu added
Status
Needs Info from Developers
 and removed
Status
Confirmed
 labels 2023-05-12 08:26:16 +02:00
Iliya Katushenock commented 2023-05-12 13:13:01 +02:00
Member
Copy Link

I can't fine source of rest_position attribute in all blender project. If delete Input Named Attribute and Set Position nodes, everyting going be okay. But i not sure, why this attribute is exist in named attribute output...

I can't fine source of `rest_position` attribute in all blender project. If delete `Input Named Attribute` and `Set Position` nodes, everyting going be okay. But i not sure, why this attribute is exist in named attribute output...
YimingWu commented 2023-05-12 13:20:03 +02:00
Member
Copy Link

@mod_moder rna_object.c line 3265

  prop = RNA_def_property(srna, "add_rest_position_attribute", PROP_BOOLEAN, PROP_NONE);
  RNA_def_property_boolean_sdna(prop, NULL, "modifier_flag", OB_MODIFIER_FLAG_ADD_REST_POSITION);
  RNA_def_property_ui_text(prop,
                           "Add Rest Position",
                           "Add a \"rest_position\" attribute that is a copy of the position "
                           "attribute before shape keys and modifiers are evaluated");
  RNA_def_property_update(prop, NC_OBJECT | ND_DRAW, "rna_Object_internal_update_data");
@mod_moder `rna_object.c` line 3265 ```C prop = RNA_def_property(srna, "add_rest_position_attribute", PROP_BOOLEAN, PROP_NONE); RNA_def_property_boolean_sdna(prop, NULL, "modifier_flag", OB_MODIFIER_FLAG_ADD_REST_POSITION); RNA_def_property_ui_text(prop, "Add Rest Position", "Add a \"rest_position\" attribute that is a copy of the position " "attribute before shape keys and modifiers are evaluated"); RNA_def_property_update(prop, NC_OBJECT | ND_DRAW, "rna_Object_internal_update_data"); ```
👀 1
Ducktor commented 2023-05-12 19:19:29 +02:00
Author
Copy Link

rest_position seem to specifically only represent surface without applying modifiers and shape keys, so this might not be considered as a bug. However if I change the node into using position, or turn off rest_position, most furs will go underneath the mesh, but applying modifier seems to bring them back up without changing the placement.

How is this issue with fur clipping into mesh supposed to be solved in that case (other than applying subdiv modifier)? Is this just a technical limitation of geonode hair right now? I really hope not since being able to have fur on animated characters is a pretty important thing.

> rest_position seem to specifically only represent surface without applying modifiers and shape keys, so this might not be considered as a bug. However if I change the node into using position, or turn off rest_position, most furs will go underneath the mesh, but applying modifier seems to bring them back up without changing the placement. How is this issue with fur clipping into mesh supposed to be solved in that case (other than applying subdiv modifier)? Is this just a technical limitation of geonode hair right now? I really hope not since being able to have fur on animated characters is a pretty important thing.
YimingWu commented 2023-05-13 16:12:49 +02:00
Member
Copy Link

@HooglyBoogly Any input on this?

@HooglyBoogly Any input on this?
Iliya Katushenock commented 2023-05-13 16:17:18 +02:00
Member
Copy Link

This is why I don't like the fact that there is no repository for assets. First of all, the creator of assets or someone who is familiar with them must understand if this is a bug in the asset, or in the blender code.

This is why I don't like the fact that there is no repository for assets. First of all, the creator of assets or someone who is familiar with them must understand if this is a bug in the asset, or in the blender code.
Ducktor commented 2023-05-21 20:55:26 +02:00
Author
Copy Link

Is there still no information on this? I was able to find a somewhat working solution, but it still caused clipping when deforming.

Is there still no information on this? I was able to find a somewhat working solution, but it still caused clipping when deforming.
👀 1
Ducktor commented 2023-06-15 04:40:26 +02:00
Author
Copy Link

Still nothing? I haven't been able to continue my work for over a month.

Still nothing? I haven't been able to continue my work for over a month.
YimingWu commented 2023-06-15 05:47:21 +02:00
Member
Copy Link

For now you might want to work on a mesh that has applied subdiv modifier. Keep in mind that the attribute system is constantly changing. Also Rest Position is not well documented.

4.0 also has the same problem. Will poke devs again.

For now you might want to work on a mesh that has applied subdiv modifier. Keep in mind that the attribute system is constantly changing. Also `Rest Position` is not well documented. 4.0 also has the same problem. Will poke devs again.
Ducktor commented 2023-10-04 21:07:28 +02:00
Author
Copy Link

Is there timeline for a fix for this? It's still a pretty huge issue for me. Having to apply subdiv is a deal breaker in a lot of cases especially on meshes with corrective shapekeys (of course, shape keys can be preserved when applying subdiv with an addon but I'm specifically talking about drivers being erased, etc)

Is there timeline for a fix for this? It's still a pretty huge issue for me. Having to apply subdiv is a deal breaker in a lot of cases especially on meshes with corrective shapekeys (of course, shape keys can be preserved when applying subdiv with an addon but I'm specifically talking about drivers being erased, etc)
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
main
brush-assets-project
blender-v4.1-release
blender-v3.3-release
blender-v3.6-release
universal-scene-description
blender-v3.6-temp_wmoss_animrig_public
temp-sculpt-dyntopo
gpencil-next
anim/animation-id-113594
blender-v4.0-release
blender-projects-basics
bridge-curves
sculpt-blender
asset-browser-frontend-split
asset-shelf
tmp-usd-python-mtl
tmp-usd-3.6
blender-v3.5-release
blender-v2.93-release
realtime-clock
sculpt-dev
bevelv2
xr-dev
v4.1.1
v3.6.11
v3.3.18
v4.1.0
v3.3.17
v3.6.10
v3.6.9
v3.3.16
v3.6.8
v3.6.7
v3.3.14
v4.0.2
v4.0.1
v4.0.0
v3.6.5
v3.3.12
v3.6.4
v3.6.3
v3.3.11
v3.6.2
v3.3.10
v3.6.1
v3.3.9
v3.6.0
v3.3.8
v3.3.7
v2.93.18
v3.5.1
v3.3.6
v2.93.17
v3.5.0
v2.93.16
v3.3.5
v3.3.4
v2.93.15
v2.93.14
v3.3.3
v2.93.13
v2.93.12
v3.4.1
v3.3.2
v3.4.0
v3.3.1
v2.93.11
v3.3.0
v3.2.2
v2.93.10
v3.2.1
v3.2.0
v2.83.20
v2.93.9
v3.1.2
v3.1.1
v3.1.0
v2.83.19
v2.93.8
v3.0.1
v2.93.7
v3.0.0
v2.93.6
v2.93.5
v2.83.18
v2.93.4
v2.93.3
v2.83.17
v2.93.2
v2.93.1
v2.83.16
v2.93.0
v2.83.15
v2.83.14
v2.83.13
v2.92.0
v2.83.12
v2.91.2
v2.83.10
v2.91.0
v2.83.9
v2.83.8
v2.83.7
v2.90.1
v2.83.6.1
v2.83.6
v2.90.0
v2.83.5
v2.83.4
v2.83.3
v2.83.2
v2.83.1
v2.83
v2.82a
v2.82
v2.81a
v2.81
v2.80
v2.80-rc3
v2.80-rc2
v2.80-rc1
v2.79b
v2.79a
v2.79
v2.79-rc2
v2.79-rc1
v2.78c
v2.78b
v2.78a
v2.78
v2.78-rc2
v2.78-rc1
v2.77a
v2.77
v2.77-rc2
v2.77-rc1
v2.76b
v2.76a
v2.76
v2.76-rc3
v2.76-rc2
v2.76-rc1
v2.75a
v2.75
v2.75-rc2
v2.75-rc1
v2.74
v2.74-rc4
v2.74-rc3
v2.74-rc2
v2.74-rc1
v2.73a
v2.73
v2.73-rc1
v2.72b
2.72b
v2.72a
v2.72
v2.72-rc1
v2.71
v2.71-rc2
v2.71-rc1
v2.70a
v2.70
v2.70-rc2
v2.70-rc
v2.69
v2.68a
v2.68
v2.67b
v2.67a
v2.67
v2.66a
v2.66
v2.65a
v2.65
v2.64a
v2.64
v2.63a
v2.63
v2.61
v2.60a
v2.60
v2.59
v2.58a
v2.58
v2.57b
v2.57a
v2.57
v2.56a
v2.56
v2.55
v2.54
v2.53
v2.52
v2.51
v2.50
v2.49b
v2.49a
v2.49
v2.48a
v2.48
v2.47
v2.46
v2.45
v2.44
v2.43
v2.42a
v2.42
v2.41
v2.40
v2.37a
v2.37
v2.36
v2.35a
v2.35
v2.34
v2.33a
v2.33
v2.32
v2.31a
v2.31
v2.30
v2.28c
v2.28a
v2.28
v2.27
v2.26
v2.25
Labels
Clear labels   
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
This issue affects/is about backward or forward 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
Issues relating to Wayland windowing support.

  
Interest
Workbench

  
Interest: X11

Issues relating to Xorg/X11 support.

  
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
Issues relating to security: https://wiki.blender.org/wiki/Process/Vulnerability_Reports

  
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 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
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
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#107856
No description provided.
Delete Branch "%!s(<nil>)"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?