Enabling Surface Rest Position in the Interpolate Hair Curves Modifier Disconnects Hair from Surface Mesh #109398

Closed
opened 2023-06-27 08:14:03 +02:00 by Chris Jones · 7 comments

System Information
Operating system: Windows-10-10.0.22621-SP0 64 Bits
Graphics card: Intel(R) UHD Graphics 770 Intel 4.5.0 - Build 31.0.101.3959

Blender Version
Broken: version: 3.5.1, branch: blender-v3.5-release, commit date: 2023-04-24 18:11, hash: e1ccd9d4a1d3
Worked: No versions that I am aware of.

Short description of error
Toggling on "Surface Rest Position" in the Interpolate Hair Curves modifier detaches the hairs from the surface mesh in an animation. This is resolved by positioning the Surface Deform modifier at the top of the modifier stack, however this is not recommended (as per #109285)

Exact steps for others to reproduce the error

  1. Load the attached file and press play
  2. Check "Surface Rest Position" in the Interpolate Hair Curves modifier, and observe that the hair is no longer attached.
**System Information** Operating system: Windows-10-10.0.22621-SP0 64 Bits Graphics card: Intel(R) UHD Graphics 770 Intel 4.5.0 - Build 31.0.101.3959 **Blender Version** Broken: version: 3.5.1, branch: blender-v3.5-release, commit date: 2023-04-24 18:11, hash: `e1ccd9d4a1d3` Worked: No versions that I am aware of. **Short description of error** Toggling on "Surface Rest Position" in the Interpolate Hair Curves modifier detaches the hairs from the surface mesh in an animation. This is resolved by positioning the Surface Deform modifier at the top of the modifier stack, however this is not recommended (as per [#109285](https://projects.blender.org/blender/blender/issues/109285#issuecomment-965372)) **Exact steps for others to reproduce the error** 1. Load the attached file and press play 2. Check "Surface Rest Position" in the Interpolate Hair Curves modifier, and observe that the hair is no longer attached.
Chris Jones added the
Type
Report
Status
Needs Triage
Priority
Normal
labels 2023-06-27 08:14:04 +02:00
Member

Likely the same cause as #107856 ?

Likely the same cause as #107856 ?
Author

Likely the same cause as #107856 ?

That was @SimonThommes 's inclination, however since the issue persists when the subsurface modifier is applied, he suggested making a separate report (hence this one).

> Likely the same cause as #107856 ? That was @SimonThommes 's inclination, however since the issue persists when the subsurface modifier is applied, he [suggested](https://projects.blender.org/blender/blender/issues/109285#issuecomment-966826) making a separate report (hence this one).
Member

Can confirm

Can confirm

I believe you are misinterpreting how it works before enabling rest position:

-With rest position disabled, it's just "snapping" the source curves onto the closest surface at the moment, thus it looks like the hair moves with the animated mesh- but it's just re-snapping each frame

-With rest position enabled, it properly snaps to the rest position mesh before posing

-However, this mesh has invalid UVs: so this makes it so they cannot pose at all. I think this is because you are using an UDIM uv map, which causes invalid attachments

Simplest fix is to create a new uv map that is just within the regular bounds, and has no mirrors.

It is also possible to edit the interpolation node to accept a second "attachment" UV map separate from the color UV map, but that is more advanced and you'd have to dive into the interpolation node group, which is what I did for one of my projects that had UDIM uv maps

I believe you are misinterpreting how it works before enabling rest position: -With rest position disabled, it's just "snapping" the source curves onto the closest surface at the moment, thus it looks like the hair moves with the animated mesh- but it's just re-snapping each frame -With rest position enabled, it properly snaps to the rest position mesh *before* posing -However, this mesh has invalid UVs: so this makes it so they cannot pose at all. I think this is because you are using an UDIM uv map, which causes invalid attachments Simplest fix is to create a new uv map that is just within the regular bounds, and has no mirrors. It is also possible to edit the interpolation node to accept a second "attachment" UV map separate from the color UV map, but that is more advanced and you'd have to dive into the interpolation node group, which is what I did for one of my projects that had UDIM uv maps
Author

I'm still somewhat new to UDIMS and might be misunderstanding, but as far as I can tell the UVs are contained within the first UDIM tile, and the only references to UDIMs that I can find is in the Overlays panel, where Tiles X is set to 4 (which is only a visual guide, from what I gather), and the UV Map name being "UVMap UDIM".

Nonetheless, the Invalid surface UVs message remains when setting Tiles X to 1 and creating a new UV map.

I'm still somewhat new to UDIMS and might be misunderstanding, but as far as I can tell the UVs are contained within the first UDIM tile, and the only references to UDIMs that I can find is in the Overlays panel, where Tiles X is set to 4 (which is only a visual guide, from what I gather), and the UV Map name being "UVMap UDIM". Nonetheless, the Invalid surface UVs message remains when setting Tiles X to 1 and creating a new UV map.

I'm still somewhat new to UDIMS and might be misunderstanding, but as far as I can tell the UVs are contained within the first UDIM tile, and the only references to UDIMs that I can find is in the Overlays panel, where Tiles X is set to 4 (which is only a visual guide, from what I gather), and the UV Map name being "UVMap UDIM".

Nonetheless, the Invalid surface UVs message remains when setting Tiles X to 1 and creating a new UV map.

If the UVs are all within the first tile then it's fine, yes.

I've found an issue with the file, on the interpolation node modifier you do not have the UV Map attribute set. You need to set it to the UV map's name, in this case, "UVMap UDIM"

After setting this the curves get their valid attachment.

Note: If you alter the uv map, you must re-connect the curves by going into sculpt mode -> snap to nearest surface

> I'm still somewhat new to UDIMS and might be misunderstanding, but as far as I can tell the UVs are contained within the first UDIM tile, and the only references to UDIMs that I can find is in the Overlays panel, where Tiles X is set to 4 (which is only a visual guide, from what I gather), and the UV Map name being "UVMap UDIM". > > Nonetheless, the Invalid surface UVs message remains when setting Tiles X to 1 and creating a new UV map. If the UVs are all within the first tile then it's fine, yes. I've found an issue with the file, on the interpolation node modifier you do not have the UV Map attribute set. You need to set it to the UV map's name, in this case, "UVMap UDIM" After setting this the curves get their valid attachment. Note: If you alter the uv map, you must re-connect the curves by going into sculpt mode -> snap to nearest surface
Author

I've found an issue with the file, on the interpolation node modifier you do not have the UV Map attribute set. You need to set it to the UV map's name, in this case, "UVMap UDIM"

This does appear to be the culprit; the UV map attribute in the Interpolate Hair Curves modifier must have been lost at some point while I was trying to isolate the original bug from which this one stemmed (the original issue still stands though).

Thanks for your input, I'll close this report.

> I've found an issue with the file, on the interpolation node modifier you do not have the UV Map attribute set. You need to set it to the UV map's name, in this case, "UVMap UDIM" This does appear to be the culprit; the UV map attribute in the Interpolate Hair Curves modifier must have been lost at some point while I was trying to isolate the [original bug](https://projects.blender.org/blender/blender/issues/109285) from which this one stemmed (the original issue still stands though). Thanks for your input, I'll close this report.
Blender Bot added
Status
Archived
and removed
Status
Confirmed
labels 2023-08-16 05:21:32 +02: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
4 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#109398
No description provided.