CoronaVFB disappears after a render when using CoronaInteractive at same time

[atelieryork]

Hi folks,

I have CoronaInteractive in one of my viewports, rendering away fine. I then launch a proper CoronaVFB Render to test how it looks at higher res and let it finish.

At this point nothing else should happen, but what does happen is that the CoronaVFB immediately disappears and the Interactive session starts up again. If I then hit the ShowCoronaVFB button nothing happens. If I close the Interactive session I still can't recover the CoronaVFB.

In other words, the Interactive is killing the main VFB render completely and is non-recoverable.

If I launch the CoronaVFB Render without using Interactive first, all is fine.

Using latest daily build. Max 2016 SP1.

[atelieryork]

Note also that if I maximise my perspective viewport (the camera view), so the interactive viewport is not visible in max, and then launch a VFB render, the same thing happens. The render completes fine, but then the VFB remains open. but as soon as I minimise/restore back to Quad view, the Interactive viewport launches and the VFB is closed and the render lost.

[atelieryork]

I am also having some issues with the Interactive renderer not updating and only showing the result of the previous session, even after starting a fresh session.

[maru]

All of this is known but apparently hard to fix. To see the content of your regular VFB, you can go to rendering > rendered frame window. This will show natie max vfb with your last Corona rendering inside.

The thing with interactive showing result of previous session - does it get fixed after you restart IR or move any of the objects in scene?

[atelieryork]

Ah yes I forgot it was saved somehow in the max FB as well. At least the render is somewhat recoverable. (although I assume only the beauty pass. other passes will be lost I guess). hope this can be fixed soon...

Maybe for now it should be made that Corona will automatically disable the current Interactive Session when you hit Render. Could this be done? Or at least a warning popup?

As for the locking Interactive window.. I just opened a fresh max instance, opened my scene, started an interactive session and it's jammed after just a few seconds. seems to be scuck on some kind of pre-calc stage. No amount of jiggling things around in the viewport fixes it. EDIT: it seems not to like one of my cameras. All other cams are fine... weird.

[atelieryork]

Ok I think I found the issue. It's a bug. Using PhysCam, if Perspective control is on, say a vertical lens shift, AND you're using target camera, Interactive doesn't work. If you disable either the target OR the lens shift it works.

To be even more specific: only shift is causing the bug. tilt doesn't cause a problem and interactive updates fine.

So, it's a bug with lens shift + interactive.

[maru]

Doesn't happen here. Can you upload some extremely simple scene where this happens? (camera+teapot?)

[atelieryork]

Hey Maru - sure I will try to make a simple version and see if I can reproduce reliably.

[atelieryork]

Hmm. Just opened Corona and my license has somehow disappeared?

Anything going on behind the scenes today?

[atelieryork]

So I reactivated my FairSAAS license and it seems ok now. Wonder why that happened?

Anyway, Maru (and others) here's the scene, max 2016 format:

https://www.dropbox.com/s/rb1nyy00n4hc250/for_maru.max?dl=0

Dead simple scene. Making a new camera causes the same problem.

Everything works fine except Shift. Which doesn't update in the interactive renderer.

[atelieryork]

Hi Maru,

Did you receive the file ok? I could re-upload if needed.

I found this same bug on a different scene I'm now working on. Using shift = no interactive update.

[maru]

Hi, I did not check this yet, but I will. Sorry for the delay.

[atelieryork]

No worries. I'll leave the file up there.

[maru]

I just checked and everything works fine in 1.2.1 and daily build. Or maybe I am doing something wrong. I switched to the camera in that file, enabled targeted and shift. IR updates fine docked and floating, regular rendering works too. Also created a new camera and did that, works fine again. Would be great if someone else could check this.

[atelieryork]

Hey Maru.

I'll check again on a fresh scene myself later if I get a moment. 2 deadlines today.

Cheers,