Please consider the following code, and its output. Seemingly has nothing to do with rendering, why is it affected by whether or not the render scene dialog is open?
renderSceneDialog.close()
ts = timestamp()
display (bitmap 300 300 color:red)
format "Without render scene dialog: % ms
" (timestamp()-ts)
renderSceneDialog.open()
ts = timestamp()
display (bitmap 300 300 color:red)
format "With render scene dialog: % ms
" (timestamp()-ts)
Output:
Without render scene dialog: 41 ms
With render scene dialog: [B]719 ms[/B]
I wonder if it has anything to do with the legacy ‘Cancel’ capabilities of the Render Scene Dialog…
Where’s Denis with some win32 code that disables updating of the render scene dialog
Is this in pre-max2012? I remember having an issue like this in 2010… it’s not exactly like your problem but it could be related. Rendering via the render dialog keep hanging for a few seconds on the the ‘translating scene’ stage (or so it seemed), using the render() command in the listener it started instantly…
It is in max2009. I will try to test in other versions as well.
Scratch that… tried with LockWindowUpdate windows function and it doesn’t help…
you might wonder … but that are my results …
Without render scene dialog: 57 ms
With render scene dialog: 28 ms
okay a second cycle was a bit different
Without render scene dialog: 21 ms
With render scene dialog: 30 ms
might depend on the current active renderer ?
or net rendering option active ?
UPDATE:
i tried everything but can’t get my times above 30 ms now
( this is max 2009 x64 by the way … )
That is interesting… tried with all the renderers I could, and network on/off, but similar results.
Also on max 2009 x64.
Can’t reproduce here, also on Max 2009 x64…
Do you have any render dialog or rendering callbacks? Sounds like a 3rd party tool (script or plugin) causing something weird to happen.
-Eric