Maniphest T102916

Corrupt Motion Blur When Using Remesh or Volume-To-Mesh
Closed, Archived
Actions

Assigned To
None
Authored By
David (DavidM)
Dec 2 2022, 1:05 PM
Tags
  • BF Blender
Subscribers
David (DavidM)
Iliya Katueshenock (Moder)

Description

System Information
Operating system: Windows-10-10.0.19044-SP0 64 Bits
Graphics card: NVIDIA GeForce RTX 2080 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 517.40

Blender Version
Broken: version: 3.4.0 Release Candidate, branch: blender-v3.4-release, commit date: 2022-11-30 21:26, hash: rB1017b493edb9

Short description of error
Random (but repeatable) frames show heavy motion-blur corruption when using remesh modifier or mesh-to-volume node in geometry nodes.

Exact steps for others to reproduce the error
Please open up this blender file and render frame 31 with motion blur turned on - you will see the error. Turn motion blur off and is goes away.

Related Objects

Event Timeline

David (DavidM) created this task.Dec 2 2022, 1:05 PM
Iliya Katueshenock (Moder) closed this task as Archived.EditedDec 2 2022, 3:05 PM
Iliya Katueshenock (Moder) added a subscriber: Iliya Katueshenock (Moder).

Hello. This is not a bug. If the amount of data (mesh vertices) depends on time, then their speed cannot be calculated correctly (because the blender cannot know which data from one frame has passed into new data in another frame). So you can follow the directions in the answers from this report T101152: Geometry nodes: Instances Incorrectly Rendered with Motion Blur when deleting Instances.

(But I'm not sure if this will work for the mesh)