Defining Additional Viewable Compression Recipes
The pvschange recipe files that the Windchill Viewable Compression Utilities use are located under the <Windchill>\wvs\recipe sub-folder on the Windchill server. Out-of-the-box, this folder contains the following recipe files:
• pvschange.pvr—The master recipe file that defines the defaults for the pvschange execution (do not edited, unless under instruction from PTC).
• pvschange_for_illustration.rcp—The default recipe file that is used when no customized alternative viewable compression recipe is specified.
◦ Enables the conversion of only Tessellation, Wireframe, Curves and Cosmetic Geometry.
◦ Enables the compression of all shapes and faces to a single BLOB (binary large object) of compact data.
◦ Does not support conversion of Author States.
• pvschange_for_illustration_with_view_state.rcp
◦ Enables the conversion of all entity types except Analytical and Mass Properties
◦ Supports the conversion of Author States and hidden entities.
• pvsoptimize_for_illustration.rcp—Optimizes Creo View content for AR delivery for Creo Illustrate.
◦ Supports features of pvaroptimizer that are necessary for publishing to Creo View and Creo Illustrate
◦ Specified geometry is converted with all faces merged at body level.
◦ Accommodating Windchill multi-fidelity representation output.
◦ Enabling version downgrades with changes in outputPview values.
◦ Tessellation and Datum Quilts are converted, whereas data-heavy entities such as datums, mass properties, and analytical information are not converted.
◦ Supports the conversion of Author States, but Output Author States not enabled by default
◦ Generates only one fidelity.
◦ Generates PVZ files.
◦ Under > , unlike pvschange, Links and Geometry are selected, but hidden geometry and All layers are enabled are not selected.
• pvsoptimize_for_illustration_with_view_state.rcp— provides the same support as pvsoptimize_for_illustration.rcp, and also the following:
◦ Specified geometry is converted.
◦ Datums, Mass Properties, and analytical information are converted.
Simple customized variations of these out-of-the-box pvschange recipe files can be created using a text editor (not the Recipe Editor) and following the basic editing instructions in each recipe file. Users planning to shift from one conversion recipe to another, should be aware of the differences between the default recipe options.
Due to the complexity and interrelationships between the various recipe settings, PTC does not recommend performing recipe changes other than those described in the sample recipe file notes. Customers should check with PTC Technical Support before making any other changes to the recipe settings and perform extensive testing of the resulting recipes before deploying and using in production.