Renders saved by Lightwave (I don't want it to !) Tweet

[Mastoy]

Hello everyone,
I'm using LW 2018.0.4 and Octane 3.08.1 and something is bugging me :
I use the render passes node from Octane to save my renders (Beauty + other passes).
In the LW render properties, NOTHING is checked (Buffers tab or Output tab)
But still LW continues to write files called Final_Render###.png in my "Renders" directory.
How can I stop it from doing that ?
Cheers !

[hkleton]

Disconnect the render passes .
Only that will prevent saving ...

[juanjgon]

Hmm, this can be a problem in the LightWave side, because the plugin doesn't control how the image is exported using the LightWave native saving functions. Perhaps a workaround could be set an empty or not valid path for the LW images.

I'll check it.

Thanks,
-Juanjo

[Mastoy]

I checked with the Lightwave team and as soon as you remove the Octane plugins, the bug disappears.

Here is what they said :
You should get that reported to JuanJo - so he can see where the issue is. Whether it's in his plugin, or something else - he can help us isolate the issue.
Because this is in a 3rd party plugin - it needs to go to them first.
Thank you for your report.

Thx !

[3dreamstudios]

We have found that setting up the LW Render Properties panel in such a way to MATCH what is going to be saved by Octane is needed when we render with network LWSN.exe with render manager. Render manager is looking for the native LW render properties so it knows what will be saved...but Octane is what is actually saving files.

Attached is a screen shot of what works for us. Notice in NATIVE dialog we add the _Main which is what OCTANE will add at render time, but we don't include that in the name on Octanes side....it's a mess but it works everytime thus far.

What would be nice for us is to allow JPG saving from Octane Render Passes, and even better integration with native dialog. That way Octane info comes directly and entirely from the Native Render Properties panel. Right now that is not the case. There is a checkbox to use NAME but that actually has a bug and adds the _Main__Main to the names saved...messes up our render manager looking for final frames.

Hope that all makes sense to you and Juanjo, for a future update.

[LightwaveGuru]

"Attached is a screen shot of what works for us"

Thats what i say in my answere in the nother thread...

btw

that is no wonder.
you have to assign a different name for the color layer which is saved as .jpg. for example with the prefix "preview" before the name.
if you give the same name twice so once for lw native and once for the octane layer and save it in the same folder ...
what do you mean what happens then?

snip lwguru

[ArtMooney]

This problem is still in Octane 4.00.0.16. Any news for a solution, it's starting to get a bit annoying?

Other than that - fantastic work!