Well, with 17.1v1 the error description is now different and specifically talks about disabling the Prime or Studio+ version of Octane kit... much clearer than before.

G

The last of both: modo 17.0v8 (with the eol license now) and OctaneRender_for_Modo17_2024_1_0_201_STUDIO
But actually in the log says OctaneRender Prime 2023.1.2 (13000200), that -fun fact- I never installed after the complete OS reset... lol!

Ok, uninstalled 2024.1, today I discover that modo ...

Thanks.
I have only installed the Studio+ subscription version... I don't know nothing about PRIME version: is there a documentation about that, so I can learn how to disable it?

Hello, I recently moved from Win10 to Win11 with a fresh install, and now on modo launch I get this error:
I reinstalled the plugin but the error persists.
Any suggestion?

G

Hello Paul,
is there an estimated release date for a build with analytic lights support?

Thanks.
Regards,

G

Thanks for the answer Paul.
Yeah, I already moved all my data to the local drive, no resources on the network. And there are no problems with RAM (scene occupation is high because of meshed RealFlow simulations that modo keeps in memory for all frames: luckily I have 128GB and they fit well ...

Hello,
I'm currently rendering a 375 frames sequence in Octane for modo (build 190 on modo 16.1v7 Windows10): it takes roughly 8/9 minutes per frame, but after 1 hour of rendering, modo freezes for 20-60 minutes, then comes back to life, renders a pair of frames back at 8/9 minutes per frame, then ...

Ok, got it: you're talking about Camera Motion Blur checkbox. Correct?

G

Hi Paul, I'm not able to find the checkbox you're talking about... Can you please attach a screenshot?

G

Hi, I'm working on a project with multiple cameras. In modo, I animated the "Render Camera" option, so it switches to the correct one while rendering the animation.
I tested the support of multiple cameras switching with Octane in a simple scene, and it worked, but it isn't working now on my scene ...