PDA

View Full Version : Why does RenderScene Dialog make everything so slow?


lo
05-31-2011, 06:31 PM
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\n" (timestamp()-ts)

renderSceneDialog.open()
ts = timestamp()
display (bitmap 300 300 color:red)
format "With render scene dialog: % ms\n" (timestamp()-ts)
Output:
Without render scene dialog: 41 ms
With render scene dialog: 719 ms

DaveWortley
06-01-2011, 09:11 AM
I wonder if it has anything to do with the legacy 'Cancel' capabilities of the Render Scene Dialog...

lo
06-01-2011, 09:19 AM
Where's Denis with some win32 code that disables updating of the render scene dialog :)

jonadb
06-01-2011, 10:01 AM
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..

lo
06-01-2011, 10:06 AM
It is in max2009. I will try to test in other versions as well.

lo
06-01-2011, 10:45 AM
Where's Denis with some win32 code that disables updating of the render scene dialog :)

Scratch that... tried with LockWindowUpdate windows function and it doesn't help...

spacefrog
06-01-2011, 11:34 AM
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 .. )

lo
06-01-2011, 11:52 AM
That is interesting... tried with all the renderers I could, and network on/off, but similar results.
Also on max 2009 x64.

noouch
06-01-2011, 02:21 PM
Can't reproduce here, also on Max 2009 x64...

PiXeL_MoNKeY
06-01-2011, 02:44 PM
Do you have any render dialog or rendering callbacks? Sounds like a 3rd party tool (script or plugin) causing something weird to happen.

-Eric

lo
06-01-2011, 03:03 PM
I tried removing all maxscript callbacks and didn't help. Probably a plugin doing something under the hood.

Thanks.

PiXeL_MoNKeY
06-01-2011, 03:12 PM
Try starting Max with a standard only plugin.ini (no 3rd party paths included) using the -p command-line parameter and see if you get the same result. That should at least point out if it is a 3rd party tool or something possibly system related.

-Eric

lo
06-01-2011, 03:25 PM
will try, thanks

lo
06-01-2011, 04:53 PM
Unfortunately, same result (though nice seeing max start up quickly for a change :D )

Maybe it's a Vista thing...

jonahhawk
06-02-2011, 05:09 AM
Max 2012, XP 64
First time was slow: 93ms/16ms. Second time, after closing the render scene dialog and the two bitmaps, was the identical. Repeated many times and still 16/16 or 16/15.

Then I closed Max down completely, restarted and ran the code again... and got 16/16...:eek:

I restarted Max a second time and got 15/16.

I'm too tired (and confused) to reboot and try to get something close to 93/16 again...

denisT
06-02-2011, 06:07 AM
Output:
Without render scene dialog: 41 ms
With render scene dialog: 719 ms

is it repeatable? i know situations when some opened dialog slows down some operations. but this one sounds new for me. if so, why do you need to keep the render dialog opened?

lo
06-02-2011, 07:13 AM
is it repeatable?Yes, happens every time, in the range of 500-1500ms.


why do you need to keep the render dialog opened?I don't have to, but it is too slow to close and reopen it for every action of the user.

RappyBMX
06-02-2011, 02:51 PM
Without render scene dialog: 180 ms
With render scene dialog: 414 ms
Without render scene dialog: 139 ms
With render scene dialog: 310 ms
Without render scene dialog: 132 ms
With render scene dialog: 250 ms
With render scene dialog: 285 ms
Without render scene dialog: 121 ms
Without render scene dialog: 124 ms
Without render scene dialog: 113 ms
With render scene dialog: 233 ms
With render scene dialog: 244 ms

a little difference... max 2011 x64... AMD processor < which i believe it's the root to the slow UI... (every max version from 9-2012... sub object level change takes ages :( )

reecpj
06-08-2011, 01:31 PM
Yikes! I get:
1.
Without render scene dialog: 66 ms
With render scene dialog: 1278 ms
2.
Without render scene dialog: 119 ms
With render scene dialog: 1384 ms

That can't be good!

denisT
06-08-2011, 02:13 PM
Without render scene dialog: 31 ms
With render scene dialog: 51 ms

max 2010, 64-bit

i have no idea what can cause the slowing down.

lo
06-08-2011, 03:04 PM
Yikes! I get:
1.
Without render scene dialog: 66 ms
With render scene dialog: 1278 ms
2.
Without render scene dialog: 119 ms
With render scene dialog: 1384 ms

That can't be good!

Finally, proof I am not insane.

denisT
06-08-2011, 03:15 PM
Finally, proof I am not insane.

you can try to check messages sent to Render Dialog Window using Spy++ ...
but I don't see anything odd.

denisT
06-08-2011, 03:20 PM
Finally, proof I am not insane.

could you try to check open time of Material Editor for example with and without opened Render Dialog?

lo
06-08-2011, 04:41 PM
could you try to check open time of Material Editor for example with and without opened Render Dialog?

around 100ms for both. Interesting.

I've worked around this problem in the meantime, so it remains only as a curiosity for me.

PiXeL_MoNKeY
06-08-2011, 06:08 PM
What hardware and drivers are you using? What 3rd party tools are you using? What virus scan software? Those are the things that I could think might cause something like that.

-Eric

CGTalk Moderation
06-08-2011, 06:08 PM
This thread has been automatically closed as it remained inactive for 12 months. If you wish to continue the discussion, please create a new thread in the appropriate forum.