Hi,
I’ve been working on my script called Renderitis and wanted to share the progress here. It’s a script to store, edit and share renderpresets. It stores the settings in an xml-file and exposes them through a gui. The user can edit, apply and record new presets.
A big challenge with this is to store the rendersettings in such a way that they appear in the gui logically and recognizable. This means I need to store the type of the value together with the name of the value. For “normal” types this isn’t so much of an issue: boolean, float, integer and color can all be detected automatically. But rendersettings where the user is presented a dropdown with multiple options need manual work to recreate.
So I’ve split the xml-files in two: one where information about the maxversions, the settings, rendersettings and rollouts are stored and a second one where the presets are stored with the actual values. The first file is created by me and consists of a whole lot of manual work. Each new renderengine needs a lot of checking and adjusting. The second file is created automatically by adding or adjusting presets through the gui.
I’m curious what you think and if you’d expect features not described here. Also if someone has tips on capturing rendersettings from a renderengine more easily I’d be very happy!
You can download the script from my blog.
BTW, I’ve created this script earlier and written about it 1.5 years ago. I decided to dust off the idea and used my mildly improved skills to have another go at it. Previously I hadn’t released the script, but now it’s available for everybody to use.
Browse the available presets in the script and create some yourself.
You can adjust rendersettings directly in the script.