Hello World: OctaneRender 4 is here

[Jolbertoquini]

@Haze,

But what About "AI adaptive sampling" to replace our clunky adaptive sampling system ?
or maybe the current system can be feed with a noise map based on the difference between the beauty and the denoise pass ?

There is a talk about that at GTC 2018 :
https://2018gputechconf.smarteventsclou ... tleSort&p=

S8788 - Adaptive Ray Tracing Rendering Powered by Deep Learning
Session Speakers

Andrew Tao - Distinguished Engineer, Director for Deep Learning Applied research, NVIDIA
Carsten Waechter - Ray Tracing Software Architect, NVIDIA

Session Description

This session will present a proof of concept where a deep neural network was trained with pairs of Iray ray traced images (one arbitrary ray tracing iteration number and one fully converged image) and theirs structural similarity index (SSIM). Originally thought as a method for measuring the similarity between two images, SSIM index can also be viewed as a quality measure versus a reference image or, in our case, as a ray tracing rendering progress. The DNN can now from any render iteration of arbitrary scene infer a rendering progress estimator but also provides heat map pictures of the scenes that can be used for adaptive rendering, focusing ray tracing engine power on appropriate zones.

Or is it already the same technique used in AI lights ?

Interesting "AI adaptive sampling" I was wondering this to about the AI lights would be good to know

[Jolbertoquini]

Hi Guys,

I saw a post from Goldorak viewtopic.php?f=9&t=64990&hilit=coverage
about - bent normal AOV vector +coverage pass I'm really interesting on the Coverage pass will be add soon?

I remember I asked 2 or 3 year ago about coverage pass to use with material ID.

Any news about and if is already there how to use Please?

Cheers,
JO

[Silverwing]

Hi there everyone.
First of thanks to the developers for their hard work!
Great new features. I am really excited.

I did a couple of tests that I want to share here.
I tried to make this as scientific as possible. I did a system restart before every test, also I kept the settings unchanged.
There were two tests for each setup (yes, a lot of restarts), the median values have been taken. They did not vary much though.

Thanks to Cornelius Dämmrich for providing the scene and allowing me to use it as demonstration.
Unfortunately this scene is under copyright, so I con´t make it public.
I used it since it is a really complicated heavy scene built for production, not for testing and therefore might represent a closer to reality example of how Octane behaves under stress.

Here are my system specs:
Motherboard: ASUS X-99-E WS
Processor: i7 5960x, 8 Cores - 16 Threads, 3.0 GHz
Ram: 64 GB DDR4
Graphics: 3X GTX 1080 Ti (Reference Design)
PSU: 1500 W, Corsair AX 1500i
HDDs: Samsung 850, Samsung 840, 2 X Seagate 2 TB
CASE: Lian Li PC-X2000FN

The scene files were read of the Samsung 850 SSD

Octane 3.07 C4D
Scene Load --------------- 1:14 Min
Rendering 256 SSP ----- 1:55 Min
Average Ms/Sec ---------- 5.3 Ms/Sec
Scene Size ------------------ 5.60 GB
Scene Size & System --- 6.10 GB
System RAM -------------- 21.5 GB

3.07 C4D Octane

Octane 3.08 RC2 C4D
Scene Load --------------- 1:24 Min
Rendering 256 SSP ----- 1:47 Min
Average Ms/Sec --------- 5.6 Ms/Sec
Scene Size Vram -------- 5.60 GB
Overall Vram ------------- 6.10 GB
System RAM -------------- 22.0 GB

3.08 RC2 C4D Octane

Octane 3.07 Standalone
Opening ORBX ------------ 1:42 Min
Scene Load ----------------- 0:52 Min
Rendering 256 SSP ------ 2:03 Min
Average Ms/Sec ---------- 5.2 Ms/Sec
Scene Size Vram --------- 5.73 GB
Overall Vram -------------- 6.10 GB
System RAM -------------- 16.5 GB

3.07 Octane Standalone

Octane 3.08 RC2 Standalone
Opening ORBX ------------ 1:42 Min
Scene Load ----------------- 0:55 Min
Rendering 256 SSP ------ 1:55 Min
Average Ms/Sec ---------- 5.5 Ms/Sec
Scene Size Vram --------- 5.73 GB
Overall Vram -------------- 6.10 GB
System RAM -------------- 16.5 GB

3.08 RC2 Octane Standalone

Octane 4 XB1
Opening ORBX ------------ 1:40 Min
Scene Load ----------------- 0:22 Min
Rendering 256 SSP ------ 2:20 Min
Average Ms/Sec ---------- 4.3 Ms/Sec
Scene Size Vram --------- 7.07 GB
Overall Vram -------------- 7.45 GB
System RAM -------------- 17.5 GB

4.0 XB1 Octane Standalone

Octane 4 XB1 Denoising
Scene Size Vram----------- 8.95 GB
Overall Vram --------------- 9.72 GB
System RAM ---------------- 18.9 GB
Rendering 256 SSP ------- 2:22 Min

4.0 XB1 Octane Standalone Denoised

A couple of things:
Of course the C4D Version needs a lot more system RAM because the whole application with the scene has to run in the background.
There is a slight variation in the renders. This is because the scene was setup by Cornelius with a Coherent Ratio of 0.5

Unfortunately I not only noticed a slow down of the render speed by about 25 Sec. I also noticed a vastly increased V-Ram usage. Even without AI-Denoiser!
The V-Ram of the same scene goes up 1.34 GB from 5.73 GB to 7.07 GB.

I do understand that the AI-Denoiser needs some more data and therefore needs more V-Ram. But I would like to see the initial V-Ram being used staying the same as in the older versions of Octane.

Please note that this is not meant offensive in any way. I love octane and I thought when I share things like that I might help to make it better.

[haze]

Hi there everyone.
First of thanks to the developers for their hard work!
Great new features. I am really excited.

I did a couple of tests that I want to share here.
I tried to make this as scientific as possible. I did a system restart before every test, also I kept the settings unchanged.
There were two tests for each setup (yes, a lot of restarts), the median values have been taken. They did not vary much though.

Thanks to Cornelius Dämmrich for providing the scene and allowing me to use it as demonstration.
Unfortunately this scene is under copyright, so I con´t make it public.
I used it since it is a really complicated heavy scene built for production, not for testing and therefore might represent a closer to reality example of how Octane behaves under stress.

Thanks for this, it is of course very helpful. You'll be happy to hear that the next release will have fixes for the problems you mention - we now have the render speed of v4 very near matching v3, and the VRAM usage is far closer now too. There is more tuning to happen in the next few weeks as well.

V4 now tends to use less system memory than V3.

The denoiser is a separate issue however.

I'll post an update when we have a better idea of when the next release will be.

[coilbook]

Hi there everyone.
First of thanks to the developers for their hard work!
Great new features. I am really excited.

I did a couple of tests that I want to share here.
I tried to make this as scientific as possible. I did a system restart before every test, also I kept the settings unchanged.
There were two tests for each setup (yes, a lot of restarts), the median values have been taken. They did not vary much though.

Thanks to Cornelius Dämmrich for providing the scene and allowing me to use it as demonstration.
Unfortunately this scene is under copyright, so I con´t make it public.
I used it since it is a really complicated heavy scene built for production, not for testing and therefore might represent a closer to reality example of how Octane behaves under stress.

Here are my system specs:
Motherboard: ASUS X-99-E WS
Processor: i7 5960x, 8 Cores - 16 Threads, 3.0 GHz
Ram: 64 GB DDR4
Graphics: 3X GTX 1080 Ti (Reference Design)
PSU: 1500 W, Corsair AX 1500i
HDDs: Samsung 850, Samsung 840, 2 X Seagate 2 TB
CASE: Lian Li PC-X2000FN

The scene files were read of the Samsung 850 SSD

Octane 3.07 C4D
Scene Load --------------- 1:14 Min
Rendering 256 SSP ----- 1:55 Min
Average Ms/Sec ---------- 5.3 Ms/Sec
Scene Size ------------------ 5.60 GB
Scene Size & System --- 6.10 GB
System RAM -------------- 21.5 GB

01 Octane C4D 3.07.png

Octane 3.08 RC2 C4D
Scene Load --------------- 1:24 Min
Rendering 256 SSP ----- 1:47 Min
Average Ms/Sec --------- 5.6 Ms/Sec
Scene Size Vram -------- 5.60 GB
Overall Vram ------------- 6.10 GB
System RAM -------------- 22.0 GB

02 Octane C4D 3.08 RC2.png

Octane 3.07 Standalone
Opening ORBX ------------ 1:42 Min
Scene Load ----------------- 0:52 Min
Rendering 256 SSP ------ 2:03 Min
Average Ms/Sec ---------- 5.2 Ms/Sec
Scene Size Vram --------- 5.73 GB
Overall Vram -------------- 6.10 GB
System RAM -------------- 16.5 GB

01 Octane 3.07.png

Octane 3.08 RC2 Standalone
Opening ORBX ------------ 1:42 Min
Scene Load ----------------- 0:55 Min
Rendering 256 SSP ------ 1:55 Min
Average Ms/Sec ---------- 5.5 Ms/Sec
Scene Size Vram --------- 5.73 GB
Overall Vram -------------- 6.10 GB
System RAM -------------- 16.5 GB

02 Octane 3.08 RC2.png

Octane 4 XB1
Opening ORBX ------------ 1:40 Min
Scene Load ----------------- 0:22 Min
Rendering 256 SSP ------ 2:20 Min
Average Ms/Sec ---------- 4.3 Ms/Sec
Scene Size Vram --------- 7.07 GB
Overall Vram -------------- 7.45 GB
System RAM -------------- 17.5 GB

03 Octane 4.0 XB1.png

Octane 4 XB1 Denoising
Scene Size Vram----------- 8.95 GB
Overall Vram --------------- 9.72 GB
System RAM ---------------- 18.9 GB
Rendering 256 SSP ------- 2:22 Min

04 Octane 4.0 XB1 DN.png

A couple of things:
Of course the C4D Version needs a lot more system RAM because the whole application with the scene has to run in the background.
There is a slight variation in the renders. This is because the scene was setup by Cornelius with a Coherent Ratio of 0.5

Unfortunately I not only noticed a slow down of the render speed by about 25 Sec. I also noticed a vastly increased V-Ram usage. Even without AI-Denoiser!
The V-Ram of the same scene goes up 1.34 GB from 5.73 GB to 7.07 GB.

I do understand that the AI-Denoiser needs some more data and therefore needs more V-Ram. But I would like to see the initial V-Ram being used staying the same as in the older versions of Octane.

Please note that this is not meant offensive in any way. I love octane and I thought when I share things like that I might help to make it better.

Thanks for sharing! Otoy also said there won't be any geometry processing time and with brigade it will be a realtime rendering

[vijay]

Denoiser crashes for me every single time. I've tired it at least 20 times in many different configs to see if there was some disagreement between settings in other areas but so far no good. Tested administrative privileges to ensure that wasn't the issue. I run Octane with 2 Titan Blacks. Updated to the latest driver available 391.24. Total crashville. Please help!

Currently, denoiser is crashing on the systems that don't support AVX instructions. Processors released before 2011 Q3 don't have AVX support. This will be fixed in next release.

[Silverwing]

Hi there everyone.
First of thanks to the developers for their hard work!
Great new features. I am really excited.

I did a couple of tests that I want to share here.
I tried to make this as scientific as possible. I did a system restart before every test, also I kept the settings unchanged.
There were two tests for each setup (yes, a lot of restarts), the median values have been taken. They did not vary much though.

Thanks to Cornelius Dämmrich for providing the scene and allowing me to use it as demonstration.
Unfortunately this scene is under copyright, so I con´t make it public.
I used it since it is a really complicated heavy scene built for production, not for testing and therefore might represent a closer to reality example of how Octane behaves under stress.

Thanks for this, it is of course very helpful. You'll be happy to hear that the next release will have fixes for the problems you mention - we now have the render speed of v4 very near matching v3, and the VRAM usage is far closer now too. There is more tuning to happen in the next few weeks as well.

V4 now tends to use less system memory than V3.

The denoiser is a separate issue however.

I'll post an update when we have a better idea of when the next release will be.

HI Haze. You are right. I am very happy to hear that. Thank you very much for your answer!
Looking forward to the new builds.

As I said, I get that the denoiser needs its memory. I am looking forward what the future will bring. Maybe it can be tweaked here and there

Cheers,
Raphael

[calus]

Where the OSL atmospheric script could be found ?

I suppose this is based on this one :
https://github.com/BenSimonds/NishitaSky
https://bensimonds.com/2014/10/02/atmos ... -with-osl/

needs usual adjustements to make it work with Octane.

[dinf]

The OSL atmospheric script was marked as "roadmap for final release" on the video, so no wonder if there is only rudimentary stuff, or still nothing to find atm.

[stefan_guzzo]

WOW, just WOW

Awesome work guys [:RESPECT]
...and so much features to come along in the future ... think this is gonna be a really massive leap for all of us who love Octane so much!

(and it's just so especially perfect to arrive about now, because my new Workstation build is finally going to be completed untill end of april and I was really bothered about putting in 2 XEON Scalable Gold 6148 CPUs (mainly for CPU render tasks) & 192 GB RAM aside the obligate 4x GTX 1080Tis.... but with the outstanding new OOC-Geo-Features I feel this decision was just right and huge scenes may really benefit s lot from this system setup).

Keep up the good work guys!