This is my second time trying out ORC. The output still doesn't match what I'm getting in 3ds Max. The last time I tried it, neither motion blur nor exposure was correct. It looks like there are settings for motion blur in the render job setup, though the terminology used is completely inconsistent with the kernel settings.

This time it looks like images rendered in ORC have a different gamma as they appear washed out.

paulforgy wrote:This is my second time trying out ORC. The output still doesn't match what I'm getting in 3ds Max. The last time I tried it, neither motion blur nor exposure was correct. It looks like there are settings for motion blur in the render job setup, though the terminology used is completely inconsistent with the kernel settings.

This time it looks like images rendered in ORC have a different gamma as they appear washed out.

Just to confirm - if you export to ORBX and test in the standalone does this issue persist? Which version of the engine/plug-in are you using?

paulforgy wrote:This is my second time trying out ORC. The output still doesn't match what I'm getting in 3ds Max. The last time I tried it, neither motion blur nor exposure was correct. It looks like there are settings for motion blur in the render job setup, though the terminology used is completely inconsistent with the kernel settings.

This time it looks like images rendered in ORC have a different gamma as they appear washed out.

Just to confirm - if you export to ORBX and test in the standalone does this issue persist? Which version of the engine/plug-in are you using?

Version is Max plugin 3.07, 4.44

It does not look correct in standalone either. Motion blur is enabled even though it's off in my Max scene. The Tonemap settings in standalone come in with Neutral response set to off, which seems to be the main issue. Seems as if the orbx exporter is not grabbing settings from the kernel and camera settings tab within Max's render setup dialog. This would also explain the exposure issues I was having last time I tried to use ORC.

Aside from those issues, there seems to be some real discrepancies with naming conventions. In Max, the same setting is found in the render setup dialog->camera, under 'Imager' and is called 'Nonliner tone mapping' whereas in standalone and in an octane camera wihtin Max, it's 'imager' or 'Tonemap' and 'Neutral response' and the check boxes behave in an inverted manor.

paulforgy wrote:This is my second time trying out ORC. The output still doesn't match what I'm getting in 3ds Max. The last time I tried it, neither motion blur nor exposure was correct. It looks like there are settings for motion blur in the render job setup, though the terminology used is completely inconsistent with the kernel settings.

This time it looks like images rendered in ORC have a different gamma as they appear washed out.

Just to confirm - if you export to ORBX and test in the standalone does this issue persist? Which version of the engine/plug-in are you using?

Version is Max plugin 3.07, 4.44

It does not look correct in standalone either. Motion blur is enabled even though it's off in my Max scene. The Tonemap settings in standalone come in with Neutral response set to off, which seems to be the main issue. Seems as if the orbx exporter is not grabbing settings from the kernel and camera settings tab within Max's render setup dialog. This would also explain the exposure issues I was having last time I tried to use ORC.

Aside from those issues, there seems to be some real discrepancies with naming conventions. In Max, the same setting is found in the render setup dialog->camera, under 'Imager' and is called 'Nonliner tone mapping' whereas in standalone and in an octane camera wihtin Max, it's 'imager' or 'Tonemap' and 'Neutral response' and the check boxes behave in an inverted manor.

If the export to ORBX/SA is showing these issues, then that is apparently a bug in the MAX exporter - motion blur is determined by shutter time - is that also not right in the SA export. Can you post a screen shot of the inverted neutral reponse checkbox? NR is off by default, but if you turn it on in Max, it should carry over to the exporter.

I assume you are testing in the same 3.07 version as the plug-in and not 3.08+?

The gamma issue was due to a non Octane setting in Max, not an ORC/Octane bug.

Motion blur does seem to be a legitimate issue. There doesn't appear to be an on/off setting in standalone? The on/off setting in the Max Octane Kernel settings, nor the motion blur duration, seems to be exported or reflected in the orbx file.

Hi Paulforgy,Octane for 3dsMax 3.07 - 4.44 seems to work well exporting to .orbx.As you can see in my screenshots, MB matches and Gamma too.I do not know your settings, you could take a look at mine; could they help you?RegardsParide

paride4331 wrote:Hi Paulforgy,Octane for 3dsMax 3.07 - 4.44 seems to work well exporting to .orbx.As you can see in my screenshots, MB matches and Gamma too.I do not know your settings, you could take a look at mine; could they help you?RegardsParide

Gamma was an issue on my end.

Motion blur doesn't work. Try turning it off in kernel settings and see if that looks correct in standalone.

paride4331 wrote:Hi Paulforgy,Octane for 3dsMax 3.07 - 4.44 seems to work well exporting to .orbx.As you can see in my screenshots, MB matches and Gamma too.I do not know your settings, you could take a look at mine; could they help you?RegardsParide

Gamma was an issue on my end.

Motion blur doesn't work. Try turning it off in kernel settings and see if that looks correct in standalone.

paride4331 wrote:Hi Paulforgy,Octane for 3dsMax 3.07 - 4.44 seems to work well exporting to .orbx.As you can see in my screenshots, MB matches and Gamma too.I do not know your settings, you could take a look at mine; could they help you?RegardsParide

Gamma was an issue on my end.

Motion blur doesn't work. Try turning it off in kernel settings and see if that looks correct in standalone.

Is it correct?RegardsParide

No. Try exporting from Max with motion blur set to off. Import that into standalone, and it will still be on.