Preset Management At Rollout Level¶
Available in Krakatoa v1.5.0 and higher
Overview¶
- Krakatoa has always provided a dedicated Presets and History Rollout for saving, loading and browsing preset files saved either manually or automatically after each rendering.
- This enhancement to the existing system provides a small [<>] button to the left of the Help button in every relevant rollout.
- Clicking or right-clicking this button opens a menu which provides direct saving and loading access in the context of the current rollout.
- This new workflow simplifies the saving of specific settings because
- You don’t have to navigate to and expand the Presets and History rollout while you can still use the new menu to save all rollouts if desired.
- Only the current rollout is checked for saving, which significantly reduces the number of clicks to disable all other rollouts if only one rollout is to be saved.
Main Options¶
Save this Rollout’s Controls as Preset…¶
- Selecting this option will open the Save Preset dialog, but with all top-level checkboxes unchecked except for the one for the current rollout.
- You can freely change the checked state of all rollouts to save more or less than initially suggested, but in the typical case, if you wanted only your current rollout’s controls (say, Main Controls) to be saved, you would click on the [<>] button of the Main Controls rollout and save a preset.
- The default preset file name will consist of the name of the current Max file and the name of the current rollout separated by an underscore. You can enter any name you want.
- A new drop-down list containing all existing preset names will appear to allow you to select an existing preset name and overwrite it.
Load this Rollout’s Controls from Preset…¶
- Selecting this option will open the Load Preset dialog, but with all top-level checkboxes unchecked except for the one for the current rollout, if present.
- Note that if a Preset file was saved with just one rollout checked, only that rollout will be listed in the Load Preset dialog.
- If the Preset was saved with multiple rollouts, you can check any available rollout in the preset to load it, too.
- The new Filter Pattern text field will be automatically set to * wildcard plus underscore and the name of the current rollout. This will cause the drop-down list to show initially only Presets saved from the current rollout. By changing the pattern or clearing it, you can populate the drop-down list with others or all Presets.
- If the pattern does not match any Presets, the drop-down list will be empty and the LOAD PRESET button will be disabled.
- The file selected in the drop-down list will be the one to be loaded when the LOAD PRESET button is pressed.
More Options¶
- In addition to the above listed main options, a sub-menu provides some more loading and saving shortcuts:
Save All Controls As Preset¶
- This option is equivalent to the Save Preset button in the Presets and History rollout, but is faster to access as it does not require the navigation to and the expanding of another rollout.
Load All Controls As Preset¶
- This option is equivalent to the Load Preset button in the Presets and History rollout, but is faster to access as it does not require the navigation to and the expanding of another rollout.
Load this Rollout’s Content from History…¶
- This option is similar to the Load From History button in the Presets and History rollout, but is faster to access as it does not require the navigation to and the expanding of another rollout and has only the current rollout checked in the tree view, reducing the number of clicks needed to disable all other rollouts.
- The Filter Pattern field will be automatically set to the name of the current Max file, resulting in only History records from the current session to be displayed in the drop-down list. You can edit the Pattern or clear it completely to show others or all History records.
Load All Controls As History¶
- This option is equivalent to the Load From History button in the Presets and History rollout, but is faster to access as it does not require the navigation to and the expanding of another rollout.
