OctaneRender® 1.024 beta 2.48c TEST (lin/mac/win) [OBSOLETE]

[Jaberwocky]

Ok i've ran some more tests.

GPU Memory starts off at around 720-730mb with just Octane working.

(I am running twin screens so i expect to have around this amount available)

As i open up more programs on top of Octane.the GPU memory goes down to around 550Mb available.

If i then close most of them down the available memory goes back up to around 730-750MB available and as and when i rotate the scene around it slightly fluctuates around that figure.

Hope that explanation helps.

[abstrax]

Ok i've ran some more tests.

GPU Memory starts off at around 720-730mb with just Octane working.

(I am running twin screens so i expect to have around this amount available)

As i open up more programs on top of Octane.the GPU memory goes down to around 550Mb available.

If i then close most of them down the available memory goes back up to around 730-750MB available and as and when i rotate the scene around it slightly fluctuates around that figure.

Hope that explanation helps.

Are you using Aero? I wonder if Windows Aero sucks up graphics memory...

Thanks for the report anyway. It's quite interesting and was the reason why we changed the memory display.

Cheers,
Marcus

[Jaberwocky]

Yep using Aero on win 7 64 bit

with

1 screen - 24" 1920 x 1200
1 screen - 17" 1280 x 1024

[abstrax]

Yep using Aero on win 7 64 bit

with

1 screen - 24" 1920 x 1200
1 screen - 17" 1280 x 1024

Maybe (if you want) try to disable Aero and open the same applications again and see if the graphics memory still goes down. By the way, what were the apps you opened?

Cheers,
Marcus

[Elvissuperstar007]

Direct light is very slow, this has not been slow

What was the speed you got in beta 2.48b? What happens if you reduce the glossy depth to 8 and/or the specular depth to 8?

Cheers,
Marcus

47, it rendered the fast, and now everything slows down and my computer is very slow

[Refracty]

I have a problem with multiple render target nodes (but no crash ).
When I create a 2nd render target and click it then the I can't navigate and render any more. The image is frozen but the rest of Octane is working.

Refracty

[OctaneFX]

Refracty wrote :
"I have a problem with multiple render target nodes (but no crash ).
When I create a 2nd render target and click it then the I can't navigate and render any more. The image is frozen but the rest of Octane is working."

I have reported a very closed issue on my post on the first page of this thread, with the solution.
see the attached image here :
http://www.refractivesoftware.com/forum ... &mode=view

I have a different solution to your issue, explained bellow (seems to be a bug of the RenderTarget node) :

[Refracty]

Thank you for the workaround. Yes it seems we are adressing the same issue.

Refracty wrote :
"I have a problem with multiple render target nodes (but no crash ).
When I create a 2nd render target and click it then the I can't navigate and render any more. The image is frozen but the rest of Octane is working."

I have reported a very closed issue on my post on the first page of this thread, with the solution.
see the attached image here :
http://www.refractivesoftware.com/forum ... &mode=view

I have a different solution to your issue, explained bellow (seems to be a bug of the RenderTarget node) :

[acc24ex]

What does min_display_samples do?

[gzavye]

I have a problem with multiple render target nodes (but no crash ).
When I create a 2nd render target and click it then the I can't navigate and render any more. The image is frozen but the rest of Octane is working

Refracty, I think you did a mistake with your target node...
You plugged the kernel in the mesh pin.
Be careful when you create a new target, you have to plug an OBJ in the last pin.
Finally, You can't connect the mesh from your scene in preview tab.
I think you have to create all new targets in scene tab to achieve your network.