|
So I’ve been messing around with the command line flags “-console -verbosePython” to enable debug spew for some python scripts. Is there something in my scripts that I need to do (such as scene eval) to make the console window update every time I print something to it? Depending on the scripted task, the output window seems to either update periodically, in one huge dump, or sometimes not even at all. I’ve also noticed that the console window does not appear to display any output messages until the python editor has been opened once.
Does anyone have any advice on best practices or tips to getting a better real-time performance out of the console window?
Thanks
-csa
|
|
|
|
To answer some of my own question for others…
There is a command called FBTrace() which allows you to print information directly to the console without having to first open the Python Editor. Seems to work great, and appears ‘realtime’ and not dependent on scene calls to decide when it is time to purge print information to the python window.
Which leads me to ask, what events cause the python editor output window (where the print statement outputs) to trigger an update?
-csa
|
|
|