That could be the name we use for our project!
Arne, I toyed with starting indigo from commandline, and it seems to kind of works:
$xmlFile = "1.xml"; // requires 1.xml in indigo-homedir
$threads = 1;
string $cmd_string = " cmd /k " + "cd \"d:\\program files\\indigo_07_test5\" && d: && dir && indigo.exe " + $xmlFile + " -t " + $threads + " && pause";
print ("CHECK\ncommand string: " +$cmd_string +"\n\n");
system ("start" + $cmd_string);
System is still complaining about inifile, but starts to render nonetheless.
(to read a nice piece of garbage, either check my addons to mtiGen or refer to cmd /?, I don't know what I like more. hehehehe.)
There seems to be a power-drawn statement that is pretty cool and that has something like <overall luminous efficacy> that accompagnies it.
Anybody know what it does, and what should be our default for it?
I found out that with a gain of 1.0, you have to set <overall_luminous_efficacy> only to 1000000000000 to be well visible in sunlight. ???
<overall_luminous_efficacy> 20 </overall_luminous_efficacy>
If the <include> statement works as someone pointed kindly out,
we may have a problem hooking Alias-Shadernames up with static mti-Library-files. How do we cope with this?
One stomach turning method would be to rename all the shaders to correspond to the <material>statements of the lib on the fly while exporting, and changing them back later on.
I don't like that really much, what do you guys think (and gals out there, by the way, or do they know a better way to spend there time )
Is F-scale in any way influencing rendering speed (similar to a real camera)
I guess not, and then 50 is a pretty reasonable default, otherwise, let's check it...