OctaneRender™ Standalone 1.54

[blobbybarack]

One user post a script where you can set render time instead of sample number.
It's really usefull in production.

Doesn't it give uneven grain between frames ?

Yes it can in some situation but i'm using it in a previz context. So noise is not really a problem here. I switch back to sample for final render.
I guess we could use it for shot whith slow camera/objects move too. It should be almost invisible if time is high enought but it's just a guess.

[slimSpencer]

Hi,

thanks for the update.

I'm using a 750 Ti with driver 335.23 - when i switch off alpha shadows, the card always fails:

CUDA error 719 on device 0: An exception occurred on the device while executing a kernel. The context cannot be used anymore and must be destroyed. All existing device memory allocations from this context are invalid and must be reconstructed.
-> Kernel execution failed (pt)
CUDA device 0: Path tracing failed

br

spencer

[Seekerfinder]

Thanks guys. I'm beginning to appreciate the pace once more...

Seeker

[kavorka]

Thanks for the update
I'll be testing it out tomorrow

[blobbybarack]

i've some problem with camera focus distance update.

In fact the problem i describe previously can append for any channel.

It look like when we hit the reload arrow octane only reload mesh and geometry cache. It doesn't look for reimport and update keyframe/non keyframe value (on transform for example).

Again delete and reimport or quit/reload Octane can solve the problem.

[blobbybarack]

Octane do not write "full on" alpha when render a frame where no alpha visible in a sequence where you need alpha output at an another frame.
It's can be very problematic for channel use in compositing context.
If you create a batch/comp in a compositing app, it can be very annoying to deal with nonconstant colors channels number in you images sequences.

[roeland]

i've some problem with camera focus distance update.
Octane do not update changes makes to .abc when reloading with the circular green arrow.
If you reimport the scene one more time it keep the old camera distance.

If you delete all object and reimport the scene the focus distance is updated.
If you save and close Octane the update works too.

This is due to how the Alembic library caches loaded data, once some data is loaded from the file it is kept in some cache, and a reload will just read this cache again. In fact, due to this cache, Octane can crash if you modify an Alembic file while it's open in a scene node in Octane. The easiest way to make sure all data is loaded fresh, is to write the next file with another file name and load this new file into the scene node.

--
Roeland

[blobbybarack]

write the next file with another file name and load this new file into the scene node

Good to know. Thanks.

[BroAugustine]

Thanks Roeland et al. for the update.

One thing to be noted that has changed but is not in the change log:
It appears that maxSamples regarding render calls has changed in Lua since the last update. Just wanted to make sure if this was intended though it surely effects any scripts relying on it.

The following no longer does what one would expect, i.e., a quick render of 1 sample.

Code: Select all

octane.render.start
{
    renderTargetNode = rtNode,
    maxSamples       = 1,
    callback         = renderCallback,
}

With the above, I just want a quick animation preview which is no longer quick unless I terminate it myself in the renderCallback() function. Lua now uses the maximum samples as set in the kernel node, ignoring the explicit declaration in the Lua call.

[kavorka]

I have been trying to use the new render animation script. Twice with the same animation, I had Octane hang and become non responsive after saving the image and before starting the next frame. I went back to using the unofficial script for now. Anyone else have this problem?