RBD Procedural Motion Blur
1428 3 1-
- jarjarshaq
- Member
- 65 posts
- Joined: Feb. 2016
- Offline
I've set up a super simple rbd procedural with Point Location parm set to "File Cache". I'm trying to get geo motion blur working and attempted to use a lop cache. However, it's returning a lot of warnings complaining about varying attributes. Is it possible to get non-velocity based motion blur with the rbd procedural?
Edited by jarjarshaq - Feb. 19, 2025 14:37:26
-
- jarjarshaq
- Member
- 65 posts
- Joined: Feb. 2016
- Offline
I have also attempted to read the points from the sop by setting the Point Location to "Primitive" as outlined in the help doc:
https://www.sidefx.com/docs/houdini/solaris/houdini_rbd_procedural.html#solaris-setups. [www.sidefx.com] However, no luck getting geometry blur to work.
https://www.sidefx.com/docs/houdini/solaris/houdini_rbd_procedural.html#solaris-setups. [www.sidefx.com] However, no luck getting geometry blur to work.
-
- npetit
- Staff
- 445 posts
- Joined: Feb. 2008
- Offline
Houdini Procedurals do not currently support geometry blur, only velocity blur.
The RBD Procedural's "preview procedural" toggle previews the result in the viewport - it does this by writing the result of the procedural directly to the affected prims' various attributes. This only happens when viewing interactively and is disabled when writing to disk, leaving the procedural execution to husk, at render time.
Adding a cache LOP after the procedural is therefore misleading and results in the warnings you see since the procedural preview just writes values as default values, not timesamples.
If it was to write timesamples that you could cache, it'd defeat the purpouse of using a procedural in the first place since it'd bloat your usd cache with deforming point positions, normals etc, effectively "baking in" the results of the procedural.
The RBD Procedural's "preview procedural" toggle previews the result in the viewport - it does this by writing the result of the procedural directly to the affected prims' various attributes. This only happens when viewing interactively and is disabled when writing to disk, leaving the procedural execution to husk, at render time.
Adding a cache LOP after the procedural is therefore misleading and results in the warnings you see since the procedural preview just writes values as default values, not timesamples.
If it was to write timesamples that you could cache, it'd defeat the purpouse of using a procedural in the first place since it'd bloat your usd cache with deforming point positions, normals etc, effectively "baking in" the results of the procedural.
-
- jarjarshaq
- Member
- 65 posts
- Joined: Feb. 2016
- Offline
-
- Quick Links

