Page 4 of 25

Re: Version 3.06

Posted: Thu Apr 20, 2017 6:09 pm
by aoktar
GIOLETS wrote:Here also seems very stable.
In particular on big scenes, that at the moment not render with 3.05 and 3.06 TESTxx, finally works!
Great job.

Also seems to work very very well the "Texture Caching" option, I'm testing on our big scenes.

I'll keep you informed.

Thanks and many compiments for the update.
Thanks for feedback. Also thanks to other people who give feedbacks

Re: Version 3.06

Posted: Thu Apr 20, 2017 9:09 pm
by aoktar
PiotrAdamczyk wrote:Cinema r18 octane 3.06 test4

full_ao take has a "AO" render setting which has "override kernel setting" enabled.

the next take, named veins_glass has its own render setting without "override kernel", but it still takes the "override kernel" from the full_ao take.

Other than that it runs smooth, thanks!
I'll check for a fix if that's not breaking somethings

Re: Version 3.06

Posted: Thu Apr 20, 2017 9:11 pm
by aoktar
mr_seq wrote:I really love that Resolution scale option in the LV. Any chance that could be changed into a slider?
Thanks!
Maybe but my concern is that using minimal space in gui as much as possible.

Re: Version 3.06

Posted: Thu Apr 20, 2017 9:13 pm
by aoktar
Domenicozzo wrote:Hi Ahmet, thank you for this release. It's working great for me except for this weird thing about the triplanar node: when I try to apply the triplanar node to a slot already "occupied" (by an image texture or rgb node for example), Cinema freezes. Tried in different scenarios with different materials and it always happens. Is that happening just to me?

Domenico
I see and it will be fixed for next build. Thanks for note that.

Re: Version 3.06

Posted: Thu Apr 20, 2017 9:14 pm
by aoktar
cirasa wrote:I've an issue with C4D Plugin version 3.06.

On my notebook Asus N551j (Win 8.1) with GTX860M, i work with Octane plugin version 3.05.3 and everything run properly. (the geforce driver in use is: 359.12)

Today i tried the new plugin version 3.06 and Octane can't find any GPU available.
Have anyone encountered the same problem?

thanks in advance for any suggestion
You need newer drivers which support cuda8. Don't know minimal version numbers but probably 37x.xx

Re: Version 3.06

Posted: Thu Apr 20, 2017 9:17 pm
by aoktar
nycjunglist wrote:I've been using 3.06 Test4 in production for about 2-3 weeks now, and it's been pretty solid. I needed the motion blur support for Realflow fluids, so thank you for that, aoktar. Two things:

1) It seems that with the Folders option enabled in the Render Passes settings, if you use a token as a directory name, an extra folder with the token name will be created. Everything seems to save as normal in the proper directory though.

2) Is there support for Realflow wetmaps? If so, how can they be used?
octane-settings-306.jpg
1) I could not reproduce that on first try but I'll check later.
2) I need to check this but its propably a kind of vertexmap. Right?

Re: Version 3.06

Posted: Fri Apr 21, 2017 5:53 am
by mr_seq
aoktar wrote:
cirasa wrote:I've an issue with C4D Plugin version 3.06.

On my notebook Asus N551j (Win 8.1) with GTX860M, i work with Octane plugin version 3.05.3 and everything run properly. (the geforce driver in use is: 359.12)

Today i tried the new plugin version 3.06 and Octane can't find any GPU available.
Have anyone encountered the same problem?

thanks in advance for any suggestion
You need newer drivers which support cuda8. Don't know minimal version numbers but probably 37x.xx
That happend to me yesterday. I was running (16E195) 378.05.05.05f01 drivers along with Cuda8 drivers. It gave me the same result as you, no GPU & no CUDA detection.
When I installed (16E195) 367.15.10.45f01, everything was working fine.
A few hours later, Nvidia releases (16E195) 378.05.05.05f02. I'm not sure about the newest, but I can guarantee 367.15.10.45f01 runs fine.
Hope this helps!

Re: Version 3.06

Posted: Fri Apr 21, 2017 10:46 am
by sbstnc
Re: Adaptive sampling. Apologies if addressed in another thread, please point me to it if so.
Min samples, doesn't go above 1020? Curious why this is. So after looking into adaptive, including InLifeThrill's explanation, which I thought I understood, but maybe I don't.

So the min should be the lowest number of samples I would want in any area?
So if I have a scene, and one area that cleans the fastest, is noise free after 512 samples, but there are other parts of the image that need more than 512 to be clean. I put in 512 so it stops sending samples to the clean area, and then concentrates on the noisy area. Right?

BUT if I have two areas of a scene, and one area takes 2000 samples to clean (lots of point lights in this one), and another area takes 6000 sample to clean (out of focus background) I should be able to put min to 2000, so it stops firing samples into that area after 2000, and concentrates on the noisy area that needs more samples.
But with the max of 1020... 1020 is not enough anywhere?

Explanations say typical scene could have adaptive min of 256-512. Maybe I am doing something wrong but I have never, ever had a render that looked good after 256 or 512 samples in ANY area.
Again apologies if this is addressed elsewhere or if I am not understanding the "min" part of this.

Re: Version 3.06

Posted: Fri Apr 21, 2017 4:02 pm
by bepeg4d
Hi sbstnc,
here you can read about Adaptive sampling:
viewtopic.php?f=24&t=60014
In short, the "Min. adaptive samples" value defines the samples needed to have an estimation of the noise for each pixel, then the Adaptive sampling can use this estimation and starts to work.
As a rule, the more the noise threshold is high, the more samples are needed for a good noise estimation, so with 0.02, 256 samples are enough, with 0.05 you need 512 samples and so on. Going over 1020 samples are not necessary for the noise estimation.
ciao beppe

Re: Version 3.06

Posted: Fri Apr 21, 2017 4:16 pm
by Yan
So far it works great on MacOS with external 1080ti.

Thank you for this release!