OTOY Forums

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

I think that fix is potentially make life hard for yourself in the future.

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

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. Octane only works on my machine, if I move the Octane plugin install from the Appdata/Roaming (original install location) directory, directly into the Modo17.1v1 extras/scripts directory.

I'll try on my PC at home after work today and see if there are any differences.

Cheers,
Toby

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. Octane only works on my machine, if I move the Octane plugin install from the Appdata/Roaming (original install location) directory, directly into the Modo17.1v1 extras/scripts directory.

I'll try on my PC at home after work today and see if there are any differences.

Hi Toby

Yes, I will post the Discord version here once people have had time to confirm there are no issues.

Regarding your install issue, I have not had any other users report the problem you are having. Some things to check....

1) If you Modo->System->Open Configs Folder, what folder is opened? Does Modo open the folder that you originally installed the OctaneRender for Modo plugin into?

2) Do a search for "OctaneRenderForModo17" on your system to ensure there is not another copy of the plugin installed somewhere else

Thanks

Paul

When can we expect an update to 2024.1.2 or even 2025? Haven't seen an update since October.

Also, I'm having trouble understanding the AOV system.
Could you implement an automatic AOV node system. One-button shortcut that creates the impossibly complex AOV system automatically? 
Thanks.

When can we expect an update to 2024.1.2 or even 2025? Haven't seen an update since October.

Hi - please check the Pixel Fondue Discord channel for a test release build for Octane 2024.1.2.

Also, I'm having trouble understanding the AOV system.
Could you implement an automatic AOV node system. One-button shortcut that creates the impossibly complex AOV system automatically?

Pixel Fondue have a number of video's detailing how to use the current AOV system. An automated system could be possible, but unlikely given the time of would take, and the fact that Foundry is no longer supporting Modo.

Thanks

Paul

Paul,
Speaking of Foundry no longer supporting Modo, do you still plan to develop Octane Render for Modo moving forward?
Thanks.

leblanc980 wrote:Speaking of Foundry no longer supporting Modo, do you still plan to develop Octane Render for Modo moving forward?

The plugin will be supported for the foreseeable future, and there will be releases for new Octane versions.

Paul

I have refreshed the installers at the top of this thread with:

2024.1.2.202
- Compiled with Octane 2024.1.2
- Fixed issue where the Mesh Round Edges Visibility option was setting the Curvature Visibility
- Fixed pin names on the Octane Multiply Texture node
- Resolved issue where the Octane Texture Layer->Texture node was missing it's property sheet
- Added support for the Modo Directional Light (creates an Octane Directional Light). The Modo Directional Light "Spread Angle" is used as the Octane Directional Light "Light sample spread angle"
- Added experimental support for proxy delay, speed-up, start time and end time. These controls are on the Mesh item properties under the Proxy file name. Ensure you have Kernel->Camera Motion Blur enabled to get this working.

This will be the last Octane 2024.1 release. The next version will be compile with Octane 2025.1. Join the PixelFondue discord for test builds.

Thanks

Paul