Ok. Thank you for your input.
..and here's my feedback.
vansan wrote:
- Every time I export to XML (no need for OBJ and 3ds though, imho) I wish files to be stored in a separate folder(scene name would be ok).
I'm not sure if it is a good idea. You see Indigo saves images into "renders" folder. The folder has to be in the same place as the xml file. Also ini has to be in the same place. So if i would make a separate folder for each scene, then i would have to include inifile.txt and "renders" folder for each project separately. For me it seems more messy than it is now. Also it can be confusing what ini to edit exactly.
What do you mean by "no need for OBJ or 3DS"? No need for separate folders for them? If you have models with the same name in different scenes, then things can be rendered wrong when using resume.
vansan wrote:
- As Time Output just copies Common rendering properties visa-versa - there is no need to place it in the script menu. Just leave a spinner of desired rendering time, the update speed and saving intervals.
- No need for "Output size" group.
More buttons - more human errors, imho.
I never use standard Rendering panel while working with Indigo. I don't want to jump between different panels. I like to access all the common parameters right from the exporter panel. So sorry.. those will stay.
vansan wrote:
- Export EXR and IGI can be always ON, and stored in the same folder as the exported files in subfolder "images".
Nope. IGI can't be on by default. If the export doesn't go well, then exporter(max) may run into infinite loop while searching for igi file. You see..it waits until Indigo saves the igi first time an automatically links it with the scene. If Indigo never saves, then it continues to wait. The warning message isn't there just for fun
But...i'm planning to add "Save Settings As Defaults" button at some point. Then everybody can use their own defaults.
vansan wrote:
- No need for tonemappeing rollout for me - it's better be done in violet or another exr-compatible software.
I agree, but a lot of users still use it. Also good for animation. Don't need it? Just close it.
vansan wrote:
- White ballance - please, add a color picker(or a color temperature gradient as in BlenderEmitter mat interface) there if possible, it's really hard to guess what's "F7" or "C" for a newbie(me too
).
Nice idea, but i dont have a clue how to do that. Any thoughts? Indigo uses those wb's as parameters. If you select F7, then it is defined as F7 in XML. I'm not an expert either. I don't know how to link it with color picker.
vansan wrote:
- Procedurals resolution, 1024x1024 ore 2048x2048 by default(no stretching), please?
Can you actually see any stretching visually? I mean if you render lower resolution images. For larger images you would sure have to increase the procedurals resolution. I could use 512x512 by default. Anyway.. you can use what ever you want when i add that save as defaults button.
vansan wrote:
- Number of threads ("CPU threads" is better for me
)- to be taken from ../Indigo/inifile.txt.
I can do that
I just want to say, that most of the things are there with a reason. I didn't just randomly throw in some buttons and settings.
But i appreciate your feedback. Keep the ideas coming !!
. So please guys, stop asking the source. I will release it some day, but not now.
