A couple of small bugs that have existed for some time:
1. Grouping render targets results in the new render target having a "(2)" at the end.
2. Saving an image defaults to the last place you saved, but this is not file specific. If you save your image and then open a new Octane file, it will ...

Minor thing:

When trying to save a render target that uses a character that is invalid in a filename (mine had " ) it currently just does nothing, took me a couple min to figure it out but a popup saying it's invalid or something could be useful.

I am trying to get the perspective correction to work in Blender Octane like it does in stand alone. It seems like nothing happens when I check it (I am in Rendered mode). Is there something else that you have to do to get it to work?

c4d wrote:please, pretty please, add autosave exr feature

Autosave the Octane file and autosave your render at x intervals. Really needed feature.

Many times we toggle from Pathtracing to direct lighting so we can have a faster feedback, when we turn back to pathtracing all our values are gone...
I know we could use nodes and switch between 2 different kernel node in the nodegraph, but we have enough nodes already.

I do this a lot too. My ...

I still don't know how to enable network rendering in BOE.
their manual doesnt seem to show it at all, and there is also no V3 manual.
It almost seems like they are telling you how to set it up in Stand Alone.

I would also like to know if I can use network rendering with BOE.

Awesome work, was gonna ask about the plants and then kept reading (We use Blender and standalone as well).

Only crit I would have is the windows seem too clean for the rest of the scene (At some parts I thought I was looking through the building).

How are you exporting the grass to standalone? We ...

Accidentally posted this is TEST 2:

Found a bug:
When using a batch render job it no longer saves out leading zeros with %f and it also adds ".0" to each filename.
We found this out when rendering an animation that we had previously run in 5.01 and it had the leading zeros and no ".0" in the ...

Accidentally posted this is TEST 2:

Found a bug:
When using a batch render job it no longer saves out leading zeros with %f and it also adds ".0" to each filename.
We found this out when rendering an animation that we had previously run in 5.01 and it had the leading zeros and no ".0" in the ...