Different results rendering with 3dsmaxCMD.exe

[Dan Marks]

Hi,

Please can you help me fix this issue,

Here are my tests, on the left is a render from my local machine using 3dsmaxCMD.exe on the right is the render from my render farm, also using 3dsmaxCMD.exe

I run.
C:\Program Files\Autodesk\3ds Max 2025>Y:\dan\test.max --GammaCorrection=1 -GammaValueIN=2.2 -GammaValueOut=2.2

On my local machine the resulting image is exactly the same as if I render locally with 3dsmax, or if I render on our farm with Backburner.

I remote desktop to any node on the farm and run the same command, I get the result on the right which is slightly more contrasted. If it is difficult to see the difference, try downloading the attachments and flicking between the two. This slight contrast appears in all render channels, so it doesn't appear to be only related to lights or materials.

I am switching from Backburner to Deadline, using the 3dsmaxCMD workflow for important reasons. Which is why I need this to work.

My Question: What can be causing the output to be different? Is there a default setting the Vray or Max could be providing on my local machine that needs to be applied to the farm?

Software:

Local machine
3dsmax 2025 27.3.0.30874, Vray 7.00.04, Windows 10

Render node
3dsmax 2025 27.3.0.30874, Vray 7.00.04, Windows 11

[Dan Marks]

I can add to this that if I save from the VFB while it is rendering on the render node, it saves the same as rendering on the workstation and on backburner. Perhaps it is something in the save parameter? What is the difference between saving via the VFB and allowing 3dsmaxCMD.exe to handle the save?

[hermit.crab]

You are sending the job through the Deadline monitor, right? Since you are using some manual Gamma correction, also set it in the Render Options > Gamma Correction in the Submit 3ds Command Job to Deadline menu. The only similar difference, I'm seeing is when Deadline does not have this set. If you remove the Gamma flags in 3dsmaxcmd.exe, you'll get the Deadline look without the Gamma override. Overall, these flags seem to be creating a difference.

[Dan Marks]

Yes, I'm attempting to diagnose the issue I am experiencing with Deadline, my debugging has lead me to run the job directly from the command prompt circumnavigating Deadline completely.

I still get the same result so the problem is not with Deadline. If I can get this working at the command prompt then rendering via Deadline should work too.

The question is, why am I getting the different results rendering via 3dsmaxcmd.exe on machines with identical software setups. There must be a a file somewhere that is setting a parameter that I am missing.

[hermit.crab]

I think I found what's going on. I compared the gamma application from 3ds Max to the gamma application in 3dsmaxcmd.exe and the difference was also evident in Scanline. However, the cause of the difference depended on what was used for the decimal point in the Gamma IN/OUT flag - a point or a comma.
So in my case:
1. Using GammaValueIN/OUT = 2.2 gave wrong results
2. Using GammaValueIN/OUT = 2,2 gave identical results

I think the decimal point symbol can be changed in the Windows Language and Region settings.

[Dan Marks]

Aleksandar, I would high-five you if I could. This has been driving me around the bend. You nailed it!!!!!

[Joelaff]

So if you have your decimal point set as a period (default in the US) will the period work right? Or should you always use a comma?

[Dan Marks]

, comma is only necessary if your Windows region settings are to a location where culturally a comma is used instead of a . point/period

i.e. in the Netherlands you would write Pi as 3,145 in the UK and US 3.145

I'm in the Netherlands which is why I faced this issue. I have solved it by setting the render farm Windows region settings to UK

[DCHA34]

You could have just changed the decimal symbol without having to change the country.

[Joelaff]

So basically if you use the decimal separator set in windows then it works, right?

Sounds reasonable. I am sure support for that varies quite a bit in software, with some programs doing it “right” and requiring the character set in windows (which is, after all, why that setting exists— to localize such things to the user’s preference), while others are ignoring it and hard coding a period.

Nice find.

[Dan Marks]

Yes, from my experiments it seems that Backburner does augment the , to . but Deadline ( at least when running in 3dsCMD mode ) does not.