OctaneRender™ Standalone 1.11

[ROUBAL]

Could you try GeForce driver 310.90 or 314.07. NVIDIA solved a few problems on multi-GPU setups, maybe that helps.

Thanks Marcus,

I have updated my driver to 314.07. So far I have opened only one time my current big scene (2.2GB currently), but I have been able to close Octane 1.11 properly. I can't judge on only one time, but it is encouraging, as all recent attempts with 301.42 gave me a freeze.

I tell you if I encounter problems again.

[itou31]

Hi itou31,

I have OC'ed my cards to the same core @ 840/1680 and mem @ 2100,

But i'm not getting the results you are.
Are you sure you have recently download the benchmark scene and haven't played with any max depth or anything like that?
I'm not getting anywhere near 40 for DL unless i drop the specular depth...
Also, even with overclocking, my PT speeds increase from 1.10 to 1.11.

Thanks
Chris.

Thanks for investigating.
I will give a try tonight and verify all that setting.
It's true that my numbers are a bit high ! hum... some wrong setting !?
And will update to 314.07

[ROUBAL]

Well, bad news : Still bad memory purge and Octane freeze when closing, even with last driver.

[abstrax]

Well, bad news : Still bad memory purge and Octane freeze when closing, even with last driver.

Are you sure that this is related to 1.11 and doesn't happen in 1.10 for example? I can't think of any change that might cause this issue. Could you maybe try to explain exactly what is happening? How does Octane behave if you switch to a new (empty) project via File -> New... ?

[bepeg4d]

Ok, I just updated the Linux and Mac builds. On these platforms the dirt texture node should be available now.

it works now, big thanks

ciao beppe

[cfrank78]

Finaly i figured out how to use the fog system and how to combine it with other lights! Was a lot of fun to experiment with the new fog System! But you have to meet really the perfect parameters for scattering and gamma and some other things to make it look good. I hope there will be a simpler and more efficient solution someday!

Chris!

[ROUBAL]

@Abstrax :

Are you sure that this is related to 1.11 and doesn't happen in 1.10 for example? I can't think of any change that might cause this issue. Could you maybe try to explain exactly what is happening? How does Octane behave if you switch to a new (empty) project via File -> New... ?

EDIT : I just understand that I have not noticed the problem with 1.10, because the short period I used it I worked on a small scene of 250MB only.

So, I am almost sure that you are right : the problem probably appeared with 1.10.

Switching to an empty new project gives the same problem. I first thought that it was safer to close completely octane before opening a new project to help memory purge, but I get often a freeze as well : the memory charge stops decreasing around 60-50% in Win7 ressource manager. The mouse cursor is busy and the screen turns white.

This occurs on big scenes (my current project is around 2.2GB in 1920x1080). Small scenes of some hundred MB don't show the problem.

My rendering cards are GTX 580 3GB, but the display card is a GTX 260 (PreFermi ?) Does it has an importance in Octane Behavior ?

Before you ask : I can't provide the scene.

[abstrax]

@Abstrax :

Are you sure that this is related to 1.11 and doesn't happen in 1.10 for example? I can't think of any change that might cause this issue. Could you maybe try to explain exactly what is happening? How does Octane behave if you switch to a new (empty) project via File -> New... ?

EDIT : I just understand that I have not noticed the problem with 1.10, because the short period I used it I worked on a small scene of 250MB only.

So, I am almost sure that you are right : the problem probably appeared with 1.10.

Switching to an empty new project gives the same problem. I first thought that it was safer to close completely octane before opening a new project to help memory purge, but I get often a freeze as well : the memory charge stops decreasing around 60-50% in Win7 ressource manager. The mouse cursor is busy and the screen turns white.

This occurs on big scenes (my current project is around 2.2GB in 1920x1080). Small scenes of some hundred MB don't show the problem.

My rendering cards are GTX 580 3GB, but the display card is a GTX 260 (PreFermi ?) Does it has an importance in Octane Behavior ?

Before you ask : I can't provide the scene.

In the past (especially on our 8 GPU render system) we had issues with releasing CUDA resources - mainly textures. It's not so much the amount of data but more the number of textures used. With driver 310.90 this problem got resolved. Since you are using the CPU via a PCI extension I wonder if this is related to this. Could you test this problem with 1.00 (http://render.otoy.com/account/download ... 6&ver=1.00)?

I basically would like to know if this is a problem that was introduced recently or if it has been there for a long time. If it was introduced recently (between 1.00 and 1.11), the version would help a lot. Obviously we can't reproduce this issue here otherwise I would ask you to do these tests.

Cheers,
Marcus

[itou31]

Hi Chris,
Sorry, I have not launched the ocs file, but the obj, so I think that settings are default.
Here are my new results

Windows 8 x64
drivers 310.70
i7 3930K
64GB RAM
2x580GTX 1.5GB (OC) (840 core and 2100 at mem)

1.00
PT no Alpha Shadows: 7.28
Direct Lighting: 26.88
PMC no Alpha Shadows: 6.02

1.10
PT no Alpha Shadows: 7.37
Direct Lighting: 27.17
PMC no Alpha Shadows: 6.02

1.11
PT no Alpha Shadows: 7.91
Direct Lighting: 33.16
PMC no Alpha Shadows: 7.16


That seems 1.11 is very fast (including loading parts)
Thanks again and sorry for my mistake.

[steveps3]

Can someone give me a quick heads up as to how the fog system works? I am probably just missing it but I can't see how you activate it.

Cheers