Regression : cycles motion blur glitch on alembic hair #108415

Closed
opened 2023-05-30 12:38:18 +02:00 by MOTO · 14 comments

System Information
Operating system: windows 11
Graphics card: RTX4090

Blender Version
Broken: 3.5 3.51
Worked: 3.4

Caused by 75ad8da1ea

Short description of error
alembic hair has way more strength of motion blur than other objects and makes them look transparent in cycles render

Exact steps for others to reproduce the error
just open my blend file and relink the mesh cache in the alembic file then render frames 163 and 178 you will see the glitch

**System Information** Operating system: windows 11 Graphics card: RTX4090 **Blender Version** Broken: 3.5 3.51 Worked: 3.4 Caused by 75ad8da1ea6799e3983e4146f4b20dc4bfbb8415 **Short description of error** alembic hair has way more strength of motion blur than other objects and makes them look transparent in cycles render **Exact steps for others to reproduce the error** just open my blend file and relink the mesh cache in the alembic file then render frames 163 and 178 you will see the glitch
MOTO added the
Priority
Normal
Status
Needs Triage
Type
Report
labels 2023-05-30 12:38:19 +02:00
Author
blend file link https://www.udrop.com/8e8k/MOTION_BLUR_GLITCH.blend alembic file link https://www.udrop.com/8e8n/CAOXIN_BONE_HAIR_LAYER_1_0513.abc
MOTO changed title from motion blur glitch on alembic hair to 3.5 3.5.1 motion blur glitch on alembic hair 2023-05-30 14:08:33 +02:00
MOTO changed title from 3.5 3.5.1 motion blur glitch on alembic hair to 3.5 3.5.1 cycles motion blur glitch on alembic hair 2023-05-30 14:08:55 +02:00
Member

Can confirm the difference, will check.

Can confirm the difference, will check.
Philipp Oeser added
Status
Confirmed
and removed
Status
Needs Triage
labels 2023-05-30 18:42:21 +02:00
Member

Caused by 75ad8da1ea

CC @HooglyBoogly

Caused by 75ad8da1ea6799e3983e4146f4b20dc4bfbb8415 CC @HooglyBoogly
Philipp Oeser changed title from 3.5 3.5.1 cycles motion blur glitch on alembic hair to Regression : cycles motion blur glitch on alembic hair 2023-05-30 20:42:12 +02:00
Philipp Oeser added
Priority
High
Module
Modeling
Interest
Render & Cycles
and removed
Priority
Normal
labels 2023-05-30 20:42:43 +02:00
Hans Goudey self-assigned this 2023-05-30 22:28:58 +02:00
Member

@M-M Hi, would you be able to provide a simpler file that also demonstrates the issue? 1.6 GB and 300 MB files make fixing such an issue difficult. If possible, it would help a lot. Thanks.

@M-M Hi, would you be able to provide a simpler file that also demonstrates the issue? 1.6 GB and 300 MB files make fixing such an issue difficult. If possible, it would help a lot. Thanks.
Author

@M-M Hi, would you be able to provide a simpler file that also demonstrates the issue? 1.6 GB and 300 MB files make fixing such an issue difficult. If possible, it would help a lot. Thanks.

I could cut the alembic mesh cache into a few frames if it will work for you
And I'm sorry for the delay

> @M-M Hi, would you be able to provide a simpler file that also demonstrates the issue? 1.6 GB and 300 MB files make fixing such an issue difficult. If possible, it would help a lot. Thanks. I could cut the alembic mesh cache into a few frames if it will work for you And I'm sorry for the delay
Author

@M-M Hi, would you be able to provide a simpler file that also demonstrates the issue? 1.6 GB and 300 MB files make fixing such an issue difficult. If possible, it would help a lot. Thanks.

> @M-M Hi, would you be able to provide a simpler file that also demonstrates the issue? 1.6 GB and 300 MB files make fixing such an issue difficult. If possible, it would help a lot. Thanks.
Author

@M-M Hi, would you be able to provide a simpler file that also demonstrates the issue? 1.6 GB and 300 MB files make fixing such an issue difficult. If possible, it would help a lot. Thanks.

> @M-M Hi, would you be able to provide a simpler file that also demonstrates the issue? 1.6 GB and 300 MB files make fixing such an issue difficult. If possible, it would help a lot. Thanks.
Member

Hi, thanks. I don't see a problem on frames 163 and 178 though:

Frame before "Bad frame"
image image
image image
Hi, thanks. I don't see a problem on frames 163 and 178 though: | Frame before | "Bad frame" | | ---- | ---- | | ![image](/attachments/95933bc2-148c-47e8-9b00-763e0b35d229) | ![image](/attachments/6ffeaa73-5146-455e-823c-7baff4a1b83e) | | ![image](/attachments/c8368d89-9907-4e5d-bbdb-974129b2e7d5) | ![image](/attachments/4ef86224-b2fd-4a17-8248-55ada1be85ac) |
Author

Hi, thanks. I don't see a problem on frames 163 and 178 though:

Frame before "Bad frame"
image image
image image

You have to render it in cycles and turn on the motion blur, the alembic hair will have a much stronger motion blur effect which makes it transparent and it only happens in 3.5 and above
And make sure you have applied the hair material before rendering

Here is my guess about this glitch. The alembic hair has two vector data, one is moving with the character globally and the other one is those hair cards tumbling locally, probably those two vector data have a wrong combination algorithm which significantly increases the final vector result. Because I found when the character is standstill and moves her head, the glitch is gone.
and maybe the alpha channel in the hair shader is also related to this glitch, therefore only the hair has this glitch.

> Hi, thanks. I don't see a problem on frames 163 and 178 though: > > | Frame before | "Bad frame" | > | ---- | ---- | > | ![image](/attachments/95933bc2-148c-47e8-9b00-763e0b35d229) | ![image](/attachments/6ffeaa73-5146-455e-823c-7baff4a1b83e) | > | ![image](/attachments/c8368d89-9907-4e5d-bbdb-974129b2e7d5) | ![image](/attachments/4ef86224-b2fd-4a17-8248-55ada1be85ac) | You have to render it in cycles and turn on the motion blur, the alembic hair will have a much stronger motion blur effect which makes it transparent and it only happens in 3.5 and above And make sure you have applied the hair material before rendering Here is my guess about this glitch. The alembic hair has two vector data, one is moving with the character globally and the other one is those hair cards tumbling locally, probably those two vector data have a wrong combination algorithm which significantly increases the final vector result. Because I found when the character is standstill and moves her head, the glitch is gone. and maybe the alpha channel in the hair shader is also related to this glitch, therefore only the hair has this glitch.
Member

My frame 163 looks very different:
image

If I had to guess based on the bisected commit Philipp mentioned above though, I'd guess that this is the same as #107930, and that changing the auto smooth angle to 180 might work. That does seem to help the render here actually:

image

My frame 163 looks very different: ![image](/attachments/b6608f9d-aed9-4bb0-b0d1-76999cc8ac25) If I had to guess based on the bisected commit Philipp mentioned above though, I'd guess that this is the same as #107930, and that changing the auto smooth angle to 180 might work. That does seem to help the render here actually: ![image](/attachments/8dd60c5d-96d7-408e-901e-b78480c4b80a)
260 KiB
294 KiB
Author

My frame 163 looks very different:
image

If I had to guess based on the bisected commit Philipp mentioned above though, I'd guess that this is the same as #107930, and that changing the auto smooth angle to 180 might work. That does seem to help the render here actually:

image

My snapshot is not frame 163, it was just for demonstration, this glitch occurred in my whole running scene around 500 frames, not just the two frames I picked. frame 163 is the wrong one and frame 173 is what it was supposed to be.
So this glitch will be fixed in the next update right? I am still using 3.4 for this reason.

> My frame 163 looks very different: > ![image](/attachments/b6608f9d-aed9-4bb0-b0d1-76999cc8ac25) > > If I had to guess based on the bisected commit Philipp mentioned above though, I'd guess that this is the same as #107930, and that changing the auto smooth angle to 180 might work. That does seem to help the render here actually: > > ![image](/attachments/8dd60c5d-96d7-408e-901e-b78480c4b80a) My snapshot is not frame 163, it was just for demonstration, this glitch occurred in my whole running scene around 500 frames, not just the two frames I picked. frame 163 is the wrong one and frame 173 is what it was supposed to be. So this glitch will be fixed in the next update right? I am still using 3.4 for this reason.
Member

I'm still trying to figure out what the problem is and whether it can be fixed. As I mentioned, this might be the same as #107930, which is a known issue.

Can you try setting the auto smooth angle to 180 degrees on the mesh with the particle system?

I'm still trying to figure out what the problem is and whether it can be fixed. As I mentioned, this might be the same as #107930, which is a known issue. Can you try setting the auto smooth angle to 180 degrees on the mesh with the particle system?
Author

I'm still trying to figure out what the problem is and whether it can be fixed. As I mentioned, this might be the same as #107930, which is a known issue.

Can you try setting the auto smooth angle to 180 degrees on the mesh with the particle system?

I've tried several frames with 180 degrees auto smooth and it is fixed, awesome!

But it is still considered a bug and will be fixed right?

> I'm still trying to figure out what the problem is and whether it can be fixed. As I mentioned, this might be the same as #107930, which is a known issue. > > Can you try setting the auto smooth angle to 180 degrees on the mesh with the particle system? I've tried several frames with 180 degrees auto smooth and it is fixed, awesome! But it is still considered a bug and will be fixed right?
Member

Okay, in that case this is the same as #107930. For the reasons described in the last comment there, I don't think this will be fixed in 3.6 unfortunately. I'll close this issue to merge the two.

Okay, in that case this is the same as #107930. For the reasons described in the last comment there, I don't think this will be fixed in 3.6 unfortunately. I'll close this issue to merge the two.
Blender Bot added
Status
Archived
and removed
Status
Confirmed
labels 2023-06-22 17:03:56 +02:00
Hans Goudey added
Status
Duplicate
and removed
Status
Archived
labels 2023-06-22 17:04:04 +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
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#108415
No description provided.