Ok so I investigated this matter and it’s a little more weird than I described at first and the results are somewhat different (which is weird because last time I checked it did different things). And with two different outcomes depending on how you merge the material.
Anyway I recorded a video here: https://youtu.be/TIc1MVUaefE and I attached the mat file to this post:
I have a scene in centimeters and I created the following vray maps where you can input sizes:
VrayDirt
VrayCurvature
VrayDistanceTex
VrayColor2Bump
VrayNoiseTex (this one is missing QT I think as it loads slower)
VrayTriplanarTex
VrayEdgesTex
I then specified the size as 500 (except 100 for the EdgesTex as that is the maximum).
I saved this mat, then reset (back to cm), then changed the units (back to meters). Then dragged the mat file into the slate. When checking if the sizes are correct these ones are incorrect. All of them are multiplied by 100.
VrayCurvature
VrayColor2Bump
VrayTriplanarTex
VrayEdgesTex
What strikes me is that the fields that have the units inside (cm in this case) are all messed up when importing this way. All the fields of the other maps that have no units inside the fields are correctly scaled (at least the correct numbers, don’t know about the rendering part, I didn’t test that). The same problem occurs when I use connecter for instance to load a mat file into 3dsMax
---
I then reset my scene back to cm, drew a box and applied this material, and used copitor (which is basically save selected) to save this box. I reset my scene and changed the units to meters and pasted the box with copitor back in this scene.
Results are different this time only VrayEdgesTex displays the units multiplied by 100.
I tried with native save select and native merge and the results are the same. VrayEdgesTex is multiplied by 100.
---
So two different cases of importing the material with two different outcomes.
Can this be fixed please, or is this an Autodesk thing? Quite annoying as I’m working more and more in two different units.
3dsmax 2023.3 and Vray 6.1 (although I had this in 2022 and Vray 6.0 as well)
WrongUnits.zip (5.94 KB)