OctaneRender for Modo 3.03.3 [STABLE]

[v1adut]

Hi Paul, I've observed that with the new release .88 that when I deactivate a gpu from the render, all the rendered values from the render images gets dropped. This was not happening before.
So if my 2 gpus rendered 220 values, and I deactivate the main gpu in order to use the system, the rendered work by this gpu is trashed. Can you confirm if this is a bug or present octane behavior.

Cheers,
Vlad

[face_off]

I've observed that with the new release .88 that when I deactivate a gpu from the render, all the rendered values from the render images gets dropped. This was not happening before.
So if my 2 gpus rendered 220 values, and I deactivate the main gpu in order to use the system, the rendered work by this gpu is trashed. Can you confirm if this is a bug or present octane behavior.

Hi Vlad - is this also happening in Octane Standalone? If so, then it is potentially a general Octane issue that needs to be reported to Otoy.

Paul

[v1adut]

I've observed that with the new release .88 that when I deactivate a gpu from the render, all the rendered values from the render images gets dropped. This was not happening before.
So if my 2 gpus rendered 220 values, and I deactivate the main gpu in order to use the system, the rendered work by this gpu is trashed. Can you confirm if this is a bug or present octane behavior.

Hi Vlad - is this also happening in Octane Standalone? If so, then it is potentially a general Octane issue that needs to be reported to Otoy.

Paul

Hi Paul can you ask them for this? I think your voice is stronger for otoy than mine.

[v1adut]

Hi Paul,
It looks like it has the same behaviors in the stand alone too. Please ask them to fix this.

Cheers,
Vlad

[face_off]

It looks like it has the same behaviors in the stand alone too. Please ask them to fix this.

Hi Vlad - can you pls post this issue in the Octane Standalone 2.24.2 release thread - where the Otoy devs will see it, and they cn ask you any follow-up questions directly.

Paul

[v1adut]

It looks like it has the same behaviors in the stand alone too. Please ask them to fix this.

Hi Vlad - can you pls post this issue in the Octane Standalone 2.24.2 release thread - where the Otoy devs will see it, and they cn ask you any follow-up questions directly.

Paul

I sent a bug ticket Paul, but they said this is normal behavior, and they do not recall that it is possible to change the gpu when pausing the render.

[face_off]

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

2.24.2.89
- Fixed issue introduced in 2.24.2.88 where changing the viewport scaling interpolation to Smooth created problems with the render region box
- Added Texture Environment Power to the Environment->Daylight panel, which can be adjusted when Use Texture Environment is enabled to adjust the power of the environment texturemap
- When the Setup window is opened (when you click a Material/Group in the Shader Tree) - if the Setup Window was already open, it will be re-opened to raise it above all other windows
- Fixed minor rounding issues related to converting Modo time to Octane time

Paul

[Obizzz]

Small but sweet fixes.

Thanks Paul!

[v1adut]

No new updates in the last month, it smells octane render 3.0

is it right? Paul

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

2.24.2.89
- Fixed issue introduced in 2.24.2.88 where changing the viewport scaling interpolation to Smooth created problems with the render region box
- Added Texture Environment Power to the Environment->Daylight panel, which can be adjusted when Use Texture Environment is enabled to adjust the power of the environment texturemap
- When the Setup window is opened (when you click a Material/Group in the Shader Tree) - if the Setup Window was already open, it will be re-opened to raise it above all other windows
- Fixed minor rounding issues related to converting Modo time to Octane time

Paul

[Flyx]

Hi !

Didn't update my octane plugin in a while, but with the last version i'm facing an issue, octane doesn't use the modo colorspace setting for my texture, they are all washed out at render while the modo renderer display the good corrected texture.

Did a miss a recent change in octane ? It was working flawlessly before and never had to change settings for my map

I'm on modo 902 and the last octane plugin .89