Eliezer Carvalho VFX I would like to be able to see a single procedural node textures in the viewport to adjust simple things like size of noise, it is very helpful.
Thanks.
That thing is missing in Houdini even today, indeed. Let's see if it changes in H20 with the upcoming Vulkan viewport. Crossed fingers!
jarenas Maybe they are going the classic product launch way, with event first and later the sneakpeek as a launch event short recap. Soon enough we will see anyway
I vastly prefer this route. When they did a "sneak peek" video for H19, that clip showed pretty much everything from the presentation, and made the presentation feel a bit weak. Not the release, mind you, because 19 is an amazing update, but the excitement from watching the presentation itself was definitely deflated somewhat.
I disagree completely. The official presentation is always very powerful and informative. And the sneak peak is like a golden visit card for the whole thing. Like any interesting thing, you tease people first. IMHO
A reference to the node or file this folder imports its contents from, when Import settings is on.
The source can be either a sub-node, specified using op:node_path, or an external dialog script, specified using file:file_path. For example, to import parameters from a node named torus1 inside the asset, use op:torus1. To import from a node named sphere1 inside an object named geo1 inside the asset, use op:geo1/sphere1.
Token
The name of the item to import from the node/file, when Import settings is on. You can import a folder, an import block, or all the parameters from the source.
To import a folder, use the Name of the folder.
Tab sets are sibling folders that share the same Name. To import the all tabs in a tab set, use the shared Name as the token. To import a single tab from a group, use the Name of the tab set, followed by a colon ( : ), followed by the Label of the folder you want to import.
For example, to import a tab named folder1 with the label "Shading", the token would be folder1:Shading.
To import an import block, use the special token importblock, followed by a colon ( : ), followed by the Label of the import block you want to import.
To import all the parameters from the source, leave the token blank.
To get the name of a folder, select the source node, and in the parameter editor, open the Gear menu and choose Edit Parameter Interface. Then select the folder in the Existing parameters and check the contents of the Name field under Parameter description.
Mask
Only import parameters matching this pattern, when Import settings is on.
Excluding a multiparm will not automatically exclude any existing instances (you should craft the pattern so it excludes both the "parent" multiparm name and instance names).
This tool can fix flicker on VDBs, Flips, etc. take a look. Volumetric Temporal Deflicker | HDA Digital Asset Download https://vimeo.com/324762774 [vimeo.com]
phtj I am writing a paper where I discuss houdini… I am wondering if anyone can tell me when the first version of houdini came out? Also, what is the history of houdini - did it start out as open source? Also, are there any patents for the dataflow approach?
i updated wikipedia with a table of Houdini history… take a look.
TR 1950X here, with H80i V2 premium liquid cooling in place.. Linux System, 32Gb ram at 3200Mhz in just dual channel, not 4 channel:
FLIP scene, just 20 seconds to write to disk! (very sparse use of cores…) PYRO one, 5min 45s (and not using all cores fully, the graphic of cpu usage is very ondulated) GRAIN stuff, 1min 32s (again, no using all cores fully)
anyway, i see very nice results here, but still a lot of room for improvement for more full usage of cores (in all algorithms) and multithreading. maybe Houdini 17? maybe multi GPU support too?
friedasparagus So for that we just need to check for equality between the current sample index and the relevant value in the original file. Does this do it?
EDIT: blurp… didn't remove the sticky note.. please ignore
