I think that fix is potentially make life hard for yourself in the future.Gutmann wrote: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
The correct fix is disable the Prime version of the plug, or completely delete the Prime version of the plugin from the C:\Program Files\Modo17.0v8 folder. Moving the Studio version of the plugin will potentially cause confusion when you next run the Studio installer.
Paul