OctaneRender™ Standalone v1.02 (obsolete)
Forum rules
NOTE: The software in this forum is not %100 reliable, they are development builds and are meant for testing by experienced octane users. If you are a new octane user, we recommend to use the current stable release from the 'Commercial Product News & Releases' forum.
NOTE: The software in this forum is not %100 reliable, they are development builds and are meant for testing by experienced octane users. If you are a new octane user, we recommend to use the current stable release from the 'Commercial Product News & Releases' forum.
- SamCameron
- Posts: 162
- Joined: Sun Jan 02, 2011 12:58 pm
As I said, this is a bug, I'm pretty sure. If I set the glossy index below 1 doesn't provide any reflection until I switch from direct to pathtracing and then back to direct. Then it works.
yeah I figured this out myself, the problem is that a lot of the metal materials in the online DB don't work properly now. I'm not using 1.02 right now since it's so slow responding to commands so it's not a big deal right now.
Hi guys. I thought this too, but its not a bug - its a featureAs I said, this is a bug, I'm pretty sure. If I set the glossy index below 1 doesn't provide any reflection until I switch from direct to pathtracing and then back to direct. Then it works.

1.02 is responding even faster to me than 1.0, as long is i dont use importance sampling, but thats completely normal. for adjustments i turn it off and for final rendering on - done!
1.02 is perfect to me. much better than 1.0
Kind regards Chris!
- larsmidnatt
- Posts: 499
- Joined: Tue Sep 25, 2012 12:28 pm
Thanks for the tip, I hope that works for me too. Can't remember if I had it on or not in my test, but I know I did try using it at least once so it is possible.cfrank78 wrote: 1.02 is responding even faster to me than 1.0, as long is i dont use importance sampling, but thats completely normal. for adjustments i turn it off and for final rendering on - done!
Win10 x64
i9 10900k 64GB
2080S 8GB
DS 4.15 OcDS Prime ^_^
i9 10900k 64GB
2080S 8GB
DS 4.15 OcDS Prime ^_^
- SamCameron
- Posts: 162
- Joined: Sun Jan 02, 2011 12:58 pm
I repeat, it's a bug, first there's no fresnel option in my UI, all it says is index:

this is how it looks when I drop the value to 0:

then I switch from direct lighting to path tracing:

so I get this result:

and finally I got back from path tracing to diret lighting and I get the right result:

As you can see it doesn't have any sense at all so must be a bug.
this is how it looks when I drop the value to 0:
then I switch from direct lighting to path tracing:
so I get this result:
and finally I got back from path tracing to diret lighting and I get the right result:
As you can see it doesn't have any sense at all so must be a bug.
Hi,
When you switch to and from kernels certain settings that are in one and not the other will be changed/reset. Take a look at your glossy depth slider in DL kernel before and after you change kernels.
Before, i would guess it is set to 1 - causing the lack of reflection on the glossy material. After switching to PT and back to DL, this will most likely be re-set to the default 2, bringing the reflection back.
For the index parameter, this controls the Fresnel, sorry this is perhaps not an obvious name but never the less, this is what it is doing. It might pay for us to make this more clear.
When you switch to and from kernels certain settings that are in one and not the other will be changed/reset. Take a look at your glossy depth slider in DL kernel before and after you change kernels.
Before, i would guess it is set to 1 - causing the lack of reflection on the glossy material. After switching to PT and back to DL, this will most likely be re-set to the default 2, bringing the reflection back.
For the index parameter, this controls the Fresnel, sorry this is perhaps not an obvious name but never the less, this is what it is doing. It might pay for us to make this more clear.
- SamCameron
- Posts: 162
- Joined: Sun Jan 02, 2011 12:58 pm
FooZe, that's right, it's quite unclear at the moment, it would be nice if the default settings for the direct lighting would be set as 2 so we can see reflections as with the previous versions of Octane, on top of that as you can see in the first screenshot there's no 'fresnel' label in my glossy settings but instead it says: 'index'. This option should provide reflections as default as well. These changes makes the workflow worst so I hope we can have some tweaks about this for the next version. Thanks.
- larsmidnatt
- Posts: 499
- Joined: Tue Sep 25, 2012 12:28 pm
Ok this was my issue. I didn't realize importance sampling was enabled by default. I loaded a 1.0 scene into 1.02 and starting working and eventually the slowdown kicked in. I turned off importance sampling and everything went very quickly as in 1.0. Thanks for the pointer!cfrank78 wrote: 1.02 is responding even faster to me than 1.0, as long is i dont use importance sampling, but thats completely normal. for adjustments i turn it off and for final rendering on - done!
Win10 x64
i9 10900k 64GB
2080S 8GB
DS 4.15 OcDS Prime ^_^
i9 10900k 64GB
2080S 8GB
DS 4.15 OcDS Prime ^_^
As Chris allready Index=Fresnel!I repeat, it's a bug, first there's no fresnel option in my UI, all it says is index
What does fresnel do? Some things. One example. If you have a glossy Material and you have the reflection set to 1 - there is absolutely no colour in the Material. With the Fresnel Slider you can set a clolour in diffuse and so the Material(Metal) will be, even if it is at its full refelctivity, have a colour. Very, very useful

I took a material from live database. Gold 750 pink. It is black, cause the fresnel=index slider is set to 1.3 . If you reduce it to 0 it is shiny again - !
There is no difference for me wether i use PT, DL or PMC. I use 1.02. So here it works fine on my machine. The only thing i suggest again is that Octane Team should rename the slider to Fresnel and set it by default to 0 or 2.
Kind regards Chris!
- alexx_orel
- Posts: 2
- Joined: Tue Jan 31, 2012 7:21 pm
Hi, Roeland! Its good to see version 1.02. But it seems to me that you didnt fix the bug with importing obj scene in octane standalone. Earlier it was easy to import my scene simply via obj. But today its seems to be impossyble to find my scene in octane viewport after import. Sorry for bad English, but i cant use Octane any more without your help. Thank you for your attention to users problems.