Hello, in the sneak peek video there's a mention about an enhanced wedging workflow.
Could you tell us what's new in this regard in hou 18?
Very curious about it
cheers
Hou 18, enhanced wedging workflow?
2538 4 1- Andr
- Member
- 900 posts
- Joined: Feb. 2016
- Offline
- adrianmeyerart
- Member
- 36 posts
- Joined: July 2013
- Offline
- tpetrick
- Staff
- 578 posts
- Joined: May 2014
- Offline
The wedging enhancements are based on the discussion in this thread: https://www.sidefx.com/forum/topic/65734 [www.sidefx.com]
The wedge node is able to operate in a “push” mode, where values are pushed from the wedge to target parameters. When this option is enabled the wedge tracks the old parm values and can restore them on deselection or with a button press. You can also recapture/stash the current parm values onto the wedge node. These changes are actually backported to 17.5 as well.
A new feature in 18.0 that relates to wedging that isn't in 17.5 is that batch work items can now have different attributes per subitem, for example when using a ROP Fetch, ROP Geo, etc in batch mode. This means its possible to wedge attribute or parameter values per-frame when cooking batches. Previously the attribute values were shared for the whole batch so the wedge values had to be constant for the whole frame range.
The wedge node is able to operate in a “push” mode, where values are pushed from the wedge to target parameters. When this option is enabled the wedge tracks the old parm values and can restore them on deselection or with a button press. You can also recapture/stash the current parm values onto the wedge node. These changes are actually backported to 17.5 as well.
A new feature in 18.0 that relates to wedging that isn't in 17.5 is that batch work items can now have different attributes per subitem, for example when using a ROP Fetch, ROP Geo, etc in batch mode. This means its possible to wedge attribute or parameter values per-frame when cooking batches. Previously the attribute values were shared for the whole batch so the wedge values had to be constant for the whole frame range.
- EricSheng
- Member
- 159 posts
- Joined: Feb. 2018
- Offline
- Andr
- Member
- 900 posts
- Joined: Feb. 2016
- Offline
-
- Quick Links