OctaneRender™ 2018.1 RC1 Tweet

[abstrax]

I have to ask-
If Octane's Kernel allowed 'Parallel Samples' to go up to 64, as opposed to 32, would it render 2x as fast?!!!

Thanks

No, it doesn't. At most a couple of percent, but keep in mind that even a value of 32 requires a sample state buffer of ~1.3GB and doubling the parallel samples will double the sample state buffer, i.e. even on GPUs with much VRAM you starting to lose a significant amount of memory which may result in more OOC memory being used, which slows down rendering rather dramatically.

[abstrax]

I already can report that several ABC files I have are not importing into RC1, but were importing fine into XB2.
Issues consist of Octane freezing during AI Cache, and missing geometry in the ABC file.
In each case if left on, ABC files in Octane RC1 will cause GPUs to disconnect and driver reset.

DPC Latency shows no spike, and # GPUs is not a factor either. Seems that RC1 just has a very very rough time with ABC files.

Could you send us some example files showing the problem? No idea what's going on, because all the loading of Alembic geometry and processing it is done on the CPU.

Thx, I PM'd an ABC file.

I just tried the file and don't see any problems. It renders fine and updates geometry without any delays or crashes or whatsoever. I also can't think of any change that could have caused the issues you describe.

[abstrax]

Still very slow compared to V4.

What is slow? Rendering? We haven't noticed any major differences between version 4 and 2018. Could you maybe send me an example scene, your hardware setup and the render times you see in both versions? We will have a look at it as soon as possible.

[abstrax]

hi otoy,
were you able to find out why ai light creates fireflies with a lot of lights? Will it be fixed soon? Denoiser removes them but I think it makes image not as sharp and detailed.

Thank you for your scene, but we didn't have the chance to look into it yet, but will do so in the coming days.

[abstrax]

I still cannot get 2018 RC1 to play FBX animations on the timeline. (This goes back to prior versions of V4 as well.)
Alembic updates as you scrub through timeline with each frame, but not FBX.

What does it mean? Does the geometry not change or change very slowly? We would need an example scene, since all the FBX scenes we have work as expected. Thank you.

[abstrax]

In the file I am working in right now Octane crashes immediately when I am trying to render any of my rendertargets. (does not happen in 4.01)
This file is under an strict NDA, I will send you as much detail as I can to the email of Marcus.

Thank you for the scene file. The bug will be fixed with the next 2018 release.

[Notiusweb]

I just tried the file and don't see any problems. It renders fine and updates geometry without any delays or crashes or whatsoever. I also can't think of any change that could have caused the issues you describe.

Hi, thank you so much for looking at.
Very surprised to hear that, so I tried again myself and saw no issues....which made me look further and realize what I was additionally doing in my scene.

Using the Wrench icon for the ABC node's settings, I am resizing the "Length Unit" of the ABC alembic in the scene from Meters to Centimeters, and this is what is causing the issue.

Thus I am finding-
In XB2 resizing the ABC from Meters to Centimeters causes no issue,
in RC1 resizing the ABC from Meters to Centimeters is causing an issue.

Using the In-Scene Wrench icon for the ABC's geometry node, can you resize the Length Unit from Meters to Centimeters, and see if it causes an issue when then trying to modify the viewport.

THX!

[PolderAnimation]

Could we or is there and option that we could unload ABC files in our scene. I constantly have to close octane when I want to save an new ABC file. And I do that allot when prototyping and working on lookdef.

[enricocerica]

Could we or is there and option that we could unload ABC files in our scene. I constantly have to close octane when I want to save an new ABC file. And I do that allot when prototyping and working on lookdef.

+1

[haze]

I keep coming with requests but just trying to make octane better :).
It would be nice to have the option to make reference copys of placement nodes. So when you adjust one all of the other will adjust too.
Just an idea. Cheers,

You can do this currently if you expand the node out of the transform pin, then copy and paste the placement node - at the moment we can't do reference copies because the node system is designed very carefully around the links you see in the editor.