OTOY Forums

Ok, thanks Notiusweb for trying to test OOC, but feel like that you don't need this feature ! and even more with your Titan X !
And yes I forget to tell you about the slowdown of the viewport of DAZ. I have this issue also but have resolve it, forget how but I will check the setting tonight after work and share the tweak.
My scene has up to 7GB (a castle front wall, a dragon, a tiger armored, V4, V6, V7 and props).
I will recheck it on OR standalone to compare the memory (but remember that the scene is over 6GB) as all devices crash if OOC is not enable.
The bad news is that the use of OOC is not reliable on a low VRAM card on USB (1X) riser , as it slow down (depending on scene size) and almost freeze PC ! (need to be confirmed).
On amfeltec it only slow down but could render to final.

Hi itou31,

Please do let me know what is tweaked to reduce the lag in DAZ. I know hiding whole figures, and especially hair, helps, but if there is a way to work it better that would be awesome. One thing, when you convert to a textured mesh, you can alter the settings of the export to OBJ, so, I can try to help if you get weird results, but it should cross over in most cases without any image difference.

Also, I agree about the PC timeout thing, I found the same thing at those 5-6GB levels. You can totally freeze the app itself, or the PC on whole. I think a 6GB VRAM is just enough to squeak by most scenarios. But let me tell you, using just the 12 GB Titan X all by itself does not help too much. It's like DAZ causes a CPU bottleneck or something at the 5-6GB level, irrespective if VRAM. Maybe I just need a faster CPU. That's why I like the standalone in these cases. You can get your work out if the DAZ 'traffic jam' . If the scene is still hard to manage in the standalone, using the sub-sampling button (1x, 2x, or 4x) on the standalone helps a lot with navigating your scene. It just briefly reduces res to speed up any change in perspective. I wish DAZ had this feature itself.

I could imagine you:
(1) working in your scene in DAZ at 6GB, without using OcDS
(2) export the scene as an OBJ mesh
(3) importing the mesh ( right click on the grey below viewport, Geometry > Mesh)
(4) modifying textures to your liking with just the 6GB cards, and then once you don't need to touch anything,
(5) enabling all CUDA devices just for the straight render, taking advantage of all the raw CUDA

Please note that this is a viable option for single scene rendering. But for animations and rendering with frames, you are much better off working something out in OcDS.

Let us know how it goes!

Hi,

This is my scene memory and my settings So with big scene I will use only the Titan with OOC, even if titan black perform at 50%.
Only thing is resize textures with texture tab. But the settings are not saved.

Itou31, is that the scene giving you the problem? Try exporting the mesh out on that to the standalone and let us know how it affects your workflow and speed. I'm interested to see if it is a better alternative for your larger scenes than using OOC.

Yeah, basically instead of Out if Core, use Out if DAZ

Sorry, Out of Core, and Out of Daz.

Hey itou31, I found this

https://helpdaz.zendesk.com/entries/675 ... -Studio-4-

Last line is interesting:

Make sure your motherboard offers at least 8 lanes of PCI per GPU installed (Ideally 16 lanes per GPU). If you have 16 lanes per GPU you get the full performance, having only 8 lanes per GPU gets you around 80% of the GPU performance, this influences the decision to buy one large card over multiple smaller cards.

Hi Notiusweb,

Yes this scene crash my 6GB card until using OOC. I exported it to OR with orbx.
Same thing on OR standalone : need to enable OOC else render fail. But I notice that OOC need less RAM (978MB vs 1491MB).

Hello all,
Just an update on my current setup, I didn't post it here, so here it is:


I disabled LSI storage controller in Southbridge (a secondary SATA interface), this looks to have freed up the PCIE lanes I needed, such that I have been able to successfully boot into Win 7 64 Bit with 13 GPU cores on the ASRock X79 Extreme 11.
Main Display Titan X direct on Mobo, 6 Titan Z on risers (3 the USB 3.0 PCIE risers/3 on the Amfeltec 4-way GPU Cluster). Running storage only off the motherboard's exclusive SATA ports.

Previously I could only boot with 10 GPU cores active. Once I got 11th GPU working, I added another Titan Z as I have been having success with these, giving me the 12th and 13th GPU cores (I considered 2 more Titan Xs, but felt I was capped at 6GB anyway...).
I attempted to post scores on Octane Bench however for some reason they are not uploading (I started a separate post to see if anyone could share thoughts on that.) It does let you select the full 13 GPU on Octane Bench, but it seems the scores match as if it were only 12. As such I am inclined to believe that it is only 12 that are being run in the benchmark even when you select 13.
I also put in a request to see if MSI Afterburner could allow up to and including 13 GPUs via its UI.

I have the Creative Soundblaster X-Fi soundcard still running for music production on my slot Lane 7, and both USB 2.0 and 3.0 ports are active. I have been using my old 660 Ti as the testing card for all this, contemplating that further experimenting may get 14 GPU. To summarize, I have a 1500 W for the Mobo, then 2 separate 1600 W EVGA external power supplies. One is extended to a separate electrical circuit via a 14 gauge extension chord.

Wow ! So much power !!!
You confirm the the limit of 12 GPU from octane render (same for network rendering). Hope that V3 break this limit !

itou31 wrote:Wow ! So much power !!!
You confirm the the limit of 12 GPU from octane render (same for network rendering). Hope that V3 break this limit !

Cousin itou31,
And through your posts you confirm the importance of thinking ahead and planning. We all can learn even when we seem to fail and if, like you, we help light the way for others on the trail, then we show our compassion.