[Bf-committers] New feature: Console output space type
(requestfor input).
Toni Alatalo
antont at kyperjokki.fi
Thu Apr 20 19:28:44 CEST 2006
On Thursday 20 April 2006 19:05, Ewout Fernhout wrote:
> > 1) You killed the output window.
> it (although I agree with others that it should be optional by command
> line argument).
please be sure to also make it so, that in -b background the normal stdout
option is enabled by default.
i also like that this new feature is there, but am not sure if it should be on
by default or not (having the output of a crashed session not disappeared is
a great advantage of a out-of-blender console, as Chris(?) already noted. and
copypaste, which of course should work from blender too).
perhaps the default should be that both normal stdout, so on win32 the extra
window (on macosx it goes do /dev/console that is viewable with the
console.app), and the new in-blender console show the output (not having it
visible in Blender hopefully does not cause a slowdown) - then a runtime
option to disable the normal stdout.
> Ewout
~Toni
BTW: some of you might be interested in knowing that we used the console
output quite extensively in making the Elephants Dream .. for debugging, but
also for making render statistics. the farm system i made gathered all the
blender stdouts from all the nodes to a single file / renderjob, files like
this: http://www.blender.org/~antont/04_09
and Nathan wrote a parser for those files,
http://www.blender.org/~antont/renderstats.py
i dont have the actual stats at hand now, but now that the DVD masters are
done(!), i guess publishing stats and other stuff on-line has a chance to
begin happening..
More information about the Bf-committers
mailing list