VRayBitmap Viewport Texture Previews - 6.1

[Philip Shounev]

Hello,

I'm not able to reproduce any of the afore-mentioned issues with the incorrect brightness previews. Could you please share the exact V-Ray build version that you are using ? Also would it be possible to send over a scene in which all of these can be reproduced to philip.shounev@chaos.com? Thanks in advance.

Best regards,
Philip

[JonasNöll]

Hi,

I am running 6.10.02 build 31917, 3ds Max 2023.3
Here is a screencapture that shows the issues:
https://jonasnoell.com/downloads/vra...ortDisplay.mp4

And I sent you a scene by mail.

Best

[Philip Shounev]

Thanks for providing a scene sample. It seems that the issue is directly related to setting the color space transfer function of VRayBitmap nodes to sRGB instead of Auto type. I would suggest two solutions as workarounds for now - to use either "Realistic Materials with Maps" viewport preview mode or to manually set the color space transfer function of all VRayBitmaps to Auto.

[matanov]

Fixed in the latest official builds.

[JonasNöll]

Fixed in the latest official builds.

What is not happening anymore is the jump in brightness once changing the Multiplier when colorspace is set to sRGB
But I still have this weird fading to black once I touch any of the values. As shown in the video in my post earlier.

Btw. what also doesn't work anymore is that if you have a BlendMaterial and you wanna display the texture of one of your Coat Materials or Coat Masks in the Viewport. It just ignores it. You can only show textures from the Base Material in the viewport...
Worked before with no issues.

P.S: I'm on the latest build from today 6.10.02 build 00000

[roysgi]

Btw. what also doesn't work anymore is that if you have a BlendMaterial and you wanna display the texture of one of your Coat Materials or Coat Masks in the Viewport. It just ignores it. You can only show textures from the Base Material in the viewport...
Worked before with no issues.

This is exactly what I wrote in this posאhttps://forums.chaos.com/forum/v-ray...le-in-viewport and had no reference

[Vizioen]

Damn I just updated again to the latest version and it still has these kind of bugs, that sucks... rollback again I guess

[glorybound]

Yeah, broken here too. Realistic with maps brings my viewport to a hault, so it isn't an option, unless I isolate just what I am working on.

[Philip Shounev]

Hello,

The flickering behavior when playing around with the spinners of the bitmap parameters is 3ds Max related - this happens when using max native bitmap node as well and when gradually changing the values of the "Blur" parameter, for instance. I'm attaching an exemplary video:

[JonasNöll]

Hello,

The flickering behavior when playing around with the spinners of the bitmap parameters is 3ds Max related - this happens when using max native bitmap node as well and when gradually changing the values of the "Blur" parameter, for instance. I'm attaching an exemplary video:

Hi, I can confirm that this issue also seems to be with previous versions (tested with V-Ray 6, 3ds Max 2020).
However it seems to be rather an issue of the VRayMtl in combination with the VRayBitmap. I don't have any of those issues with a Standard Max Material with a Standard Max Bitmap. The Standard Material with the VRayBitmap does have those issues again though.

[JonasNöll]

Also there is some weird fading happening when playing with any of the values in the VRayBitmap:

[Philip Shounev]

In a simple test scene where I use Scanline renderer (uninstalled V-Ray for 3ds Max) using only 3ds Max Physical Material and max native bitmap, the same fading can be reproduced when playing with the spinners of the crop values. The fading in general happens when the viewport preview generation takes more time. With VRayBitmap the fading is even more pronounced due to the more complicated filtering behind it. It also depends on the size of the loaded texture. Attaching a video:

[theedge]

Phew !
This viewport issue was driving me mad until I flound this post. Guess I'll have to roll back to previous version as many others, as realistic mode is simply unusable for archviz work.
Can't believe such an obvious issue made it into the final update though.

[yavor.rubenov]

Phew !
This viewport issue was driving me mad until I flound this post. Guess I'll have to roll back to previous version as many others, as realistic mode is simply unusable for archviz work.
Can't believe such an obvious issue made it into the final update though.

The issue is already fixed in the official builds on site ?

[theedge]

Just started a new project, so will have to wait a few weeks before testing the latest build.