Page 8 of 31

Re: Beta 0.72 (SDK 1.20)

Posted: Tue Jul 23, 2013 10:52 pm
by ChrisVis
Another important thing I found out is about the samples value of an octane light (IES or Area light).
It seems not to have much effect when changing the sample rate value in the octane light tag, so I always got lots of noise when using several lights and wondering how the samples value seems to change nothing.
Then I discoverd, that the sample value in the details tab of the cinema light object has a great impact of reducing light emitting noise when using higher samples there (for e.g. 500 or 1000 samples). I dunno if it is meant to work like this (aoktar?), maybe the sample rate value in the octane light tag isn`t correctly connected to the cinema light object sample value?

This results in much cleaner images... hope that helps somebody to get rid of grain and noise.

Greetings,
ChrisVis

Re: Beta 0.72 (SDK 1.20)

Posted: Tue Jul 23, 2013 11:06 pm
by aoktar
Hi Chris,
Nice to hear this words. I hope that you can do much more cool works. Also i can't wait to see more c4d octane renders ;)

For questions, i must to see your materials on your scene. Maybe a bug. For lighttag, i'm going to check effects of sample for lights and emission on materials. Arealight details samples has no effect on output parameters.

Re: Beta 0.72 (SDK 1.20)

Posted: Wed Jul 24, 2013 8:58 am
by huebner
i do habe the same problem with the texture paths!
sooner or later they are lost!

would be great if you could fix it!

Re: Beta 0.72 (SDK 1.20)

Posted: Wed Jul 24, 2013 9:17 am
by aoktar
huebner wrote:i do habe the same problem with the texture paths!
sooner or later they are lost!

would be great if you could fix it!
Version?

Re: Beta 0.72 (SDK 1.20)

Posted: Wed Jul 24, 2013 6:14 pm
by huebner
hi

cinema version r14

is it possible that the textures in the octane materials should be recognized with the whole texturpath? there is only the name of the texture in the material.
i do also work with presetted texturepaths i(under preferences), means that cinema finds any texture located in a certain folder.
does the plugin support this functionality? would be great.

its angry that octane looses the textures! don't know how to cope with it!

thank you for help!

the rest of the plugin is really great!

Re: Beta 0.72 (SDK 1.20)

Posted: Wed Jul 24, 2013 8:17 pm
by aoktar
huebner wrote:hi

cinema version r14

is it possible that the textures in the octane materials should be recognized with the whole texturpath? there is only the name of the texture in the material.
i do also work with presetted texturepaths i(under preferences), means that cinema finds any texture located in a certain folder.
does the plugin support this functionality? would be great.

its angry that octane looses the textures! don't know how to cope with it!

thank you for help!

the rest of the plugin is really great!
what is the plugin version? Windows or Mac?
Normally it must ask to you as in picture. Also first picture is search paths. If you fill these, plugin will search in these locations if they not found.

Re: Beta 0.72 (SDK 1.20)

Posted: Wed Jul 24, 2013 10:38 pm
by ChrisVis
Hi aoktar,

I prepared a simple scene to show the problem with the material problem when two objects move through each other.
I am not sure, whats the problem here and if it is related to octane.
The scene has a cube with glass material, a diffuse white plane inside the glass and a cube coming out of the glass. The problem happens on frame 680 (dark color or inverted?)... and it has to do with the plane inside the glass. If I disable it, the problem disappears. Animation runs from frame 675-725... and the material of the moving cube is animated (opacity 0-100%, don`t know, if this matters).

Here are some screenshots, and the scene file.

Frame680
Frame680
Frame681
Frame681
Frame710
Frame710
Frame725
Frame725
MaterialCubeSampleScene.zip
(352.35 KiB) Downloaded 237 times

Re: Beta 0.72 (SDK 1.20)

Posted: Thu Jul 25, 2013 5:29 am
by huebner
thanks for reply

i think i know what the problem is.
could it be that tere is a limitation of materials?

i was creating a material-masterfile with many many materials.
i do have the problem only with this file so far.

Re: Beta 0.72 (SDK 1.20)

Posted: Thu Jul 25, 2013 8:50 am
by dinf
aoktar wrote:what is the plugin version? Windows or Mac?
Normally it must ask to you as in picture. Also first picture is search paths. If you fill these, plugin will search in these locations if they not found.
Same issue with textures here, but I think I got the point now (Win 7, Beta 0.7.2 SDK 1.2).
Because Cinema searches subfolders too, the images are probably shown. But they aren't calculated by Octane as long as the path isn't exact. Obviously, Octane does not scan all subfolders like Cinema. Or, it does, but only one time, so it does not ask. Later on then textures are 'gone', materials become white (here).
If typed in the exact path so Octane does not have to search any subfolders, anything works fine.

And thank you for the great Renderer!

Re: Beta 0.72 (SDK 1.20)

Posted: Thu Jul 25, 2013 10:59 am
by aoktar
plugin looks the file is available at absolute path. if it's not a full path or not available, looks project path and tex folder. if still not found, search in octane texture paths. but not in c4d preferences paths.
I should know it can be related texture counts. or scene is saved or new file? can some peope capture a video to show problem?