Save image with VFB is different from print screen VFB

[Jiri.Matys]

It doesnt matter. I just use RGB (not RGBA), anything else doesnt matter, it look like this every time.

[crazy homeless guy]

Would be best to upload the Max file as well.

[LudvikKoutny]

Here are some thoughts:

Difference on 8 bit images is most likely sRGB vs Gamma 2.2, as guys before me already stated. Difference in 32bit EXR... aren't you saving integer 32bit format instead of full float? That's a common mistake.

[irwit]

Ive had this before. Save your image as 32 bit tif or exr. Then save out a jpeg from nuke. It will match your frame buffer no porblem. Really annoying issue.

[Svetlozar Draganov]

It doesnt matter. I just use RGB (not RGBA), anything else doesnt matter, it look like this every time.

Does the same thing happen when rendering with another render engine?
What is the exact V-Ray version that you are using?

Can you send us a Max file so we could try to replicate the issue into our environment?
Did you try to open the image into another image editing software like Nuke for example?

[Jiri.Matys]

It seems I accidentaly used integer, not full float. Now its good with simple test scene. I will try to render some more complex scene and will see. But thanks for help.

[CoastalVis]

I've just installed the demo of Vray 5 to see if it is still as buggy as it was when I bought a Vray 3.6 licence a few years ago, and quite disappointed to see it is in many cases. The fact you cannot even save out the same image that is shown in the VFB without a workaround is crazy. Not all artists want to run their renders through Nuke to get what they see in the VFB, the logic is so broken in Chaosgroup. Sometimes the artist just wants a simple jpg straight from the frame buffer to show the client a quick iteration.

[seandunderdale]

In Maya you can save to png and it will save exactly as it looks in the VFB. Not sure if Max is the same though.

[^Lele^]

I've just installed the demo of Vray 5 to see if it is still as buggy as it was when I bought a Vray 3.6 licence a few years ago, and quite disappointed to see it is in many cases. The fact you cannot even save out the same image that is shown in the VFB without a workaround is crazy. Not all artists want to run their renders through Nuke to get what they see in the VFB, the logic is so broken in Chaosgroup. Sometimes the artist just wants a simple jpg straight from the frame buffer to show the client a quick iteration.

Sorry, what issue do you have?

[CoastalVis]

Hi Lele,

Basically the image I have setup in the VFB saves out slightly blown out and is unusable. I have tried rendering in several different 8bit,16bit,32bit formats and all seem to be the same result. I have googled it and alot of people have had the same problem and think its to do with the windows colour profile being set to srgb and the image saving as rgb? Also the Interactive cpu renderer is still very buggy especially with Forest pack where when you have certain 2d nodes in your shader graph its just renders out grey or incorrectly. I didnt get around to using the gpu renderer so cannot comment what thats like in vray 5. It seems everytime I use Vray im googling issues more than im getting the job done, just not the best experience but could just be unlucky this time around I guess.

[^Lele^]

Hi Lele,

Basically the image I have setup in the VFB saves out slightly blown out and is unusable. I have tried rendering in several different 8bit,16bit,32bit formats and all seem to be the same result. I have googled it and alot of people have had the same problem and think its to do with the windows colour profile being set to srgb and the image saving as rgb? Also the Interactive cpu renderer is still very buggy especially with Forest pack where when you have certain 2d nodes in your shader graph its just renders out grey or incorrectly. I didnt get around to using the gpu renderer so cannot comment what thats like in vray 5. It seems everytime I use Vray im googling issues more than im getting the job done, just not the best experience but could just be unlucky this time around I guess.

We'd need actionable feedback to get to the bottom of issues: if you have a definite set of operations that we can reproduce on our end to get the same wrong result as you do, please share them.
If they come with files, even better.

For color management, we can only do things the way we think is right (which includes fixing any bug.).
If the user hasn't set their workstation up properly (or photoshop/nuke/whatever other color managed bit of the pipeline.), we can't help besides pointing the mistake out.

For any other issue you may have, please be as specific, and as current, as you can manage, so we may try and sort it out.

[CoastalVis]

So maybe when you install Vray there should be a tutorial/info box/ webpage that pops up stating what Colour profile settings you have to change in windows to suit the vray framebuffer? Or if somethings is out of sync a warning pops up? A lot of people that mainly work in Archviz or Product viz don't need to concern themselves with Colour management pipelines. They just want the rendered image to look the same straight from the render. It's not complicated. As mentioned in my previous post every time I use vray my productivity goes right down because I'm fighting the software, why should I spend my time helping you fix something that should work out the box, does your QA team not test the product properly? The bugs I'm seeing are surely not extreme edge cases.

[^Lele^]

The thing is, it works fine for me, precisely as you describe it should, and i have touched *nothing* at all from a fresh windows, or application installs (f.e. PS or nuke, or Windows Photo, or FPV. Everything looks just fine across the board.).
We can deal with defaults, not infer intention (particularly across applications.), and it's when people *do* change settings for whatever reason that issues on their side crop up, in this specific aspect of color management.

So i can only renew a request for the *exact* steps that led to a *precise* error in the results, so that we may find out what to do about it.

[seandunderdale]

if you tonemap in the framebuffer and save out as png you will get the same result in photoshop as you have in the framebuffer. I do it all day long. You might then need to work out how you set photoshop up, if you work in Adobe98 colourspace for example. But to get an image without blownout highlights is very straightforward. If youre using a LUT, make sure it has "save in image" applied. Same goes for the same settings in the display correction" layer.

Make sure you are viewing your images in an app that isnt doing anything weird to the colour profiles (avoid windows picture viewer). I use Nomacs to view images, but also make sure I check everything in Photoshop with Adobe98 colour profile assigned.

Perhaps there are more tick boxes in Max to get the framebuffer layers saved to the image, but if you are saving to a non floating point format, then the image (effectsResult possibly) will have the correct values. Then you just need to view it in a colour accurate app. I also recommend making sure your screens are professionally calibrated. I run my Spyder X pro on my screens every month to make sure things are accurate,