OctaneRender for Modo 3.03.3 [STABLE]

[Uhlhorn]

Did you click the "Apply" button?

Ah, „Apply Cuda Settings“, now it works. I did not know what this button is doing. Thanks.
(You could rename it in „Apply settings“ only, or „set“. Then it would be more clear.)

[v1adut]

Bug, found my stupidity.

Having an octane render set to use modo render cache settings, and in the same time having an octane over ride, any change in the mesh will make modo crash.

[face_off]

Having an octane render set to use modo render cache settings, and in the same time having an octane over ride, any change in the mesh will make modo crash.

Which Modo release are you on pls?

I couldn't reproduce a crash following your instructions. Do you have a more precise set of steps I can follow? (ie. start modo, create cube, etc).

Thanks

Paul

[Coulter]

I think there might be a bug in the Cuda Settings Panel...

It appears as though the settings are not accurately carried over from session to session. When I deactivate one of my cards and reopen MODO the previously deactivated card is now showing as active for "Use for Tonemap". This has happened multiple times when I completely deactivate a card, click "Apply Cuda Settings" and close MODO. When I reopen the card is either completely active or active for Tonemap only.

I'm running MODO 10.2V1 and plugin version 3.3.3.112.901.

Thanks.

[face_off]

It appears as though the settings are not accurately carried over from session to session. When I deactivate one of my cards and reopen MODO the previously deactivated card is now showing as active for "Use for Tonemap". This has happened multiple times when I completely deactivate a card, click "Apply Cuda Settings" and close MODO. When I reopen the card is either completely active or active for Tonemap only.

Hi - if there are no cards enabled for Tonemapping, then Tonemapping is turned on for all cards when you start Modo (since at least one card needs to be available for tonemapping). There was also a possible situation where the tonemapping settings would not be saved, which I have resolved in the next release (3.4.2.114) which I will post a pre-release of in the next 30 mins in the TEST thread.

Paul

[voto1979]

Hello ... stupid question!

If I use in the Preferences --> Octane --> Use Modo Render Cache
Instances will not be rendered, is this normal or is there a workaround other then convert all instances into meshes?

[face_off]

If I use in the Preferences --> Octane --> Use Modo Render Cache
Instances will not be rendered, is this normal or is there a workaround other then convert all instances into meshes?

Can you pls re-test this on the next release of the plugin (which I will post a pre-release of in the TEST thread in the next hour - it is version 3.4.3.114).

Thanks

Paul

[voto1979]

Hi,

viewtopic.php?f=34&t=54664&p=293413#p293413

The visible pattern from the displacement is gone with the new version of the plugin (octane 3.4.3.114).
But the problem with the instance (not been rendered) is still a problem.

The Modo Instance will not been rendered if you use the "Preferences" > "Octane" > "Use Modo Render Cache"

[face_off]

The Modo Instance will not been rendered if you use the "Preferences" > "Octane" > "Use Modo Render Cache"

Which version of Modo are you running pls?

Paul

[voto1979]

I use Modo 10.1v2