View attachment 1895150
I have to show you a real torture.
Only this much progress in 1 hour
That's insane. I would have stopped it as soon as it took longer than 1 min for an iteration. On my old card, a 1050TI, it only had 4G or VRAM so I had to be careful what I put in the scene. Put too much detail, and the renderer will automatically drop to a CPU render as it needs enough VRAM (RAM on your video card) to do it or it will use the CPU which is way slower.
Ways to combat this with an older card, is to delete any object in your scene that isn't visible to the camera, if you can't see it, it is only wasting precious VRAM, even body parts, you can hide various body parts that aren't visible like perhaps the bottom of a leg is just off the camera view, click it and click the eye in the object list window which will hide it and body parts that are hidden (or deleted) won't use VRAM. You can also use software that will reduce your texture size by a quarter which I found is fine and usually you don't notice the difference except a 2048x2048 texture takes up 1/4 the VRAM as a 4096x4096 texture.
Use
You must be registered to see the links
to reduce your texture size (big help!!!) of all objects in your scene.
Use
You must be registered to see the links
to automatically remove objects in your scene outside of your camera view. It's not perfect, but it does an adequate job.
Here's a scene I rendered on my old card using all of these methods...
Now here's this SAME scene seen from a perspective view and you can see how I removed all body parts and scene objects not visible to conserve VRAM to render it faster. I also used the software I listed (scripts you use in DAZ) to reduce the texture size. I actually rendered this view by accident after hitting the render button before I switched to my camera view, but decided to keep it...
