A and B and C walk into a scene.

alan bard newcomer

Okay, a landscape, a vehicle, and some characters.
Turn off/on as in clicking the eyeCon in the scene pane thus making item visible in viewport or not. 
---
Too much to render as one unit on my cards (and way to long if they would)
---
So render the landscape, turn off landscape, turn on vehicle, and it won't render (even after scene closed and reopened) 
But just the vehicle will render in a scene without the landscape. 
Which means it has to be loading the items that aren't visible into the render engine, right? 
And why does it do that? 
And if turning visible on and off doesn't prevent them being loaded how does the system that blocks visible things from rendering function? 
In the image attached I could render the land or the land and the vehicle with people turned off but when I tried turning off the land and having just the vehicle and people it wouldn't 
and yet the vehicle and occupants would render in another scene 
so the image below is a composite with vehicle and occupants pasted in over the land and vehicle. 

Richard Haseltine

What does the log say?

barbult

You said you reloaded the scene, but I think you might benefit from closing Daz Studio and restarting it first, to free all the GPU memory.

alan bard newcomer

Richard Haseltine said:

What does the log say?

the usual not enough memory but this happens with a new daz with nothing but the one item visible although others there and turned off and then doesn't happen with a new daz and only one item in scene which means it has to be loading maps from stuff not visible in scene in order to fail in the first one.  

Richard Haseltine

alan bard newcomer said:

Richard Haseltine said:

What does the log say?

the usual not enough memory but this happens with a new daz with nothing but the one item visible although others there and turned off and then doesn't happen with a new daz and only one item in scene which means it has to be loading maps from stuff not visible in scene in order to fail in the first one.  

No, it just means that restarting givewsw you a clean slate - which may make all the difference if something is only marginal for fitting into the GPU.

alan bard newcomer

Richard Haseltine said:

alan bard newcomer said:

Richard Haseltine said:

What does the log say?

the usual not enough memory but this happens with a new daz with nothing but the one item visible although others there and turned off and then doesn't happen with a new daz and only one item in scene which means it has to be loading maps from stuff not visible in scene in order to fail in the first one.  

No, it just means that restarting givewsw you a clean slate - which may make all the difference if something is only marginal for fitting into the GPU.

I turned off everything visible but item A before closing the scene and the program and then restarted the program with nothing but item A visible and it still failed 
but if I saved just the one item as a subset and then put the subset in a new scene to render it works. 
So if opening a scene with A. B, and C loaded with only A visible in the save in the new open and it fails vs opening a scene with only A loaded then it has to be loading more than the visible A from the multipart scene into the render engine to blow out the render because of a lack of memory. 

Richard Haseltine

Turned off by turning the Visible property off, I assume, not making them transparent.

The scene still has to be loaded in full into DS, so that is going to consume some system memory - perhaps it is failing during the prepartion stage, before ti even tries to transfer to Iray for rendering. Again, what does the log say?