Frame buffer hanging.

[DanSHP]

I'm working on a pretty intensive interior at the moment. I'm noticing problems in my scene as its rendering that I need to resolve (as you do) stopping, and then restarting.

Problem is, when stopping the render, I have to wait up to 5 minute's until I can amend and restart because when clicking stop, the frame buffer hangs and becomes unresponsive for that amount of time. Extremely tedious.

I can only assume this has something to do with max/vray dumping the scene/render out of internal memory?

As an analogy, I've always thought of it like this. When you install a new application onto a windows machine, it will take time (think adobe creative suite as an extreme example!), but it takes a fraction of time to remove/uninstall/delete it etc. Can the same thing not be applied to memory dumping (assuming it is the reason)? i.e. when starting the render, it will take time to build up the resources required and for the render to start (install app), but when clicking stop (delete/uninstall app) should it not take a fraction of time too?

Is there anyway to make things a little quicker and responsive??? I've noticed this on quite a few scenes.

Vray 3.6
Intel i9-7940x
64.0bg
1080ti

[yavor.rubenov]

Hello,

Do you have many instanced proxies in your scene - for example scattered with ForestPro? If so - there is a similar issue here:
https://forums.chaosgroup.com/forum/...unfreezing-max
Best regards,
Yavor

[DanSHP]

Hello,

Do you have many instanced proxies in your scene - for example scattered with ForestPro? If so - there is a similar issue here:
https://forums.chaosgroup.com/forum/...unfreezing-max
Best regards,
Yavor

No, not in this scene. I've noticed this on much smaller less intensive scenes too, usually I have quite a few render passes saving out with all my .vrimg's, could this be a reason?

[yavor.rubenov]

Yep saving many passes to disk can be slow. You can try to disable the output to test if it helps.

[DanSHP]

Yep saving many passes to disk can be slow. You can try to disable the output to test if it helps.

I was under the impression .vrimg wrote to disk as an image rendered. I'm sure I've picked that up from somewhere, even checked out the .vrimg file size increasing on disk as the render progresses.

[yavor.rubenov]

Yep .vrimg can write to disk while rendering buckets if you are using the V-Ray raw image output. If you are using the Max output - it's written at the end of the render.

Anyways - another thing we can do about the initial issue - can you attach a V-Ray log from one render that is so slow at render end ?

[DanSHP]

Yep .vrimg can write to disk while rendering buckets if you are using the V-Ray raw image output. If you are using the Max output - it's written at the end of the render.

Anyways - another thing we can do about the initial issue - can you attach a V-Ray log from one render that is so slow at render end ?

The frame buffer seizing up happens pressing stop, not just at the end of a finished render.

I suppose, its just crossed my mind, that it is writing to disk via the VFB backup folder too, but then again is this doing that at render end? at render stop? or as the render progresses?

I will post a log, later on many thanks!