VFB Rendering Entire IMage Instead of Region

[Joelaff]

I have a region selected in the VFB (not in Max Common tab), and for some reason VRay has started rendering the entire image even with the region enabled. I can see the region, and drag it around. The little region icon is lit up. Is there some other way that I could have turned off the region rendering in the VFB. This seem to be affecting multiple scene. I should try a brand new scene..

Thoughts?

Thanks.

[hermit.crab]

Usually, no. The resetting the region through this command in the MaxScript Listener and try again:

vfbControl #setregion "reset"

[Joelaff]

Oddly, rebooting the machine fixed it. That I don't get. It's probably unrelated. Most likely the last instance of Max to quit (and thus the one that wrote the prefs to disk last) didn't have the issue, and that fixed it.

Thanks for the code snippet, will try that if I see the issue again.

[Joelaff]

It seems I spoke too soon. I have at least one scene that is still exhibiting this behavior.

[hermit.crab]

If you could reproduce the issue on a simple scene (or simplify the one that's exhibiting it) do send it so we can debug it.

[kosso_olli]

You are not using the "F9" render last command, right?

[Joelaff]

You are not using the "F9" render last command, right?

I am starting the interactive render by clicking the button near the top right of the VFB.


If I can reproduce it I will try to send a scene, but right how I have to deliver something before the holiday.

thanks

[Joelaff]

So I was using the VFB Interactive Rendering while I had Enable Built-in Frame Buffer *disabled* in the VRay tab of the Render settings. This is useful since I render with the default frame buffer for best support from Deadline (handles paths more conveniently). Enabling this checkbox fixed the problem!

That should be in the docs, if it's not.

[hermit.crab]

So I was using the VFB Interactive Rendering while I had Enable Built-in Frame Buffer *disabled* in the VRay tab of the Render settings. This is useful since I render with the default frame buffer for best support from Deadline (handles paths more conveniently). Enabling this checkbox fixed the problem!

That should be in the docs, if it's not.

Hmm, great find. We are not yet sure how to handle this - warning/docs limitation/fix/etc. However, I did log it (internal bug-tracker id: VMAX-12898 ) for investigation.

[Joelaff]

In a perfect world it would just work, but I a guessing that is a technical limitation.

Otherwise at least a warning in the logs (not sure how many people check the logs, but I do, especially if I am having problems.

Thanks.