i have updated to the latest vray and have noticed a change in behavior that is a little inconvenient…
When i render out a region in maya using VFB or via deadline using -reg command the saved file is only a crop and not full frame. On previous versions it always used to be full frame so easier for comping in post. I know that on old version of vray if i changed the memory frame buffer from full to none it would do this so i always left on default. Now it seams default also only saves out a crop.
Dunno of this makes a difference but im rendering out multilayer exr.
Is this normal behaviour or am i missing a new button somewhere?
I couldn’t see anything that could cause this at a first glance looking at our changelogs. Could you share a few examples so we can get a better idea? Maybe we broke something along the way.
In the old version, we did save the whole picture even with region rendering, however only the region part was rendered.
This meant that we used to save whatever (possibly junk) data was in the buffer to the image.
I’m not sure I understand why you need the old behavior. Could you explain your workflow in a bit more detail?
Hi. I mainly work in high res stills. If retoucher requests an ammend to a wheel or headlight. Rather than render the whole image again i render a region, having the full frame means the retoucher doesnt have to manually allign and can drag the whole image including the black surrounding unrendered frame onto comp and its aligned.
you already have an option to optimise frame buffer memory management, (which stops vray saving out the whole frame) to eliviate any overheads so why change the default option?
Oh I see. Some people load an already rendered image and use the render region to render on top of it. Then the output is a complete frame, without any black surroundings. Apparently, we broke this workflow between 02 and 03.
We’ll probably have a fix for this soon, in the mean time I have a few more questions:
If I understand correctly, you don’t load an image, you just need the surrounding black areas of the image for alignment purposes, is that correct?
I’m asking because normally, the data window coordinates we write in the image should be sufficient for alignment. So in theory, the black undrendered part doesn’t have to be in the image explicitly. I’d like to know if there’s something wrong with how we output dataWindow coordinates, or the receiving software ignores dataWindow coordinates.
I normally render in deadline using -reg command, so no option to preload old image and render over it. nice work around for viewport rendering however, i usually like to submit to deadline as this frees up my user license so i can continue to work while rendering.
We use photoshop to retouch and i dont believe it uses data window coordinates unless you know otherwise
We have recently upgated to next, and i notice this behavour still exsists which is pretty fundermental to breaking our workflow. any ideas of how to get around this?
Im running the above version of vray and it has not changed back to the old behavour is this something you can fix or do we have to change our workflow?
Ah, probably I forgot to mention how it behaves with the fix and you can try if it works on your end.
Since there were lots of ambiguity in behavior with the region enabled and with setting the data window, to streamline things, now enabling the VFB region determines whether the region or the whole image will be saved when saving from the VFB.
So in brief - if the region is enabled - only the region will be saved.
If the region is disabled - the whole image is saved.
Try disabling the region after rendering and it should work.
But if i render from deadline outside of maya there is no way to switch of VFB region after a render and save out the image? Also i usually pick up the file that is automatically saved to the maya temp folder. Are you saying that i will make to manually save out within maya VFB after switching of VFB regoins in order to save out the full frame and not the cropped image?
when i render in deadline it submits a maya batch render and i use the addtiaonal command line arguement -reg #### #### #### #### where the # are the coordinates for left right bottom top regions in pixels. it is completely outside of maya GUI.
deadline submits scenes to the farm, it load a maya batch render with no GUI interface. You can specifiy regions with in the deadline submitter using addtional command line arguements such as -reg #### #### #### ####, where the # is the pixel coordinates for left, right bottom and top regions in pixels for the regions render, all i want is for the regions not to be a crop. I see when i open the cropped imags in photoshop using proexr that there is some meta date showing these regions as
Then this is different than the VFB issue/fix.
What’s the expected behavior here, I got a bit lost. What do you need to happen when you render a region in batch mode?
I would be nice for it to behave like it did in vray 3.6.02 which was, when i opened a region render in photoshop for it to have full bleed and not crop to the region.