A command line utility to provide feedback about evaluated cache files.
|–help||produce help message|
|–file <string>||the input cache file name|
|–density <float>||density of generated fur|
|–samples <multi float>||a list of time samples that should be used to evaluate the cache|
|–bounding_box||return the bounding box of the evaluated cache|
We supply pgYetiGenPtc as a convenience to users who wish to generate point clouds for various shading effects, the command takes a generated .fur file and generates PTC files where the samples are more evenly spaced across the fur for more predictable results.
pgYetiGenPtc [arguments] input.fur output.ptc
|–help||produce help message|
|–area,a||include _area in the generated ptc for point based ambient occlusion|
|–radius,r||constant radius for generated point, overrides width of fur generated|
|–time,t||time within the cache ( ie. you may want 49.8 vs 50.0 to sample the ptc on shutter open )|
|–density,d||density of generated fur|
|–length,l||length of generated fur|
|–width,w||width of generated fur|
|–threads,t||number of threads to use, 0 for maximum|
Yeti is integrated into the rendering engines as a procedural DSO which has arguments that can be used to control the output of the generated fur by modifying the call to the DSO in the scene description (.rib, .ass, vrscene etc.)
Some are renderer specific, we’ve made note of this in the description.
|-density||Dynamically control the density of the generated geometry.|
|-length||Dynamically control the length of the generated fibres.|
|-width||Modulate the width of the generated fibres.|
|-verbose||The verbosity of the output.|
|-threads||The number of threads to use for graph evaluation.|
|-filename||The input fur cache file.|
|-frame||The current frame, this is an integer and used to load caches etc.|
|-samples||A comma separated list of float values representing the motion blur samples to be generated. (RenderMan, 3delight and Arnold only)|
|-motionBlockSamples||The actual sample times defined in the Renderman motion block statement. (Renderman and 3delight)|
|-curveChunkSize||Outputs fur objects as batches of RiCurve calls, this defines the size of the batches or 0 for all in one call. (Renderman and 3delight)|
|-center_samples||A boolean value which tells Yeti to output motion samples centered around frame 0 vs. the current frame. (Renderman and 3delight)|
|-frameRelativeSamples||A boolean value which forces Yeti to interpret the samples as frame relative, it will add the samples to the current frame value. (Arnold)|
|-setDeformTimeSamples||A boolean value which forces Yeti to set the deform_time_samples parameter on newly generated nodes using the specified samples. (Arnold)|
|-setFrameRelativeDeformTimeSamples||A boolean value which forces Yeti to set the deform_time_samples parameter on new generated nodes using the specified samples offset by the frame value. (Arnold)|
|-imageSearchPath||A semi-colon separated string of paths used to search for images. (textures etc.)|
|-dynamicHairTesselation||A boolean value to toggle between smooth or linear hair splines. (V-Ray)|
|-segmentLength||The pixel length used to determine the tesselation factor of smooth hair splines. (V-Ray)|
|-mode||Controls the curve style used for output firbres, 0 == ribbon, 1 == tubes, 2 == orientations (Arnold)|
There are two parameters that can affect how the deform_time_samples are output on a node in Arnold.
setDeformTimeSamples will use the values listed in the samples parameter as defined, whether or not frameRelativeSamples is used.
setFrameRelativeDeformTimeSamples will offset the values listed in the samples parameter by the current frame (ie. 1.5 and 2.0 on frame 2 would become -0.5 and 0), whether or not frameRelativeSamples is used.
At no point does Yeti reference any deform_time_samples values defined on the proc node.