Save render state during octane live preview

[mark0spasic]

Hi Jim is it possible to implement save render state during octane live preview?
I usually use octane live preview for stills insted of final render.

[rv3d]

I usually use octane live preview for stills insted of final render.

Me too, it will be nice.

[JimStar]

What is the usecase for it?..
Interactive rendering session is by definition volatile - you almost always change something when it's active, it is its main purpose, to watch the scene changes... If you close the interactive window - there will be almost certainly something changed in the scene before opening it the second time... If not - what's the point of closing it at all?
Plus, the interactive session's ideology - is to be simple to run. It will be broken by the overhead of saving the session every time you close it plus asking you every time by annoying dialog before opening the interactive window: "Do you want to use the saved session?"...
Too much harm for the feature that supposed to be quick and interactive preview, and is not supposed to be used for final rendering...

[kevinshane]

too many reasons, for example, we render almost everything in realtime viewport other than hit the render button cuz realtime viewport gives many stats info, in fact, I think no one would render the STILL image by using 3ds max own frame buffer
also saving many render passes is paintful cuz they always popup many windows and I have to name them one by one(again, still in realtime viewport), I would prefer a button that could auto save them all and name it correctly, currently I have to point to path and a still image from native 3ds max frame buffer, it also makes me uncomfortable(due to the poor info in that frame buffer)
so does the deep image saving process...

Shane

[rv3d]

What is the usecase for it?..
Interactive rendering session is by definition volatile - you almost always change something when it's active, it is its main purpose, to watch the scene changes... If you close the interactive window - there will be almost certainly something changed in the scene before opening it the second time... If not - what's the point of closing it at all?
Plus, the interactive session's ideology - is to be simple to run. It will be broken by the overhead of saving the session every time you close it plus asking you every time by annoying dialog before opening the interactive window: "Do you want to use the saved session?"...
Too much harm for the feature that supposed to be quick and interactive preview, and is not supposed to be used for final rendering...

for example, I need this option to send some quick renders for the customer.