1. For a few months we noticed an issue when exporting a vrmat from 3dsMax and importing that material in Cinema concering the Falloff node. Apparently when a Falloff node is used directly as for example Diffuse color, it gets converted in Cinema into just 1 color. On the other hand if used as a node for blending in VrayBlendMtl it works as intended (one color/texture gets blended from one into another). If there is a lot of nodes, doubling materials to make it work, makes editing really fidgety. (Pictures of the problem attached)
2. When we open vrmat materials with submaterials (multiple, but also with just one, Material Name), exported names have an additional suffix like “Material_#138@mtl**_2**” - which is not in the original material name in 3dsMax. If used in the Take system for example, that causes a lot problems, because if any editing is done and the vrmat is exported again from 3dsMax, it’ll have a different number in the suffix (Material_#138@mtl**_51**) and the Take system has to be manually corrected in Cinema to change the parameters. If it is not avoidable to add the suffix, can it at least stay the same suffix when doing additional exports.
3. There is also trouble with Triplanar nodes from Max which again get weirdly transferred/don’t work when transffered, but we avoided that issues by using VRayUVWRandomiser node and we use models are properly unwrapped, so it’s not that big of a problem…still would be nice if it was fixed.
Hi @prima_commerce , can you give some additional details on your exact workflow and possibly example files we can check out? I’ll try to address some of your problems, but keep in mind that transferring materials between different integrations may not always be seamless.
From my attempt at reproducing your example, it seems that the produced VRMat is problematic and we’ll need to investigate in details why it differs so much when rendered in Cinema 4D. In the meantime, might I suggest you to try to avoid VRMats and instead export a .vrscene file (you may export only the materials and textures in it), and then import the scene in Cinema 4D. This way the material graph will be reconstructed with native V-Ray nodes in Cinema 4D and you will both have more control over the imported material and result.
The names used in the exported VRMat files are generated during export in 3dsMax and may be different on each export and I’m not sure there is an easy way to prevent this. I can only suggest here to export only single materials, so the VRMats will have only a single material contained inside. The files can then be post-processed with a script to use a predefined name.
Is this again with .vrmat export or the materials transferred in different way? An example would also be helpful here.
1. Well we tried this on more than several occasions, I currently don’t have a specific example I am allowed to share though. I assure you the problem is consistent though and even had it on previous Cinema version.
2. I see. That is rather unfortunate. But thanks for checking.
3. What was noticed that there’s a problem with scaling, if we use any scaling on the texture it basically doesn’t scale. I am not currently in the office to give you an example, so I’ll post on monday.