Page MenuHome

Object with a Particle Instance Modifier does not generate Vector Map or Motion Blur
Closed, ArchivedPublic

Description

System Information
Operating system: Windows-10-10.0.18362 64 Bits
Graphics card: Quadro P6000/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 436.02

Blender Version
Broken: version: 2.80 (sub 75), branch: master, commit date: 2019-07-29 14:47, hash: rBf6cb5f54494e
Worked: (optional)

Short description of error
The Title says it all. If an object has a Particle Instance Modifier on it, it does not generate a Vector Map nor does it Motion Blur.

Exact steps for others to reproduce the error

  1. Create a Particle System on the default cube (I used a plane for clarity in my demo scene).
  2. Create a new object (I used a cone)
  3. Bake the the Particle System to a cache (for ease of scrubbing the timeline)
  4. On the new object, cone, add a Particle Instance Modifier
  5. Select the emitting object (cube) and choose the particle system (default is ParticleSettings for me)
  6. Any combination of modifier settings is fine; for clarity I checked on Regular and Size and then adjusted the size to be smaller in the Render > Scale section of the ParticleSettings system.
  7. Switch to Cycles in Render Settings
  8. Turn on Motion Blur in Render Settings
  9. Turn on Vector in Layer passes
  10. Scrub to a point where you see particles in your timeline moving
  11. Turn on Use Nodes in Compositor
  12. Render image
  13. In Compositor you can drag Vector to your Composite Image input. You'll note no image appears, nor does any Motion Blur appear.

Attached is a demo scene, with a few Forces to move the system around for clarity's sake.

Event Timeline

Philipp Oeser (lichtwerk) closed this task as Archived.Jan 8 2020, 5:59 PM
Philipp Oeser (lichtwerk) claimed this task.

Hi there and thx for the report! (sorry this has been lying around for so long...)

I believe this is a limitation of how the Particle Instance modifier works.
It is not really different objects [with different matrices to read motion from], blender creates one big mesh instead.

And this resulting mesh is changing vertex count all the time (so deformation motionblur wont kick in)
In a way, it could probably be made working using something along the lines of rB10b0e33de1b9: Cycles: add support for motion blurring of fluid meshes., but this is really more like a feature request than a real bug.

So the issue reported here is a request for modified/improved behavior and not a bug in current behavior. Closing as this bug tracker is only for bugs and errors.
For user requests and feedback, please use other channels: https://wiki.blender.org/wiki/Communication/Contact#User_Feedback_and_Requests
For more information on why this isn't considered a bug, visit: https://wiki.blender.org/wiki/Reference/Not_a_bug