I think library materials and the corresponding instances I import in my scene have to be linked. If I change them in my scene, I can't save the changes back to the library. If I have library shaders in my scene and they change (through tweaks in Vred or otherwise), I will not get the updates to my scene (and if the material name in the library changed, I can not reapply them automatically) A functionality analog to Vred would be highly appreciated. Firstly because it is meant to work together and also because the Vred library system is really good! Additionally, it would be amazing to get the possibility to edit the look of the Alias shaders that Vred exports. So far, we use a file with custom materials as the "library" because the ones from Vred get overwritten everytime Vred exports them again. These two reasons, to my experience, make it impossible to build a proper Vred/Alias pipeline out of the box. My workflow suggestion would be: - Build and maintain materials in both softwares - If the shader doesnt exist in either software, it will automatically create one - If it does exist and you edit it in one software, the visual properties of the other software's shader will never get overwritten and only changes like Name, Tags and Metadata will be synced This would enable a synced library with good looking materials on both sides and an easy transfer to Vred, if more advanced visualization is required. 2024 really improved the possibility to work with material libraries. Before I could hardly get any Alias modeller in my company to use them. The menu was so small, the tabs so tedious and you could never even find the shader you were looking for because you couldn't read the names. Now with 2024, I would really like to push the workflow in this direction but this linking of the assets is clearly missing.
Show More