I've sent a ticket, thanks.
On Wed, Apr 27, 2011 at 1:15 PM, Frank Rueter <[email protected]> wrote: > wow, that is annoying. I'm sure it used to show render times per frame in > previous versions when using verbose mode (I haven't checked in ages though, > so don't know when that disappeared). > I guess you could try afterFrameRender callbacks to build your own custom > system, but this should definitely be reported as a regression > > > > On Apr 28, 2011, at 6:40 AM, [email protected] wrote: > >> Hi, just wanted to check what you guys use to check render times, >> performance and metrics (I need to test on the local machine on a gui >> session). Verbose mode does not seem to report it, and -P mode doesn't >> either (only individual nodes, it seems). I have tried to use timeit >> through python on a nuke.execute, but I haven't been able to make it >> work. Your ideas are much appreciated, thanks. >> _______________________________________________ >> Nuke-python mailing list >> [email protected] >> http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python > > _______________________________________________ > Nuke-python mailing list > [email protected] > http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python > _______________________________________________ Nuke-python mailing list [email protected] http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python
