OctaneRender® pre-Beta 2.4 (win x64) [OBSOLETE]

[oguzbir]

Bug report:
In v2.4 the specular material's roughness parameter; floattexture default value has 4 digit as -> 0.0000
In 2.3_v5 the same parameter used to have 7 digit value 0.0000000
Explanation:
If you try create a specular material in 2.4 from start, the roughness floattexture jumps to 0.0001 as you edit the slider the material instantly get too much roughness. We cannot create a less roughned glass in 2.4

I created a test file in 2.3v5 and gave a less value in roughness like 0.0000078 and open the file in 2.4
The roughness value displays like 0.0000 but actually preserves the previous value in file.
Which is <value>7.8e-006</value>.

[abstrax]

This version is a very good update. Thank you guys.

Just to help you solve problems for further versions. I have a bug report.

I have just came across with a problem while testing it with an old scene. And sadly I was able to re-create it 3 times.
Pathtracing on , Daylight on, alpha mode on
Rotating viewport gave the problematic screen below. The alpha problem occured after enabling the daylight mode.
Tried to recreate it with a single material node with pathtrace and daylight on. It didn't happen. It seemed OK.
Now, I tried it with another old scene the problem occurs again.
Keep environment option doest not help.

Edit----
My Nvidia version is a beta - v 266.35 . (I think I must stress that out)
------

Thanks for the files. I found the problem and it was easy to fix. Until the fix becomes available, please make sure that the image width is a multiple of 8. In your case, switching from a width of 900 to 904 makes alpha work again.

Cheers,
Marcus

[Jaberwocky]

Thanks for the new version.I can finally use all 336 cores on my single GTX460.I also have to report that i can drop it to my task bar and still use other programs without the display feeling jerky.This may only because i have tried it with a simple test render of the teapot though.So i will keep you all informed.One query.I am using the latest driver 260.99 and i know you have compiled it using Cuda 3.2. However my account preferences screen wrongly displays Cuda 3.02 ? .You may need to look at that.Small point i know.

[Jaberwocky]

Sorry.Forgot to post the screen shot

[oguzbir]

Thanks for the files. I found the problem and it was easy to fix. Until the fix becomes available, please make sure that the image width is a multiple of 8. In your case, switching from a width of 900 to 904 makes alpha work again.
Cheers,
Marcus

Thank you
It really worked.

[abstrax]

Thanks for the new version.I can finally use all 336 cores on my single GTX460.I also have to report that i can drop it to my task bar and still use other programs without the display feeling jerky.This may only because i have tried it with a simple test render of the teapot though.So i will keep you all informed.One query.I am using the latest driver 260.99 and i know you have compiled it using Cuda 3.2. However my account preferences screen wrongly displays Cuda 3.02 ? .You may need to look at that.Small point i know.

Yes, that's a little weird, but the internal version number of CUDA 3.2 toolkit is indeed 3.02. Ask nVidia about that...

Cheers,
Marcus

[abstrax]

Bug report:
In v2.4 the specular material's roughness parameter; floattexture default value has 4 digit as -> 0.0000
In 2.3_v5 the same parameter used to have 7 digit value 0.0000000
Explanation:
If you try create a specular material in 2.4 from start, the roughness floattexture jumps to 0.0001 as you edit the slider the material instantly get too much roughness. We cannot create a less roughned glass in 2.4

I created a test file in 2.3v5 and gave a less value in roughness like 0.0000078 and open the file in 2.4
The roughness value displays like 0.0000 but actually preserves the previous value in file.
Which is <value>7.8e-006</value>.

Thanks for the heads up. I have fixed the problem and it will become available with the next release.

Cheers,
Marcus

[mirobimbo]

Maybe I found a mistake.
Every time i turn on alpha channel, screen is getting wrong.
I tried directlighting, pathtracing, daylight ... It makes always.
336 cuda cores on my 460 work fine .
Sorry my English.

[oguzbir]

Maybe I found a mistake.
Every time i turn on alpha channel, screen is getting wrong.
I tried directlighting, pathtracing, daylight ... It makes always.
336 cuda cores on my 460 work fine .
Sorry my English.

The workaround for the problem is already posted a few posts up..
your image dimensions has to be multiple of 8

[Jaberwocky]

Typing this whilst Octane is buisy rendering up a more complex scene.I can report that 1 core of my dual cores is running at full tilt.The other Core is Idle.May i make a suggestion that tests are done on optimising the code for dual cores.This may decrease the juddering a bit whilst rendering in the background.