Weird rendering of points with velocity attribute #103918
Operating system: Linux-5.15.0-58-generic-x86_64-with-glibc2.35 64 Bits
Graphics card: NVIDIA GeForce RTX 2070 Super/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 525.60.13
Broken: version: 3.5.0 Alpha, branch: master, commit date: 2023-01-16 11:41, hash:
also broken: 3.4.1, 3.3.2
Short description of error
Shading of points is totally broken in Cycles when using a "velocity" attribute. I noticed this during a project that needs motion blur on point clouds.
At first I thought it was something broken with the incoming Alembics (I use 2 to work around the current shortcomings of importing attributes on Alembic point clouds following this tutorial by Entagma ).
But when I started to boil down my scene to create an "as simple as possible repro scene" I noticed that something is seriously broken, at least with points, Geometry Nodes and motion blur in Cycles.
I'm currently trying to work around by using instanced spheres instead of points but first results don't look too good either.
The error itself is that as soon as there's a "velocity" attribute on points and I use Motion Blur during rendering, the shading completely breaks. Even if the velocity vectors are at 0, 0, 0.
Notice the "velocity" attribute which is basically set to no motion whatsoever:
The render doesn't become better if I e.g. set it to any other values.
Exact steps for others to reproduce the error
- Open the attached blend file
It's just some points distributed on a grid
- Press F12 to render without MB -> all fine
- Check "Motion Blur" and re-render -> weird result
I can confirm behavior. But the velocity attribute must be used for blurring. And it's coming through. Just not sure what it should look like for velocity close to 0...
Thanks for confirming. A velocity vector of length 0 should result in no blurring at all. If you e.g. in my blend file manually set the velocity vectors to 0, 0, 10 (which should result in vertical motion blur), it looks like this
So there is a vertical blur but the spherical shape of the points is totally gone. In my renderings above you can also see that the size of the points gets visually smaller, even if there should be no blur.
Changed status from 'Needs Triage' to: 'Needs Developer To Reproduce'
Based on the description I don't think this is related to geometry nodes directly. Thanks for the report.
I did test this in 3.4.1 and current master, and would like to note that with CPU rendering the issue doesn't occur.
(My GPU is too old to be used with Cycles.)
@SteffenD and @mod_moder, can either of you please re-test using CPU rendering to see if this is GPU only?
Changed status from 'Needs Developer To Reproduce' to: 'Confirmed'
Thx @EAW ! Now i see that this bug only for GPU render
Indeed, CPU rendering looks fine. Optix and CUDA are broken.
This bug bit me again today. I had already forgotten about it, but it's annoying as hell.
Same problem here.
And I agree, this is dangerous for production and it's very annoying.
I don't see this bug assigned to anyone, so I'll mention @brecht because I think it's mainly related to Cycles and the Point Cloud implementation :)
No due date set.
No dependencies set.
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?