OTOY Forums

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 your instructions.

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

That would indicate that your Nvidia drivers are disabled or not installed. Does Octane Standalone render?

You should have Nvidia driver 552.22 installed.

You can also try rebooting, then reinstall the plugin.

Paul

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.

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

Which version Nvidia driver did you install?
Which version of Modo17 did you install?
What is the filename of the Octane plugin that you installed?

Thanks

Paul

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)

Cheers,
Toby

Thanks Toby. I have pretty much the same environment as you, and have not seen this isuue. I have not had any other reports of this issue from any other users. So there is something amiss with how the plugin is working with your Modo17 install. Potentially the Modo17 studio installer has installed into the wrong folder on ypur system. You could try deleting the folder that contains the prime version of the plugin to ensure there is no conflict there.

Sorry I don't have an immediate solution, as this is a new issue to me.

Paul

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

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,

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 [C:\Program Files\Modo17.0v8\modo\extra\Scripts] folder...so it's sitting right next to the original Prime install.
3. Fired up Modo17.0v8 and it just works.

Why has nobody else had this problem...and what would cause modo to throw a fit like this? there is definitely something amiss with the Configs in Modo17 and Octane Prime and Studio, I just don't know where.

Cheers,
Toby