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
@jnwggs
yeah that and not clearing from the processes so the program hangs LONG after being shut down. the refusal to open even if the process was ended. there are a few bugs. but the not using the GPU has been the most annoying.
I have been using DAZ long enough to know when a scene will tip the balance and have to fall back to CPU for that kind of heavy scene I'm ok with CPU helping but as a few have been posting the GPU is not being tapped at all and that is a major waste of resources the faster processor for the render is tossed to the side and ignored. you'd think getting them both to work together would have been intuitive.
Ok this one really has me scratching my head. one look at the screenshot should also puzzle you! yes its rendering in 8K not likely relevent in this case. I'll include a scene info screenshot when it finishes rendering. this scene is VERY light 6 planes 2 prop mountains 2 characters and a bike it does have fog<<< that will chew stuff up the scene itself uses the same texture on most surfaces and then another for the ground. characters and bike may account for 8-10 others. (If I was to guess where to look for the effective change between quick GPU test renders and this one. the "Quality" on/off toggle would be it!) increasing the iterations was included but I'm betting against that being the change.you can see the RAM hasn't even past 1/3'rd CPU fallback doesn't occur on my machine before 2/3-3/4+ RAM usage. its how I know if fallback needs to be on if no black screens have occured yet. the GPU is not even topped out <<< draw your own conclusions but its hard to say it ran out of VRAM.
still puzzled about the way this one rendered. turned out fine. but the usage as seen below was pretty small and it looked to be doing a tandem render. something which is being said does not happen!
On the not being able to start a new instance until the old one has finished closing, it is possible but requires the instance have a new name Daz Studio Pro 4.12 - instances
Putting one of those graphs in the performance tab to show CUDA might help, 82% is certainly high CPU usage - but I would expect an Iray render to be close to 100% CPU usage.
Limited threads. wont let DAZ turn my system into mollasses for hours at a time
pretty sure they didn't include with 'home' most useful stuff was gutted from 'pro'
We never said "tandem render" wasn't possible, that depends on your selections. If you have selected both the GPU and CPU for rendering, then it will use both just like it will use multiple GPU:s, but... The memory is not combined between the devices (unless you have NVLINK between two or more GPU:s) and if the memory load exceeds the available amount on the GPU, it throws in the towel and the CPU will handle it if allowed.
Ah, that makes sense then. Sorry, I don't know why it would fail if it isn't running out of memory or an issue with a specific shader.
All the symptoms are telling that it is running out of VRAM, the snippet with 8.1GB:s of VRAM used does not prove that it didn't run out - A real logfile in textfile would help figuring out the problem.
Have found something interesting, but have to do some more testing...
I'm speaking of DAZ3D the program hanging in processes five-ten minutes after being closed. then the program refuses to start even when the programs process has been terminated and no longer hanging. just two days ago while we were discussing this thread it took nearly 30 tries to get DAZ to open. that I'd call a bug.
I've left it overnight and found it still stuck in the processes and had to "end task" the next day to get rid or it before Daz would open again. I left it on just to see if it would eventually shut down...
It would be really helpful if Daz Studio had a little box somewhere that showed how much Vram a particular scene is going to need while you're building your scene. Nothing fancy, just some little box somewhere up top that had a figure such as 2.6 Gigs used so far that increased or decreased as you added or deleted things, or changed lighting etc.... It wouldn't need to be reading your GPU, you'd already know that for instance, your card has 8 gigs, and you could just keep an eye on what you're up to as you add things to your scene. Like a gauge on a car that tells you roughly how much gas you have in the tank. You're not told precisely how many milliliters of fuel you have left, but you get a rough idea of whether or not you're at a quarter tank, or 3 quarters of a tank. It wouldn't even need to be accurate or real, it only needs to be what Daz "thinks" it will need, since after all, it's Daz Studio that decides when to forget the GPU and use the CPU to render instead. Why isn't that being done? It can't be that hard...
It's meant to work that way - the link explains how to set up a command line switch (or use the attached script to do it for you) so that you can launch a new instance of Daz Studio while the other is closing.
The trouble is DS doesn't know - it could estimate geometry size and maps siz (and in fact there is, or was, a store script that will do that) but a lot depends on how Iray puts things together to build materials and so on so the estimate isn't really useful.
So by "overnight", I'm talking about 12 hours later it's still open in the processes and I coudn't open Daz Studio until I terminated. Is it really supposed to stay open indefinately like that? I've never seen a program do this...
Well it probably would be somewhat useful, about as much as a gas guage that told you if you were close to empty vs. pretty full. I know Daz can't be very accurate with this idea, but the problem at the moment is that there is zero to go on until you try to render. Some of the newer models render in seconds instead of many minutes, and there must be a reason for that that Daz could at least guess at. As it stands at the moment, you have to try to render the scene every single time you add or change something, and it would be helpful to have a ball park idea if you've just made a huge change or a little change to the amount of Vram you might need. Even if Daz were guessing within a Gigabyte would be better than no estimate at all...
Why couldn't the PA's figure out the Vram their products will need and have that included as some meta data that Daz Studio could use? They could test their product before they offer it online and include the meta data so that Daz would know how much you've just added when you load the product. I realize that older products would have to be tested and updated, and that not every product would be done, but at least if you only used the products with meta data, you'd have a pretty good idea of how much you'd need ... within a gigabyte at least...
It certainly shouldn't usually hang for that long - is it actually doing anything (using CPU, if you check Task Manager) or is it literally hanging? As I said you can set up short cuts to launch a fresh instance of DS even while a previous one iss till closing, but unless you want to hand-craft tghe command line it should be done in advance.
yeah the program is active usually still using the VRAM at whatever level it dropped to post render (sometimes half or more which is the reason to shut down and clear it) the CPU usage is nominal at best.
The main process ends, but a second "back ground process" opens below that in Task Manager that never closes. You have to manually close it before Daz will restart. Note though, that this does not always happen. Sometimes that back ground process terminates by itself after 10 minutes or so. If I open Daz and then close it right away, the back ground process starts up and closes again after only a few seconds. But if I create a scene and render it, it's anybody's guess when the background process will close...sometimes, like I've said, it never does and you may only notice that when you go to open up Daz later in the day, or even the next day. I actually pinned Task Manager to my task bar just for shutting down Daz when this happens so that I don't have to press "Control, alt, delete" so much. That's how frustrating this is. I'm hoping, like everyone else, that this latest bug will get cleared up someday...That and the randomly switching back and forth between GPU and CPU I mentioned earlier...
I'm not sure what you mean by background process - when you close DS it goes from the icons on the Task Bar and in the Apps list in Task manager, because it no longer has a UI, but it stays open in Background Processes until it has finished clearing up after itself (which can take a long time with a morph-heavy figure with lots of links, though it really should be a matter of hours - I have masses of characters and morph sets installed for Genesis 8 Female and it takes less than ten minutes, admittedly with a fairly high-end Ryzen CPU and plenty of RAM so there should be little or no disc swapping).
You kind of answered your own question. Yes, I'm talking about the Background Processes that stay open in while it's clearing itself up.
Ok, so you're saying it's normal then for Daz to take "a matter of hours" to clear itself up before you can use it again, but not overnight? I don't think that I know of any other program that takes so long to shut itself down before you can reopen it. Don't most programs let you open up a new instance and take care of "clearing up" the instance you've shut down "in the background?" In fact, a lot of programs let you have several instances of the same program running simultaneously - Such as Firefox...
Ok, tested an indoor scene with four G8 figures, their clothes and hair. The scene was lit with 3 spotlights.
System i7-5820K, X99, 64GB RAM, RTX2070Super (8GB VRAM), W7 Ultimate, DS 4.15.0.2 and Nvidia 456.38
Kept increasing the SubD on the characters until the GPU threw in the towel (had to go up to SubD 5 on all of them)
In the final render where GPU was not involved, GPU-Z still showed VRAM usage jumping from 2115MB to 5031MB (out of 8GB) but the GPU load was at 0% and the log told;
Iray [WARNING] - IRAY:RENDER :: 1.4 IRAY rend warn : CUDA device 0 (GeForce RTX 2070 SUPER) ran out of memory and is temporarily unavailable for rendering.
Iray [WARNING] - IRAY:RENDER :: 1.4 IRAY rend warn : All available GPUs failed.
Iray [WARNING] - IRAY:RENDER :: 1.4 IRAY rend warn : No devices activated. Enabling CPU fallback.
So, having VRAM used is no proof of GPU being involved in actual rendering.
I would regard an hour as a surprisingly long time, though if you have different base figures loaded (Geensis 8 Female, Genesis 8 male, Genesis 3...) then each could contribute to the time taken. Still, hours would seem a long delay to me - I would be surprised at anything over an hour really.
I think when Richard posted " though it really should be a matter of hours" he accidently left out the "not".
Ah, yes - sorry.
Oh, well since we're talking hours vs. days in some cases, I didn't make that assumption...
Still, I have a fast computer, and a GTX 1070 and it seems to me that even a complex scene should clear itself out within 10 minutes or less, not still be hung up the next day. I still don't understand why Daz won't open a new instance until the background process finishes. Isn't that the point of it shutting down in the "background?"
That is pretty much what I said when it drops the GPU to run on CPU the GPU becomes an expensive form of extra RAM.
Certainly not going to get into that quote mess above: Cleaning up in the background<<< not happening correctly it should be doing so at the end of any saved/terminated render but keeps building up VRAM usage with consecutive renders. if you do several test renders at low resolutions to identify clipping or pose issues the VRAM usage keeps building up even if the test render was terminated and not saved.
Yeah, that was getting a bit cumbersome...
I press "Shift, Control, Windows Key and B" before each render to clear out the GPU ram. But even doing that, now, doesn't work like it used to, and sometimes Daz uses the CPU instead of the GPU anyway. But like I said somewhere earlier, I can have it switch to CPU and for a couple of renders, and then without doing anything more than clicking the render button, it will suddenly render the same scene with the GPU. If the scene was too big for the GPU, then it should never switch back and forth at random like that...