The command line renderer does not render user presets. It only renders presets that are hard-coded or "baked in" to the filter. If I create an xml file referencing a filter with a preset number higher than what is hard-coded in the filter, and the preset number exists as a user preset but not hard-coded, it does not render. It just defaults to the first hard-coded preset.
This is the case in the newest Filter Forge version/command-line renderer at this writing, version 9.
This defeats the purpose of user presets as far as the command-line renderer is concerned. It would be great if it found the user preset file and dynamically grabbed the preset from that.
Also, preset numbering in scripting is zero-indexed, which is counter-intuitive. I would prefer the preset numbering start at 1, not 0.
You refer to the prophecy of the pastry that will bring balance to the Force. And you believe it's this...donut?
