Huge delay on render end when elements enabled

[tricky]

When rendering a 4k image (for example), the render may complete in only a matter of a few minutes. However, when we use render elements (we have about 9 setup typically), there is a huge delay at the end of the render before the session of max becomes active again. The delay can last for two minutes or more. This happens when rendering the entire frame buffer or a tiny region of it.

If we disable render elements, the scene recovers much more quickly at render end.

When elements are enabled, we can switch through all the elements during the render without any delay. Only right at the end is there the problem.

Why is this? It is most frustrating. I'm using a Quadro 4000 card. The machine is Windows 7 with a dual Xeon setup and 64GB memory. The scene itself is very straightforward. I am using a Nitrous display.

[vlado]

Can you get me a scene where I can reproduce this to vlado@chaosgroup.com ?

Best regards,
Vlado

[super gnu]

is it not simply a case of vray saving multiple large image files? if it has to generate, compress and write 9 or 10, 4k, 32bit images over the network.

thats probably quite a few hundred megabytes at least.

you mentioned it still happens with tiny regions rendered.. but do you mean region, or crop? with regions, the image is still a 4k file..

[joconnell]

Is it just that you're writing out some large image files? Are you using the 3dsmax frame buffer or the vray one? You can often have a look at the folder that everything is saving out to and actually see your bitmaps being written to disk - It might take a few seconds for each image to be written and with 9 at 4k, a few seconds per image is going to build up slightly. Are you rendering to the network or a local disk?

[tricky]

I don't have save on render end checked so it isn't that. I vaguely recall Vlado suggesting that Nitrous doesn't like having more than one session of Max open at any one time, so I will try with just one session open and see if things improve (I did have another scene open but it was just dormant and not actually being used so didn't think that would affect things)

[dejan]

Do you have VFB history auto save enabled? I remember I noticed some delays at render end after enabling it.

[tricky]

Nope - I don't use that

[vlado]

We did some tests, but we couldn't find memory differences between 2.4 and 3.2; will have to do a few more tests though, just to be sure. Still trying to figure where the delay is coming from, however.

Best regards,
Vlado

[tricky]

We did some tests, but we couldn't find memory differences between 2.4 and 3.2; will have to do a few more tests though, just to be sure. Still trying to figure where the delay is coming from, however.

Best regards,
Vlado

So are you able to reproduce this delay with one of your test scenes Vlado?

[Morbid Angel]

tricky, could it be possible the elements have some old network paths in them? I recall we had a problem like that once - we create a max scene using a script which was setup few years ago and network paths have changed since then but the original paths in the render elements were still pointing to old \\server\ and so resolving them was taking that long.

[tricky]

tricky, could it be possible the elements have some old network paths in them? I recall we had a problem like that once - we create a max scene using a script which was setup few years ago and network paths have changed since then but the original paths in the render elements were still pointing to old \\server\ and so resolving them was taking that long.

No I don't think so. These are all fresh scenes and I haven't even given the elements a path to save to. They just save when we choose to save separate render channels in the frame buffer window.

[re:FORM]

Hi Tricky,
I had this problem too.
I know you've probably already check this, but it might be worth triple-checking you don't have the vfb history autosave enabled. It was the cause of my issues.
I just did a test in Maya and even with the power switch off, if I had autosave enabled, it was still saving the VFX after rendering.

In fact, can I flag that as a bug Vlado? (I've only tested this in Maya)

[tricky]

Hi Tricky,
I had this problem too.
I know you've probably already check this, but it might be worth triple-checking you don't have the vfb history autosave enabled. It was the cause of my issues.
I just did a test in Maya and even with the power switch off, if I had autosave enabled, it was still saving the VFX after rendering.

In fact, can I flag that as a bug Vlado? (I've only tested this in Maya)

OK - triple checked. You are absolutely correct - it was enabled! I had assumed if the history button was unchecked it wasn't saving my history. Going into the settings and it was ticked to save saving to my D: drive - a 700+ MB file each time.

Good grief, I've been suffering with this for months and months.

Thanks all.

[re:FORM]

Hah, Months?!? I feel your pain!

I think this sums up your reaction to checking the settings...



I take it my pint is in the post?!

[tricky]

Hah, Months?!? I feel your pain!

I think this sums up your reaction to checking the settings...



I take it my pint is in the post?!

I LOVE Ron Swanson! Best series ever.

(and yes, I've been complaining about this for months now!)

4-pack in post right now