OctaneRender™ 2018.1 RC1

[Notiusweb]

Correct, Octane does not currently support FBX BlendShape deformer. We'll look into this once stability issues are out of the way.

Awesome!
THX

[Notiusweb]

Is this version, 2018, when released, going to still be named "2018"...because obviously now it is 2019, so, are we going to see it renamed to "2019"?
Or, is this "2018" really another name for "V5"...and then in more background testing, there is yet a separate "2019" (aka V6), with even newer and more added features in development?

Because with V4 out and testing V5, just want to know if 2018 is going to be 2019 at some point, or will we only get 2019 in 2020. Or will it still be 2018 in 2019.

[Goldorak]

Is this version, 2018, when released, going to still be named "2018"...because obviously now it is 2019, so, are we going to see it renamed to "2019"?
Or, is this "2018" really another name for "V5"...and then in more background testing, there is yet a separate "2019" (aka V6), with even newer and more added features in development?

Because with V4 out and testing V5, just want to know if 2018 is going to be 2019 at some point, or will we only get 2019 in 2020. Or will it still be 2018 in 2019.

Both V4 and 2018.1 (V5) were feature locked in 2018, and will still get minor updates until they are final stable releases - they were released much closer together than V3 to V5, and that pace will continue. So Octane 2019.1 is a whole new engine (V6) coming soon and this is where new all features introduced in 2019 will roll out (starting with material layers). There will be a second major engine update (V7) in 2019.x that will bring RT Core and Vulkan/Metal backend support as well.

[Notiusweb]

Is this version, 2018, when released, going to still be named "2018"...because obviously now it is 2019, so, are we going to see it renamed to "2019"?
Or, is this "2018" really another name for "V5"...and then in more background testing, there is yet a separate "2019" (aka V6), with even newer and more added features in development?

Because with V4 out and testing V5, just want to know if 2018 is going to be 2019 at some point, or will we only get 2019 in 2020. Or will it still be 2018 in 2019.

Both V4 and 2018.1 (V5) were feature locked in 2018, and will still get minor updates until they are final stable releases - they were released much closer together than V3 to V5, and that pace will continue. So Octane 2019.1 is a whole new engine (V6) coming soon and this is where new all features introduced in 2019 will roll out (starting with material layers). There will be a second major engine update (V7) in 2019.x that will bring RT Core and Vulkan/Metal backend support as well.

V7!!!!....

LOL...What does "feature locked" mean, I keep seeing that phrase used, but wasn't sure. Does it mean that 2018's features are the full extent of features it will have....

When do Substrates, Upscaling, and Anime Kernel come (as were teased in the V5 video)...
(A) a later version of 2018/V5.
(B) 2019/V6, or
(C) 2019.x/V7...
(D) All of the Above

Thanks, G!

[leehenshall]

Hi Guys,

I tested couple big scenes (with 2GB size) scenes and I realize XB1 opens way faster the orbx scenes then XB2 and RC1 any reason for that? Also cryptomatte is not stable, is crashing while saving exr a lot with GTX series GPU with RTX Gpus is working without crashes.

Cheers,
JO

Hi Guys,

me again I toke 10 different scenes and actually also the RTX as problem with cryptomatte is crashing a lot random scenes sometimes works, other times render 3 or 4 frames then crashs, I check memory and seems right enough space and etc

Is weird because the same computer can work for a while then when we open the same scene again crash while saving the image batch render export, also sometimes when we do a selection to preview the cryptomatte passes.

Cheers,
JO

I can confirm that cryptomatte is crashing and very unstable for me as well. If I only enable one element like instanceid or materialpin it might work for a while longer but will eventually crash.

If I enable them all then toggle between them in the viewport I get a hard crash with no error message.

Is this going to be fixed in RC2?

[Jolbertoquini]

Please Guys,

Cryptomatte is huge thing on production for compositing stage today supported in Nuke and After Effects we have all setup ready for that, is really important to have a fix for this random crashes I realize the Material and Obj ids is the more sensible, instances id only I had better results but not all the time I tested with different scenes and benchmark scenes also crash randomly on different machines and etc.

Cheers,
JO

[coilbook]

Can you guys add an option of your volume fog far away affecting mesh like a terrain but not sky background? It'll make distant atmosphere effect better

[Notiusweb]

I am finding that I can add a Vectron to a scene, but it is WAY unstable....

With just 1 Vectron:
-I run the risk of crashing RC1 soley because I left the default render target at 5000 s/px, whereas if I I lower it to 50, I have much higher chance RC1 does not crash.
-When I change the "bounds", it has a high crash rate too.

PS - I have little knowledge of how or where to use a Vectron yet , but it much reminds me of Volume Mediums in V3's early days, in that it crashes scenes a lot so it is hard to explore.

[Notiusweb]

Hey, is it just me, or do none of the sample scenes, ie - Fun With Vectron, work in RC1?
I can make it work in XB2, but not RC1....

[haze]

Hey, is it just me, or do none of the sample scenes, ie - Fun With Vectron, work in RC1?
I can make it work in XB2, but not RC1....

Please download the updated scene from the first post in this thread, it's been updated with the improvements of RC1.

download/file.php?id=72066