vfb saving issues

[agentdark45]

I'm getting some weird issues saving files from the vfb in the A7 preview build. The saved filed only contains a region (with a black background) that doesn't correspond to the location of the 3ds max region. It also is affecting VFB+ and outputting the wrong region to it. I can copy the image from the vfb fine however.

Not sure what's going on or if I've messed up a setting somewhere.

[ukajali]

hi,

have to second this one.
rendered an office and had to rerender some reflections->positioned the region in max fb->rendered the correct region->saved to file via corona vfb->
but got the wrong region saved!  the region moved down to the bottom of the frame.
copy to max fb copied the wrong region too.
i ended up getting my region by snipping it from coronas fb with the snipping tool :)

i'm on daily build post-A6, timestamp May 27

[Ondra]

hi,

have to second this one.
rendered an office and had to rerender some reflections->positioned the region in max fb->rendered the correct region->saved to file via corona vfb->
but got the wrong region saved!  the region moved down to the bottom of the frame.
copy to max fb copied the wrong region too.
i ended up getting my region by snipping it from coronas fb with the snipping tool :)

i'm on daily build post-A6, timestamp May 27

are you also using VFB+ script?

[ukajali]

no, no vfb+

didn't test it with another scene to check if reproducible...will do as soon as possible.

[ukajali]

happens with other scenes too....region is always moving to the bottom of the frame when saved.

still same built as mentioned above.

[Ondra]

hm, that is really weird.
Can you try latest assert build?
Can you think of anything unusual about your workflow or 3dsmax installation?

[ukajali]

no, my max installation always worked pretty stable...

windows 7
max 2012
pretty clean, without much plugs other than vray and multiscatter...

will try latest build tomorrow

[romullus]

I can confirm this bug too. Build timestamp: jun 17, max 2014 sp5

[Ondra]

note to self: regionrender_bug.rar

[Ondra]

Ok, it should be fixed, but I was unable to explain why it did not happen to me earlies, also the description is not entirely consistent with what I saw, so test it properly when new build is out.