Fixing Filter Problems
When a filter is submitted to the Filter Library, the Submit Wizard checks it for problems. If the filter has one or more problems that prevent it from being accepted to the Library, the Wizard lists them on the Problems page:
Imported lighting environments used
This message means that the filter being submitted uses custom HDRI lighting environments that were imported using the HDRI Import dialog. Such filters cannot be accepted to the Filter Library – to use such filters, the users would also need the custom environment file. To avoid the problem, all presets of the filter must use only the lighting environments supplied with Filter Forge. To fix the problem, repeat these steps for each preset, including the default one:
- Open the Presets tab in Filter Controls and apply a preset.
- Switch to the Lighting tab and set Environment to one of the default environments.
- Go back to the Presets tab and update the same preset.
No control components
Any filter submitted to the Filter Library must have at least one control component. To fix this problem, open the filter in the Filter Editor and add one or more control components. Note that in order to add controls to the Settings tab, control components must be connected to the Result component, directly or indirectly.
Too many control components (100 is the maximum)
The filter being submitted uses too many control components. To fix this problem, open the filter in the Filter Editor and delete some control components until their number is below the limit.
Untitled control components (marked with red)
One or more control components in the filter have no name – such components are displayed as Untitled in the Filter Editor. To fix this problem, open the filter in the Filter Editor and name these control components appropriately.
Unconnected required inputs (marked with red)
There are components in the filter that have unconnected required inputs. Examples of required inputs are Source in the Blur component and Height in the Result component. If a required input of a component is unconnected, the component is unable to perform its function – for example, the Blur component cannot operate without the source picture. When unconnected, the required inputs are marked with red in the Filter Editor. To fix this problem, look for components with inputs marked with red, and connect other components to these inputs.
Control warnings (red warning signs near controlled inputs)
One or more of the control components in the filter have control warnings. These warnings look as red exclamation marks near the inputs controlled by control components. Filters with such warnings are not accepted to the Filter Library because these filters may have non-intuitive controls. To fix this problem, replace the control components that cause the warnings with more appropriate controls – see the Control Warning section for more information.
Render Maps must be turned off for every preset
One or more of the filter's presets were saved with a non-default Render Maps Menu setting. In order to be accepted to the Filter Library, all presets in the filter must be saved with the Render Maps menu set to Off. To fix this problem, repeat these steps for each preset, including the default one:
- Open the Presets tab in Filter Controls and apply a preset.
- Choose Filter > Render Maps from the menu and make sure that Off is selected.
- Go back to the Presets tab and update the same preset, if necessary.
Duplicate presets found
Two or more of the filter's presets are identical to each other. Since duplicate presets have no value to the filter users, the Filter Library requires all presets to be unique. To fix this problem, find and delete the duplicate presets.
Too many presets (20 is the maximum)
There is a limit on the number of presets for filters submitted to the Filter Library. This limit was imposed because filters with a large number of presets slow down the queue on the rendering server which produces preview images for filter's web pages. To fix this problem, simply delete some presets until their number is below the limit.
Duplicate control names found (unique names required)
Two or more control components in the filter have duplicate names. This may occur due to the auto-naming of control components when they are connected to inputs with identical names. To fix this problem, open the filter in the Filter Editor, find the control components with duplicate names, and rename them.
Two-position IntSlider control found (replace it with a Checkbox)
One or more IntSlider controls in the filter have the range of 1 to 2, thus making it a two-position slider. Such short-ranged IntSliders can be replaced with Checkbox controls which are more intuitive for filter users. To fix the problem, open the filter in the Filter Editor, find the IntSlider in question and replace it with a Checkbox.