Tweet
Hello, we've been looking to add our OCIO-config to the 3dsmax color management via the OCIO environment variable. But if we set that variable with the correct path the VFB gets set to "None" in the Display Correction and we can't change it to OCIO. Shouldn't it get set to "OCIO" automatically?
It works like expected if we don't set the OCIO env. variable on launch and instead set max's color management to custom config and browse to the same config file. Then the VFB automatically switches to "OCIO" and loads that config via max's color management.
Shouldn't they work the same way? We want the env.var approach to work as the custom config way since we use environment variables in our launcher to set per project configs for different apps.
If we set the OCIO environment variable on launch it doesn't matter what we set max's color management to. Nothing works, the VFB is stuck on "None" for display correction.
The screenshots are from different sessions of 3dsmax. One with OCIO environment variable set and without it set.
3dsmax 2024.2 - Vray 6 update 2.1
/Andreas
It works like expected if we don't set the OCIO env. variable on launch and instead set max's color management to custom config and browse to the same config file. Then the VFB automatically switches to "OCIO" and loads that config via max's color management.
Shouldn't they work the same way? We want the env.var approach to work as the custom config way since we use environment variables in our launcher to set per project configs for different apps.
If we set the OCIO environment variable on launch it doesn't matter what we set max's color management to. Nothing works, the VFB is stuck on "None" for display correction.
The screenshots are from different sessions of 3dsmax. One with OCIO environment variable set and without it set.
3dsmax 2024.2 - Vray 6 update 2.1
/Andreas
Attached Files
Comment