Quite a long delay when render is "done"

[alexyork]

Hi Vlado and Co,

Running latest stable with max design 2014, here. This has been a minor issue for a while and it seems it's still happening, but I find there can be quite a significant delay after a render finishes (when it says "done") before max is usable again. This happens even when no file is being written on completion. I'm guessing it's doing something akin to flushing cache/memory or something along those lines. This delay appears to be more significant with more complex renders/scenes or when the VRFB is loaded with more "stuff" to deal with. Or maybe it's something to do with the viewports... I really have no idea.

I'm just wondering if it might be possible to optimise/fix this somewhat for a future build. Wait times can be as long as 30 seconds or so, I've found, which is quite a timesink when you're doing lots of test renders etc.

Cheers,

[LudvikKoutny]

From my experience it has something to do with combination of these factors:

VrayVFB and Console window being displayed over viewport
Progressive refinement in viewport enabled
Windows Aero enabled
Graphics driver

[alexyork]

I have Aero and Progressive Refinement disabled, so perhaps it's something more related to the VrayVFB/Console and the viewports.

[Svetlozar Draganov]

If you render the same scene with Max 2013 is the result the same ?
What happens in Max Frame Buffer is used instead of VFB ?

It is most likely related to unloading bitmaps and other stuff - we can check this in the Vray-Messages windows (level 4)
You could check how much time Vray spends in the ending-procedure >>