1
$\begingroup$

I am trying to add "artificial" motion blur to a static object via manipulating the "velocity" attribute in geometry nodes. I've tried 4 cases (posted screenshots):

  1. mesh + motion blur option (case 1): works as expected

  2. points + motion blur option (case 2): works as expected

  3. mesh + vector pass - vector blur (case 3): works as expected

  4. points + vector pass - vector blur (case 4): completely ignores direction of the velocity vector and just points towards the center of the object (scene maybe?)

Has anyone else encountered this? Is this expected behavior (if so, I'm curious what the logic behind it is, if you could help) or just a bug?

Case 4: The result of rendering points with a "velocity" attribute; the vector blur direction points outwards from the center of the object

The result of rendering points with a "velocity" attribute; the vector blur direction points outwards from the center of the object

Improve this question
$\endgroup$
1
  • $\begingroup$ I've tested this on some points generated in Geometry Nodes 4.5.3 LTS and I got the same result. I guess Blender doesn't calculate Velocity for any instanced points with no real Geo. It does however calculate proper vector data on instanced geometry. Proper data requires vertices, edges, or faces. $\endgroup$ Commented Nov 6 at 19:52

0

Reset to default

You must log in to answer this question.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.