Tweet
As those of you who use Maya 2019 on Linux probably know, it normally requires a Centos7 (or compatible) environment to run, unlike all previous versions which were based on centos 6.x
(It is a bit more involved than that, the real issue is the version on glibc which has become incompatible with previous VRay builds, but this is beyong the scope of this post)
We are considering renaming the directory structure of V-Ray for Maya (and Standalone) - for version 2019 and on - to reflect the changed underlying architecture. E.g. until now binaries used to reside in bin/linux_x64/clang-gcc-4.8 and now they would be placed in bin/centos7/clang-SOMEVER
Is anyone aware of any issues this might cause with existing infrastructure scripts at customer sites? Any files etc. would be named the same, but shell scripts (and other automation code) invoking vray in batch mode would have to have the base pathnames updated
We're asking to make sure we make this as painless as possible.
Windows users should not be affected.
(It is a bit more involved than that, the real issue is the version on glibc which has become incompatible with previous VRay builds, but this is beyong the scope of this post)
We are considering renaming the directory structure of V-Ray for Maya (and Standalone) - for version 2019 and on - to reflect the changed underlying architecture. E.g. until now binaries used to reside in bin/linux_x64/clang-gcc-4.8 and now they would be placed in bin/centos7/clang-SOMEVER
Is anyone aware of any issues this might cause with existing infrastructure scripts at customer sites? Any files etc. would be named the same, but shell scripts (and other automation code) invoking vray in batch mode would have to have the base pathnames updated
We're asking to make sure we make this as painless as possible.
Windows users should not be affected.
Comment