Corona 12h1 Color managment on Render farm

[Jims]

Hi corona team,

The issue is when we use the color managment in a scene and we send it to our renderfarm, the color managment is not active anymore in node mod. On nodes the scene is open as gamma workflow.

Could someone can help with this ?

We are using Pulze to send scenes.

Thank you

Jims

[maru]

(Un)fortunately, Corona is not responsible for anything like that. Please try the following on all of the machines where the rendering is not working as expected (render nodes):

Close 3ds Max, open this file in notepad C:\Users\_your_username_\AppData\Local\Autodesk\3dsMax\202x - 64bit\ENU\en-US\defaults\MAX\CurrentDefaults.ini , search for "PipelineMode" and make sure that it is set to 2. If it's set to 1, please remove the number 1 and replace it with 2. Then close the file and save changes. Then start 3ds Max, open your scene, and check if the issue is still there.

1 means gamma workflow
2 means OCIO workflow

Most likely this issue is completely independent from Corona. You can check that by sending a job with another renderer.

[Jims]

Hi,

Unfortunately, I already check this but it's not the solution... :-/

If someone have an other idea, please let me know.


On Attachement, on left is my VFB ACESsg with AdobeRGB Display, on right is the Tif outpout in photoshop with adobeRGB color profile

[maru]

On Attachement, on left is my VFB ACESsg with AdobeRGB Display

How exactly did you configure this in 3ds Max?

[Jims]

I received some information so I will share it with you :

IMPORTANT

Be aware that using OCIO in network mode will NOT work using Deadline in max 2025 (probably 2024 too)…

This result in incorrect texture color profile and max will switch to unmanaged Color mapping… (confirmed so far using Vray, or corona, Max lightening daemon or MAX CMD)…

Need to try if this happen too with Backburner (should since maxcmd in deadline is basicly backburner mode), to know if this is a Deadline issue, or a MAX issue.

EDIT : it appear this happen with backburner too (sadly still not compatible with ipV6 local network in 2024), so this is a 3dsMAX network mode issue…

EDIT 2 : OCIO Env Variable have NO effect

Edit 3 : So far the only way i found OCIO working on a renderfarm, is setting max color management to gamma Workflow (the old good way), then use Vray in ACES mode (loading the ACES 3dsMax ‘.OCIO’ build-in config in Vray VFB, if you want OCIO display as max OCIO default), then only use Vray bitmap, with primaries and color transfert set correctly and manually (no auto/default mode)…

[Jpjapers]

Can confirm im also facing a similar issue. Rendered several large images with Garagefarm and after receiving finished renders with clearly incorrect colours, myself and the support both tried rendering locally and the images were rendering correctly on a single local machine.

I later tried the same file using DR locally across two machines and the same issue occurred meaning this is a network-only issue.

Using Max 2024 and OCIO Defaults. Garagefarm support tried the env variable fix but it didnt work.

Can confirm going back to linear works fine.

[DotDesignStudio]

Hi,

I have the same problem. Max 2025 - if i render from a workstation with OCIO enabled and render it via corona DR i get bands of different brightness and colors from render nodes. I tried to change pipeline mode in CurrentDefaults.INI, i tried to open max on a render node and change the color management to OCIO and save it as defaults.

Nothing works. It opens max for DR with gamma workflow no mater what i do.

Mike.