Problem with vray bitmap and .psd files

[OPEN_RANGE]

In think, but cannot absolutely certify, that this issue started with Max 2013.2. Prior to that update I don’t think this problem occurred. Again not 100% on that. It for sure exists with Max 2013.3

Here are steps that I believe induce the problem:

• New blank Max 2021.3 scene with vray 5.
• Create box.
• In material editor assign material to box. Click diffuse map button, choose vray bitmap for map type. choose .psd with adjustment layer for map. Save Max scene
• Open .psd in Photoshop, make a change to adjustment layer. Save. Now you get error message "cannot save because in use in other application".

I have not had anyone else confirm so ideally this could be tested to make sure it’s not a problem that is unique to me.

also note his same problem first appeared in Max 2016. At that time vray bit map did not exist and this happened with the general Max bitmap. AutoDesk recognized the problem and ultimately and thankfully fixed it. I’m not sure if this would be fixed by AutoDesk in Max or by Chaos in Vray? If it needs to be addressed by AutoDesk, maybe Chaos group could help encourage that? It is a problem for me and anyone else who uses .psd files with adjustment layers for texture maps and want to use them with the new vray bitmap map type.

Thanks!

[OPEN_RANGE]

A support person from ADESK was able to reproduce and verify this is a problem. He says it has now been reported and a fix will be forthcoming.

[OPEN_RANGE]

A support person from AutoDesk has replied to my topic with this:

>>"You mentioned that you can reproduce this issue when using V-Ray Bitmap. Have you reported this issue directly to the Chaos Group folks and checked their support forums as well?"

"Please note that issues with the V-Ray renderer, lights, materials and their Frame Buffer should be reported first to The Chaos Group, since they make V-Ray. If they determine that it's a Max-only issue, or a combination of Max and V-Ray, then we can proceed from there. Thanks!"<<

https://forums.autodesk.com/t5/3ds-m...9892701/page/2

Is it possible someone from Chaos can respond to this?

[Margarita.Stoeva]

Hello mark f.

Thank you for reporting this issue!
I reproduced it and forwarded it to our developers to look into.

I have tested all 3ds max versions we currently support and I don't see any difference with current and previous V-Ray versions.
Regardless of whether this used to work in 3ds max versions older than 2016 we'd like to fix it.
The issue is logged in our internal bug tracking system with key VMAX-10562 - use this index if you need to ask us on its development in the future.

Best regards,
Margarita

[OPEN_RANGE]

Thank you! Note this is a problem with bray bitmap which is new starting with vray 5 or
maybe vray next so any versions of vray prior are not applicable. Also, I believe this problem began with Max 2013.2 and prior to that problem did not exist.

[OPEN_RANGE]

Hi. I'm bumping this forward. I am using the most current Vray 5.1.1 and most current #DS Max 2021 and this problem still exists. Possible it can be fixed for the just out Max 2022? Hope so.

thanks!

[Margarita.Stoeva]

Hello

Our developers have already investigated the problem in detail and figured out it depends on specific file handling in 3ds Max which we use with VRayBitmap.
We have officially reported the case to Autodesk - the respective communication is in progress.
At this point, simple test with 3ds Max 2022 confirms that the issue persists.

Best regards,
Margarita

[OPEN_RANGE]

Thanks for the update Margarita.