VFB - right click doesnt reveal pixel info

[PIXELBOX_SRO]

Hi guys,
as the topic says, no info...seem s to be broken.
M

[Brian Bradley]

Same here??

[Miro]

Do you guys mean the Pixel information dialog doesn't show at all or it shows up but is empty?

[PIXELBOX_SRO]

nope it doesnt show at all.
i am on the max 2017 btw and the latest vray (not nightly)

[Miro]

The dialog probably went off-screen. Could you try changing the render engine to i.e. Scanline and the back to V-Ray?
This will reset the render settings and should also reset the position of the Pixel information dialog.

[Brian Bradley]

Wasn't showing up at all for me, but then it just started working??? Currently using latest Vray in Max 2016. Any particular reason why the Float values are in an eye aching red?

[thatworm]

Wasn't showing up at all for me, but then it just started working??? Currently using latest Vray in Max 2016. Any particular reason why the Float values are in an eye aching red?

I think that means you have the "corrected colours" option in the pixel information pane ticked, my understanding is that when that is ticked the information is in srgb rather than linear

[Miro]

thatworm is correct, red shows the corrected pixel color values (this includes corrections applied from the Color corrections pane of the VFB )

[Art48]

To be honest - at least in our workflow - we don't care about the linear color, we care about the "true" shown color right there and how I see it at that moment. In my opinion it would make more sense to switch those 2 around, meaning the default would be the actual shown color in the VFB, color-corrected and all, and the linear one would be the opt-in. At the moment I can't imagine a scenario (except debugging AOVs or sth.) where you actually want to see the linear color and not the one you actually see right now.

Also a less-intrusive/eye-aching red would be better, too. I dunno - maybe darker/less saturated? Maybe not even colored, but just bold?

[svetlozar.draganov]

What about keeping the arrangement as it is but removing the eye catching red color from the corrected colors and using the same color as non-corrected one?

[Ihno]

To be honest - at least in our workflow - we don't care about the linear color, we care about the "true" shown color right there and how I see it at that moment. In my opinion it would make more sense to switch those 2 around, meaning the default would be the actual shown color in the VFB, color-corrected and all, and the linear one would be the opt-in. At the moment I can't imagine a scenario (except debugging AOVs or sth.) where you actually want to see the linear color and not the one you actually see right now.

Also a less-intrusive/eye-aching red would be better, too. I dunno - maybe darker/less saturated? Maybe not even colored, but just bold?

To be Honest Imo the linear color information is way more important. Debugging lighting, get right values for lence effects masks and a lot other of stuff. I, dont even need the corrected values very often. Since, like many people I usally do the tonemapping in Post.

[Art48]

What about keeping the arrangement as it is but removing the eye catching red color from the corrected colors and using the same color as non-corrected one?

I'd be okay with that. Getting some kind of distinction would be good tho - maybe italics?

[svetlozar.draganov]

Added it as Improvement request in the system and will keep you posted.