03-22-2013, 05:59 PM
Oort,
Update ... A "bigger" job render time went from 33s (-t 1) to 12s (-t 4). There's some overheads on setting up, but these soon become insignificant (especially on your 3hr job !?!) - so forget about them.
Autodetect Threads: Tried to set "-t -1" as an option in preferences but that fails with :
"ERROR: option --threads has no value"
which, since the "-1" looks like a parameter switch, is no surprise!
But adding the parameter: <threads ival="-1"/> to the XML file <render> section (and drag/drop the XML file onto the Yafa..exe) works. It gives same behaviour as "-t 4" on my i5 system.
So: You could set this Autodetect value as default in the XML output - like Blender. It could then be overridden if necessary by "-t" on the command line string (I believe).
In the meantime, my preferences are set to "-t 4".
Wegg,
In total agreement about how gob-smacking the height mapper is.
Have you already tried putting "-t 6" in the preferences to use all of your 6-core system?
greytery
Update ... A "bigger" job render time went from 33s (-t 1) to 12s (-t 4). There's some overheads on setting up, but these soon become insignificant (especially on your 3hr job !?!) - so forget about them.
Autodetect Threads: Tried to set "-t -1" as an option in preferences but that fails with :
"ERROR: option --threads has no value"
which, since the "-1" looks like a parameter switch, is no surprise!
But adding the parameter: <threads ival="-1"/> to the XML file <render> section (and drag/drop the XML file onto the Yafa..exe) works. It gives same behaviour as "-t 4" on my i5 system.
So: You could set this Autodetect value as default in the XML output - like Blender. It could then be overridden if necessary by "-t" on the command line string (I believe).
In the meantime, my preferences are set to "-t 4".
Wegg,
In total agreement about how gob-smacking the height mapper is.
Have you already tried putting "-t 6" in the preferences to use all of your 6-core system?
greytery