OctaneRender™ Standalone 3.06 Tweet

[kavorka]

please, pretty please, add autosave exr feature

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

[abstrax]

To be clear on this please,
What was Expected Exposure, is now Adaptive Strength -?-

./rrb

No, "expected exposure" is used for scaling down the noise estimate and for scaling up the minimum samples (see viewtopic.php?f=24&t=60014). "Adaptive strength" was removed after the first test build, because it only complicated things and wasn't very useful.

[Jorgensen]

i'm getting an error, not sure if it's caused by this release.....

sometimes octane render window stops and i have to restart octane.

it does not seem to be a gpu ram issue.

does anyone know what could cause this problem?

jorgensen

[nextvr]

A question about network rendering with this release (downloaded last night, so very latest builds):

We've got a linux machine with OctaneRender_3_06_linux installed and running , but the artist on Windows running OctaneRender_for_Maya_3.06t4_-_10.13 gets a message in the network render UI that the linux slave version is incompatible. Are these two known to work together or is there another version of standalone for linux we should be using?

[abstrax]

A question about network rendering with this release (downloaded last night, so very latest builds):

We've got a linux machine with OctaneRender_3_06_linux installed and running , but the artist on Windows running OctaneRender_for_Maya_3.06t4_-_10.13 gets a message in the network render UI that the linux slave version is incompatible. Are these two known to work together or is there another version of standalone for linux we should be using?

Yes, that's most likely because OctaneRender_for_Maya_3.06t4_-_10.13 is of version 3.06 test 4 (3060003) while this release is a stable 3.06 release (3060005).

[abstrax]

i'm getting an error, not sure if it's caused by this release.....

sometimes octane render window stops and i have to restart octane.

it does not seem to be a gpu ram issue.

does anyone know what could cause this problem?

jorgensen

Could be all kinds of reasons. First thing to check is the log. What does is the first CUDA error message you can see in the log?

[nextvr]

A question about network rendering with this release (downloaded last night, so very latest builds):

We've got a linux machine with OctaneRender_3_06_linux installed and running , but the artist on Windows running OctaneRender_for_Maya_3.06t4_-_10.13 gets a message in the network render UI that the linux slave version is incompatible. Are these two known to work together or is there another version of standalone for linux we should be using?

Yes, that's most likely because OctaneRender_for_Maya_3.06t4_-_10.13 is of version 3.06 test 4 (3060003) while this release is a stable 3.06 release (3060005).

Ah thanks. In case this gets anyone else -- The account downloads page shows only "t" versions of the 3.06 maya plugin and only non-t versions of the 3.06 standalone. You'll find the 3.06t4 Standalone download posted in the Development Build Releases forum.

[c4d]

please, pretty please, add autosave exr feature

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

HI, otoy dev team, would u guys please don't ignore our request please? autosave is really important feature that several engines are already have, but not in octane, or should I say you guys are never never never losing rendering process during any kind of issues like gpu too heat or crash? even the new vray 3.5, they already support autosave and resume feature, same to corona render. so you guys just hit the render button and let many gpu running, finally you always get what you want and never had crash or any issue that cause losing render process???

[3dworks]

apologies if i repost this same question here from the development forum, i found out only now that 3.0.6 is final, but have to wait until it is supported by the LW plugin.

i did see reported this already somewhere else, just not sure if that has been fixed: when using the PMC kernel, on my networked windows machine with 5 x geforce 980ti GPU's connected, i can see that the GPU activity never goes beyond 75% on the single GPU. in fact, the fans don't even make any noise when rendering that way. totally expected behaviour when rendering with path tracing: 100% GPU usage and quite some fan noise! has this been fixed with the latest stable update? using octane with the latest lightwave plugin, here...

cheers

markus

[coilbook]

can we have a feature to add object from the scene where camera will always autofocus on it no matter where it is on the screen (center or corner)