Alembic - Aplly scale doesn't work with the Mesh Sequence and hair #63654

Closed
opened 2019-04-16 10:37:36 +02:00 by Serj Maiorov · 10 comments

System Information
Operating system: Windows-10-10.0.17134 64 Bits
Graphics card: GeForce RTX 2070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 418.96

Blender Version
Broken: version: 2.80 (sub 57), branch: master, commit date: 2019-04-14 19:18, hash: 860a9f979d
Worked: (optional)

Short description of error
I have lots of brushed hair on a character. Scaling is crucial to hair systems, and when I import an Alembic without animation, All I have to do is to scale the alembic to the size of my character, apply scale and copy all the hairs systems - works like magic.
The problem begins when I import an animated alembic, no matter what I do the hair goes craze and when I apply the scale it jumps back to its original size and messes the hair again.

Exact steps for others to reproduce the error
All I need to do is to import the alembic' copy weight paints, copy all the particles systems, scale the Alembic to the right size, apply scale - and it jumps back.
tried to import an Alembic with smaller scaler beforehand but didn't work either

RAR file with Blend and Alembic
AlembicSequenceTests.rar

BeforeModifier_001.PNG

AfterModifier_001.PNG

**System Information** Operating system: Windows-10-10.0.17134 64 Bits Graphics card: GeForce RTX 2070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 418.96 **Blender Version** Broken: version: 2.80 (sub 57), branch: master, commit date: 2019-04-14 19:18, hash: `860a9f979d` Worked: (optional) **Short description of error** I have lots of brushed hair on a character. Scaling is crucial to hair systems, and when I import an Alembic without animation, All I have to do is to scale the alembic to the size of my character, apply scale and copy all the hairs systems - works like magic. The problem begins when I import an animated alembic, no matter what I do the hair goes craze and when I apply the scale it jumps back to its original size and messes the hair again. **Exact steps for others to reproduce the error** All I need to do is to import the alembic' copy weight paints, copy all the particles systems, scale the Alembic to the right size, apply scale - and it jumps back. tried to import an Alembic with smaller scaler beforehand but didn't work either RAR file with Blend and Alembic [AlembicSequenceTests.rar](https://archive.blender.org/developer/F6950869/AlembicSequenceTests.rar) ![BeforeModifier_001.PNG](https://archive.blender.org/developer/F6950902/BeforeModifier_001.PNG) ![AfterModifier_001.PNG](https://archive.blender.org/developer/F6950903/AfterModifier_001.PNG)
Author

Added subscriber: @SerjMaiorov

Added subscriber: @SerjMaiorov
Serj Maiorov changed title from Alembic - Aplly scale doesn't work with the Mesh Sequence to Alembic - Aplly scale doesn't work with the Mesh Sequence and hair 2019-04-16 10:40:28 +02:00

Added subscribers: @dr.sybren, @ZedDB

Added subscribers: @dr.sybren, @ZedDB
Sybren A. Stüvel was assigned by Sebastian Parborg 2019-04-16 14:00:15 +02:00

Unsure if applying scale is supported for sequence caches. @dr.sybren any input on this?

Unsure if applying scale is supported for sequence caches. @dr.sybren any input on this?

Applying scale is not supported. This changes the mesh data, which is replaced with the data from Alembic. Try creating an Empty, set it as the parent of the imported Alembic object, and scale the Empty.

Applying scale is not supported. This changes the mesh data, which is replaced with the data from Alembic. Try creating an Empty, set it as the parent of the imported Alembic object, and scale the Empty.
Author

Tried to do that but it still breaks the hair
Bug_001.PNG

Tried to do that but it still breaks the hair ![Bug_001.PNG](https://archive.blender.org/developer/F6951642/Bug_001.PNG)
Author

Is there an alternative to that workflow? Because we use real world scales to be consistent with lighting and materials over live footages. How can we interchange hair between Alembics and still maintain real scales?

Is there an alternative to that workflow? Because we use real world scales to be consistent with lighting and materials over live footages. How can we interchange hair between Alembics and still maintain real scales?

Blender's hair system is very picky when it comes to the mesh it's attached to. Especially when grooming, it is vital that the face & vertex indices remain the same. Are you sure that the mesh in Alembic didn't change between grooming the hair in Blender and getting these errors?

Please provide us with an as-simple-as-possible test file. This file has various hidden (and thus probably irrelevant) objects, three different hair systems, and a subdivision modifier that may or may not influence the result.

As an alternative workflow, what is stopping you from exporting to Alembic in the correct scale, so that later stages in the pipeline can just use the file as-is?

Blender's hair system is very picky when it comes to the mesh it's attached to. Especially when grooming, it is vital that the face & vertex indices remain the same. Are you sure that the mesh in Alembic didn't change between grooming the hair in Blender and getting these errors? Please provide us with an as-simple-as-possible test file. This file has various hidden (and thus probably irrelevant) objects, three different hair systems, and a subdivision modifier that may or may not influence the result. As an alternative workflow, what is stopping you from exporting to Alembic in the correct scale, so that later stages in the pipeline can just use the file as-is?

This is probably the same issue as #63534.

This is probably the same issue as #63534.

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'

Since last asking for information it has been 7 or more days, due to the policy of our bug tracker we will have to archive the report until the requested information is given.

This issue is probably solved in ee8aad79c1. If not, please provide the requested information.

Since last asking for information it has been 7 or more days, due to the policy of our bug tracker we will have to archive the report until the requested information is given. This issue is probably solved in ee8aad79c159. If not, please provide the requested information.
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#63654
No description provided.