OctaneRender™ 2018.1 RC1 Tweet

[haze]

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.

Does this happen with any scene and any vectron node you have? Would you mind sending the contents of your log window?

[haze]

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?

We'll look into the first issue and try to reproduce it. Roeland has fixed the second issue for RC2 already.

Correction: Roeland fixed both issues for next release.

[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.

Does this happen with any scene and any vectron node you have? Would you mind sending the contents of your log window?

Hi, thx!
Okay, this I am new to also....
In standalone I created a log window, where does it save the log to when it crashes?

[haze]

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.

Does this happen with any scene and any vectron node you have? Would you mind sending the contents of your log window?

Hi, thx!
Okay, this I am new to also....
In standalone I created a log window, where does it save the log to when it crashes?

Sorry, left out some important details. I'll send you a PM.

[Notiusweb]

It appears if a scene crashes, the log window also crashes, so it doesn't help with crashes.
You can save as a text file only while the app is in operation.

[Notiusweb]

Maybe my PC is a weak POS, but man...when a Vectron scene does work, it really struggles almighty to render the scene.
For 1 texture I would think it could go super fast, it is supposed to have a low geometry cost, right? (the geometry doesn't even say what it is...)
Whatever this Vectronian thing is my GPUs are busting their a$$es off....

This was 2:30 for 300 s/px @1080p on a zoom-in shot.

But when it does finish, really cool, I can almost feel the larvae growing in the mutagnic pod-sacks.

EDIT



Oh...So, Vectron can make a geometry without a mesh footprint on the scene, but then still, Octane now has to contend with lighting the 'geometry' as if were a mesh, and a very highly displaced mesh, at that?
So, it has to independently trace light through all the nooks and crannies you generate with Vectron, right, and that's why it is so super duper demanding?

[haze]

Maybe my PC is a weak POS, but man...when a Vectron scene does work, it really struggles almighty to render the scene.
For 1 texture I would think it could go super fast, it is supposed to have a low geometry cost, right? (the geometry doesn't even say what it is...)
Whatever this Vectronian thing is my GPUs are busting their a$$es off....

This was 2:30 for 300 s/px @1080p on a zoom-in shot.


But when it does finish, really cool, I can almost feel the larvae growing in the mutagnic pod-sacks.

EDIT

Oh...So, Vectron can make a geometry without a mesh footprint on the scene, but then still, Octane now has to contend with lighting the 'geometry' as if were a mesh, and a very highly displaced mesh, at that?
So, it has to independently trace light through all the nooks and crannies you generate with Vectron, right, and that's why it is so super duper demanding?

There are some issues in RC1 where SDFs would render super slow if there is any positive scaling in the scene. This will be fixed in RC2.

Sampling lights from hits on the surface is not nearly as expensive as tracing the geometry. Which is why we're looking at ways to speed it up.