OctaneRender™ Standalone 2.15

[gardeler]

I found what I think is a major bug;
Look like the titan Z is mirroring it's mem usage. The 2nd gfx card's usage shows up as "allocated memory used by other apps". This halves the the 6GB memory to only 3!! It seems to be titan Z specific. Works fine on normal titans.

[grimm]

Do you have another 3GB card and have you included it in the rendering pool? Also do you use the Titan Z to run your displays?

[aLeXXtoR]

Titan Z has 2 Videochips and it's memory splits by 2 for each videochip (each videochip gets half of the total memory — just like if you have 2 videocards), so 3 GB is normal for 6 GB video cards.

P. S.: I'm not very good in hardware theory, so maybe not the best explanation — I just know the fact that it's normal for Titan Z.

[Seekerfinder]

Titan Z has 2 Videochips and it's memory splits by 2 for each videochip (each videochip gets half of the total memory — just like if you have 2 videocards), so 3 GB is normal for 6 GB video cards.

Titan Z has 12GB of mem - 6GB for each GPU. Octane should indeed see 6GB of available memory with a Z. There are now a number of Titan Z Octane users that have not reported this issue. Perhaps you have a smaller card activated for Octane as Grimm suggested?
Best,
Seeker

[gardeler]

I only have the titan Z, and before loading something into octane, It correctly say: 2 gpu's / 6144 MB. But after octane loads a scene that uses 2 GB ram, it claims that now only 2 GB is left of the stated 6 GB. (2 GB is lost in space...)

It looks to me that what ever octane loads into GPU 2 is seen as "other software mem usage", and therefore eats doubble amounts of RAM...

[gardeler]

Ok, if I disable gpu2 I get my RAM back. But if I enable it again, it runs out of ram. So far it doesn't fail like it does normally if you try to load too much data. But render speed just dies completly to like a 10th and the whole system struggles...

any other titanZ user that can reproduce?

[gardeler]

Ok... this is wierd. I have access to another dual titan Z system, and on that system it behaves correctly. Same scene, same nvidia driver, same version of octane...

(octane 2.14 on win 7 by the way.)

so the problem is somehow connected to my machine only.

[grimm]

Unfortunately it looks like there is a hardware issue with your card.

[gardeler]

Noooooooooo!!!

[grimm]

Either that or you have a very high resolution monitor plugged into it that is sucking up the memory? This is one reason why it's better to have another card in the system that just handles the monitors. My two HD monitors take almost 600 MBytes of my 460's memory.