OctaneRender™ 3.0 for LightWave™ - Test build 3.07.0.0 Tweet

[BorisGoreta]

But as I understood they will fix that, no ?

[juanjgon]

But as I understood they will fix that, no ?

Yes, the dev team will try to fix it.

Thanks,
-Juanjo

[BorisGoreta]

Octane does not support this file type anymore, it is 32 but format which used to work before.

[roeland]

I think 32-bit monochrome works, but not 32-bit RGB. We can fix that in the next Octane version.

[BorisGoreta]

But the exact same image was working some versions before because I was doing other projects with it.

[abstrax]

But the exact same image was working some versions before because I was doing other projects with it.

It was a bug in the 3rd party library we are using. Roeland fixed it with the stable 3.07.

[Jackytalpalar]

Hey Juanjo, I'm having trouble with the Network options, now Lightwave doesn't remember if a network daemon is enabled, from session to session...

[juanjgon]

Hi,

The network options are a global setting on the system. I mean, if you configure them from Standalone the plugin settings will be overridden. Can this be your problem?

Thanks,
-Juanjo

[Jackytalpalar]

Hi,

The network options are a global setting on the system. I mean, if you configure them from Standalone the plugin settings will be overridden. Can this be your problem?

Thanks,
-Juanjo

I don't think so, I never use the standalone. In previous versions LW always remembered the network settings and it was easy to use the render-q, now I need to check the box every single time I open LW. I'ts not that terrible as it is, but was better before

[juanjgon]

Hey Juanjo, I'm having trouble with the Network options, now Lightwave doesn't remember if a network daemon is enabled, from session to session...

I think that this problem has been fixed in the final 3.07 Octane core: "Fixed loading of the net render daemon selection from the preferences.", so it should be also fixed in the next build of the LightWave plugin that I want to release later this week.

Thanks,
-Juanjo