Something is wrong with Daz Studio 4.20 (Not Rendering Iray)
desireroad
Posts: 76
Hey, I have been trying to figure out for the past 3 hours why my scene wont preview in the viewport or render.. to put things in perspective , I have:
RTX 3080TI with 12gb DDR6 , I have a ryzen 7, 5GHZ clock CPU, 32 gb of DDR5 and Daz running on a SSD.
I'm starting to think Daz isn't actually utilizing my Hardware at all. The scene im trying to render for example has been given Scene Optomizer , Has had it's sub division all lowered to 1 and has most of the area wiped of objects. Daz is refusing still to load it.
This is the Log that comes up and you might be thinking, Yea you are out of memory but, If you look at the actual available memory , It says I have 0.000B ? When I check the task manager.. this is the results when I try and render.
it's actually not even trying to use anything? I mean, Check out this scene... Does it seem extensive ?
Any Help would be really, REALLY appreciated.
Note: The one thing I'm thinking could be causing it is a program I bought called The Multi-Layer Landscape system but then again, I turned everything down on it and in the Examples the dude is running alot more of the layers on the screen with animals ect, no issues.
Daz 3D is part of 
Connect
DAZ Productions, Inc.
7533 S Center View Ct #4664
West Jordan, UT 84084
Licensing Agreement | Terms of Service | Privacy Policy | EULA
© 2024 Daz Productions Inc. All Rights Reserved.
Comments
In the first line of the log it says your GPU is out of memory.
12 GB might seem like much, but scenes can become very large.
You haven't included how it comes to that.
If you have a large scene with many instances, check that instance optimization in render settings is set to memory.
Or if you have a large scene without instances, add 2 section planes to limit what is sent to the GPU.
The main Issue I have with the fact it says it's out of Memory is firstly the required memory is 1gb to render the scene as stated and the fact the textures have all been set to 520 x 520 and the poly count is 640k ? Like we are talking PS2 graphics at this point. What in the hell going on.
Can you tell me more about the sections planes, I have never heard of that process.
Got the newest one today. Made no difference :( , Thats the thing, I can load in like 4-6 characters and render them no issues with a simple scene but I can't render this particular scene, I have tried adding all the files to a new scene, have tried exporting them as an OBJ and importing, Have tried all sorts of things, I even imported the scene into blender and it ran with not an ounce of Issues.
I can suggest that you attach a full log of what happens when you try to render that scene.
When the scene doesn't fit the GPU VRAM, it may load the geometry in there which is usually just a few hundred megabytes, but doesn't load the textures anymore as they don't fit.
Looking at a scene does not tell how much VRAM it may require, it's about the size (dimensions) and color depth of the textures and maps used on it.
The memory requirement of textures has nothing to do with the filesize of the used images, but is calculated with "Width (px) x Height (px) x color depth (bits) / 8 (bits) / 1024^2 = MegaBytes" irrespective of the program used to load them.
The default Iray compression settings reduce the memory usage to about half, ie. if the images take 4GB's of RAM they would take 2GB's of VRAM
In your case, I would restart the computer first because something may have put your GPU in a state that it's no longer working right, then open only DS and load one simple item and try to render it, if it does render, then load your scene and try again.
You haven't told us, which version of DS are you using and and which GPU drivers.
In general the Task Manager is not a good tool to check the situation, by default it doesn't show Cuda activity and it reports false figures about the amount of VRAM, in the attached picture I have crossed out the figures that have nothing to do with real information.
Didn't find any trees or bushes mentioned in the Multi-Layer Landscape system, the leaves can be a real memory hog, where did those come from?
Yup , I actually think you were right, Switched the tree's for ones with less leafs and it sorted most of my Issues.
I am guessing you meant, render two scenes and add planes to mimic the background. I did that and it helped alot too. Many thanks.
An Iray section plane can remove geometry (and related textures) that is outside view of the camera, so you reduce the load on the GPU.
Here is a semo
Are you sure? It's been a minute since I tested this, but my understanding is that using section panes doesn't save VRAM. Makes sense if you think about it - IRay has to figure out what to cut, and in order to do so the geometry must be loaded. I suppose this could happen before textures are loaded, but I don't remember this being the case.
- Greg
ETA: Actually, upon thinking about this more, I think all the textures are definitely loaded whether cut or not because the panes can be moved. If they are moved so that everything is displayed, the re-draw is still fast (meaning everything must have been loaded already).
I am fairly certain, yes.
I have used them if I had a large environment to remove not seen items, and that have increased render speed,
Furthermore, I think there is a product in the store, where it essentially uses these to get faster render.
And you don't need the GPU to remove unnessecary geometry, that can the CPU do without problems.
A render speed increase doesn't mean VRAM savings. A speed-up could easily be explained if more light was being let in. I still don't think section planes can be used to save VRAM.
- Greg
If you're referring to this product, I don't think it uses section planes:
https://www.daz3d.com/camera-view-optimizer
- Greg
No, it was this product https://www.daz3d.com/camera-cutaway
From the product description:
"This product is for Iray only. Note that Camera Cutaways reduce rendering time but do not change the amount of GPU memory required."
- Greg
Actually version 4.20 is having problem in rendering.
When I open daz3d and render the first image it will probably be fine, but on the second picture things start to get worse, and so on it gets slower and slower on the next images, it won't even render. floating 1 picture except the first time when starting the program, I don't know why. Does it save the changed steps anywhere and make the program heavier, if so I just turn it off because it doesn't need to do anything that heavy.
But for that 1 scene project, I tried removing a lot of things but it's still the same, even I removed more than 60% of the objects in the project it still renders slowly in the 2nd picture. onwards. Why?
While previous versions of that project I rendered normally, the first and second render times were the same. So version 4.20 has changed how project loading and rendering management is so bad.
Are you closing the render windows or leaving them open? If you leave them open then the scene data will still be stored, so that they can resume, consuming memory on the render device.
normally when the render window stops rendering and then saves the file it will close by itself. then when rendering another scene it shows another scene display window. and every time render, there is only 1 window showing the rendering process.
How much RAM do you have and what GPU are you using?