No VrayHDRI node anymore?

[Frank2223]

Hi all,

After recently upgrading to Vray5, I’ve noticed the VrayHDRI map node is now no longer there. I’ve used VrayBitmap in its place, and it has exactly the same parameters in the dialogue box. Can anyone confirm that it’s the the “new” HDRI node? Cheers!

[Joelaff]

Yes, VrayBitmap is the new VrayHDRI.

Enjoy.

[matanov]

Yes, we've changed only the name since people thought it's only good for hdr images and IBL

[^Lele^]

Indeed, in scripting you can create the map with either class name.
Old tools will work just fine.

[demonslayer]

Have to dig this out again. Was it possible to disable the automatic Color space transfer function on map reload or renaming/rerouting?

[vlado]

If the file name stays the same and only the path is changed, then the transfer function is not modified.

If there is a situation where the automatic setup is not desired, can you help me understand the use case?

Best regards,
Vlado

[chicohermida]

If the file name stays the same and only the path is changed, then the transfer function is not modified.

If there is a situation where the automatic setup is not desired, can you help me understand the use case?

Best regards,
Vlado

If you drag a material from a library (including vray material library) and press the reload button on vraybitmap, it will potentially change the "color space transfer option" on the first time only. Looks like a flag that is not transferred over when you make a copy of a material.

Worst case is when you archive a scene and use something like "Relink Bitmap". All newly copied materials from libraries can have the "color space transfer option" changed on a glossiness map with jpg extension for example.

As a suggestion, you could introduce a "Auto" checkbox that is on by default, but can be turned off to stop the automatic behavior

[^Lele^]

If you drag a material from a library (including vray material library) and press the reload button on vraybitmap, it will potentially change the "color space transfer option" on the first time only. Looks like a flag that is not transferred over when you make a copy of a material.

I cannot replicate this. it works just fine.
Can you go into more details?

Worst case is when you archive a scene and use something like "Relink Bitmap". All newly copied materials from libraries can have the "color space transfer option" changed on a glossiness map with jpg extension for example.

I have just tried this with both the map and the asset tracker: so long as file name and extension stay the same, nothing at all changes.
I'm not sure what "relink bitmap" is (Colin's old script?), or what it's doing (it's easy to set the transfer function via scripting. With MXS the map will not be automated in any way.) but the map isn't misbehaving with the max methods and tools i used.
More specific info would be great.

As a suggestion, you could introduce a "Auto" checkbox that is on by default, but can be turned off to stop the automatic behavior

I'd love one global option to disable the automatic behaviour, if nothing else to give some peace of mind to those which don't want training wheels (me, f.e.).

[chicohermida]

Yes Relink Bitmap by Colin as a common example

Can you go into more details?

Step 1: Save a 8 bit jpg from photoshop
Step 2: Create a new VrayBitmap in the material editor
Step 3: assign the jpg
Step 3: choose "Inverse Gamma" on the "Color Space Transfer Function"
Step 4: duplicate the VrayBitmap
Step 5: press the "Reload" button on the new copy of VrayBitmap

Once you press reload it will revert from "Inverse Gamma" to "From 3ds max"

It happens every time the VrayBitmap is duplicated, the same would happen when duplicating a whole material, or dragging it from a material library

Even though we are testing with the reload button, it will also automatically change when you are trying to reassign the filepath through a script in a situation where files have been moved.

Haven't tested on multiple computers, will test on another client's computer next week.

Thanks for testing.

[^Lele^]

Step 1: Save a 8 bit jpg from photoshop
Step 2: Create a new VrayBitmap in the material editor
Step 3: assign the jpg
Step 3: choose "Inverse Gamma" on the "Color Space Transfer Function"
Step 4: duplicate the VrayBitmap
Step 5: press the "Reload" button on the new copy of VrayBitmap

Once you press reload it will revert from "Inverse Gamma" to "From 3ds max"

Not happening to me, wether with instanced or copied map.
As explained so long as the file *name* and *extension* are identical, no change happens, be it via UI or Scripting, and this is all i am experiencing.

So far, i couldn't repro any of the behaviours you describe, be those actual or hypotetical (i tried scripting a map path change, and there was absolutely no change in the .color_space property: gamma stayed what i had it set to.).
I'll need a reproducible case, as right now there is nothing to "fix" that i can see and bring to devs.