In my experience, If you're saving your image from the Blender Output Dialog, you'll get this problem. Layered EXR's (With Cryptomattes) will never be interpreted correctly in Photoshop using the EXR-io Plugin.

I've found, if you open the "Show Octane Viewport" under the "Octane Kernel" Tab and ...

Hey Paul,

Yeah I understand it's better to use the "correct" install method...but I don't seem to have a choice. Just updated to your latest release you posted on the PF Discord. (you gonna update this forum to the latest release?)
Followed your instructions from Discord, still the same result ...

Paul,

EUREKA! It's bloody work'n mate!!

1. I simply disabled Prime with your Environment Variable setting.
2. Installed Octane Studio for Modo 17 using the latest installer. After install, moved the OctaneRenderForModo17 folder from [C:\Users\MY-NAME\AppData\Roaming\Luxology\Configs] over to the ...

OK, found Prime, moved it, opened Modo 17, still the same issue.
Whats different with Modo 16 and 17...Looks like I'll have to stick with Modo 16.

Paul,

I think it's Prime plugin conflict too...how I don't know. Where can I locate the prime render plugin folder to move it out of that location, to see if that's the issue?
Is it in the main Modo install location on C: or somewhere more obscure?

Cheers,
Toby

Paul,

552.22-desktop-win10-win11-64bit-international-nsd-dch-whql.exe (Downloaded from Nvidia, and machine backdated to that driver as I was running a newer one)

Modo17.0v8.207049.msi (From the foundry Website)

OctaneRender_for_Modo17_2024_1_0_201_STUDIO.exe (your direct link here in this forum ...

Paul,

Did a complete uninstall, restart, reinstall of Modo 17, Nvidia Drivers and Octane modo 17 and still have the same issue...Installed Octane Standalone too, it works perfectly.

Does an Nvidia STUDIO or GAME READY driver make a difference? I've been using the Studio Driver

The 552.22 drivers are installed...Blender Octane works perfectly...and Modo 16.0v8 works as well.
Maybe I'll uninstall everything related to modo 17 and try again.

for further info...I'm using modo 16.0v8 with that Octane Studio version too (modo 15-16 build of course) with no issues...so it seems like a conflict with the Prime version that came with modo17.0v8 and this studio version. Prime version is disabled and Nvidia Driver 552.22 is being used as per ...

Paul,

Sorry for the missing info. Windows 10. Studio Plugin: OctaneRender_for_Modo17_2024_1_0_201_STUDIO.exe...... Deleted Configs, yeah.