Thankyou very much for pointing the way
3D Software Help and Assistance. Ask Away.
- Thread starter Lt. Aldo Raine
- Start date
- Oct 23, 2020
- 2,221
- 3,975
I thought I would ask here. I know there is an overwhelming wealth of DAZ knowledge here. I have an issue that has popped up here in the last week or so that is driving me crazy. Which is actually a short walk rather than a drive...
I am using DAZ V4.15.0.2 Pro
Just a couple of weeks ago I noticed that my render time to increase to the point that it is almost unusable. I have the renders set short by most standards so I can get things done quickly or updates would be months apart. I am getting exceptable renders for a VN I think.
Progressive Setting: Min=1
interval=5sec
Min Samples=100
Max samples=800
Max Time=270sec
Quality=On
Quality=2
Post SSIM=OFF (or ON it makes no difference it seems)
I have the currant ver of Nvidia Studio drivers installed.
What used to take only 5 min 20 secs @ 500 to 700 Iterations of the 800 now takes more than 45 minutes to just get to the Min 100 iterations where it finishes. ??
I have watched the GPU on the Nvidia monitor and it is running at 99/100% during the render period like always has. I can tell within 45 sec to a minute if it is working right or not by the sound. When the RTX 3080 kicks in it sounds like a jet. That doesn't happen now. The CPU monitor is as always around 8 to 12% . It isn't reverting back to CPU mode or DAZ would say so ( I think, or it used to. ) and the CPU would run WAO. The machine is an Alianware R11 with 11Gen i9, and the RTX 3080.
I have looked, and looked with Zero luck trying some info on the various DAZ forums. Which by the way is mostly useless.....
Does any one out here have any idea what I could try to get this thing back to how it was, and should be???????
HELP me Obi-Wan Kenobi !
Any help appreciated thanks
I am using DAZ V4.15.0.2 Pro
Just a couple of weeks ago I noticed that my render time to increase to the point that it is almost unusable. I have the renders set short by most standards so I can get things done quickly or updates would be months apart. I am getting exceptable renders for a VN I think.
Progressive Setting: Min=1
interval=5sec
Min Samples=100
Max samples=800
Max Time=270sec
Quality=On
Quality=2
Post SSIM=OFF (or ON it makes no difference it seems)
I have the currant ver of Nvidia Studio drivers installed.
What used to take only 5 min 20 secs @ 500 to 700 Iterations of the 800 now takes more than 45 minutes to just get to the Min 100 iterations where it finishes. ??
I have watched the GPU on the Nvidia monitor and it is running at 99/100% during the render period like always has. I can tell within 45 sec to a minute if it is working right or not by the sound. When the RTX 3080 kicks in it sounds like a jet. That doesn't happen now. The CPU monitor is as always around 8 to 12% . It isn't reverting back to CPU mode or DAZ would say so ( I think, or it used to. ) and the CPU would run WAO. The machine is an Alianware R11 with 11Gen i9, and the RTX 3080.
I have looked, and looked with Zero luck trying some info on the various DAZ forums. Which by the way is mostly useless.....
Does any one out here have any idea what I could try to get this thing back to how it was, and should be???????
HELP me Obi-Wan Kenobi !
Any help appreciated thanks
- Apr 25, 2020
- 1,092
- 8,109
I'am not sure if this will fix it for you, but you should disable Post SSIM, it disables your Render Quality settings as far as i know and replaces it with an intern logic of when Daz thinks your render is done.
Again, i might be wrong, i did some tests when they introduced it on Daz and never touched SSIM again.
Couple questions:
Did you check your rendering resolution? The only thing that can shoot your render time that high from nowhere is resolution (other than hardware problems) as far as i know.
Is this scene you are rendering a new one that you never rendered before? New environment, etc.
Again, i might be wrong, i did some tests when they introduced it on Daz and never touched SSIM again.
Couple questions:
Did you check your rendering resolution? The only thing that can shoot your render time that high from nowhere is resolution (other than hardware problems) as far as i know.
Is this scene you are rendering a new one that you never rendered before? New environment, etc.
Last edited:
- Aug 17, 2019
- 5,471
- 8,762
That poor GPU. . .that being said, it's entirely possible that your renders are being throttled due to heat as there's little to no air coming in through an R11. That isn't a great case, and is likely slowly killing your components much faster than a normal case would. There's absolutely no reason a 3080 should be taking that long to render anything. Even most 4K renders are close to done at nearly a half-hour. That kind of hardware should be moving a lot more quickly than 45 minutes. Something is up there.
First, double check your CPU fallback settings. Render Settings > Advanced > Make sure all CPU options are unchecked. If they are checked, uncheck them. Like so:
I basically have the same-esque system, only with a 10th Gen i7 and external, non-prebuilt hardware (technical term is escaping me). My settings are basically like this (below) at 4K, or even 2K. Gives me the freedom to cancel a render once I feel it's good enough to be presented in a VN.
The thing is, I've had some renders taken twenty minutes and I've had others take an hour or longer. It all really varies with how many characters and lights are in your scenes, along with stuff like fur or reflections bouncing everywhere. Lights themselves can be a killer when rendering new scenes.
- Jul 4, 2017
- 2,622
- 4,807
tripod70
The way to know for sure why a render falls back to CPU is to look at the DAZ Logs.
You can open the logs via the menu: Help -> Troubleshooting -> View Log File
I recommend you turn off Iray viewport preview, as when that is enabled you get both Renders and Preview log entries in the file which makes it confusing.
It will be full of info about loading scenes/figures and previous renders. None of that is relevant for this issue, so delete everything in the log file and save the file. Close the file and then reopen from the menu.
Then start the render.
You will see a part where it is loading all the data. Then there will be a part about memory etc. Finally it will start having regular repeating entries as the render progresses.
In the "memory" section you can see if it uses GPU or falls back to CPU. Normally there is a line about "not enough memory" if that is the problem.
There are several other threads about how to reduce memory usage of your scene if that is the cause of the fallback.
Here's an example of the log for a render that is working in the GPU only, no fallback:
Here is the log when the scene memory requirement exceeds the GPU capacity (with no CPU fallback allowed)
And finally an example where GPU memory is exceeded and CPU fallback is enabled
Possible note of interest, I had to load a complete environment and 6 characters (2 usind HD variant) all with different clothing and Hair to exceed the 12gb memory on my 3060 card.
If I used a product like "scene optimizer" to reduce the texture image size of some of the assets, It would be possible to easily fit more characters in a single render. However, with so many characters the scene load time and render setup time was very long, about ~6 minutes.
The way to know for sure why a render falls back to CPU is to look at the DAZ Logs.
You can open the logs via the menu: Help -> Troubleshooting -> View Log File
I recommend you turn off Iray viewport preview, as when that is enabled you get both Renders and Preview log entries in the file which makes it confusing.
It will be full of info about loading scenes/figures and previous renders. None of that is relevant for this issue, so delete everything in the log file and save the file. Close the file and then reopen from the menu.
Then start the render.
You will see a part where it is loading all the data. Then there will be a part about memory etc. Finally it will start having regular repeating entries as the render progresses.
In the "memory" section you can see if it uses GPU or falls back to CPU. Normally there is a line about "not enough memory" if that is the problem.
There are several other threads about how to reduce memory usage of your scene if that is the cause of the fallback.
Here's an example of the log for a render that is working in the GPU only, no fallback:
You don't have permission to view the spoiler content.
Log in or register now.
Here is the log when the scene memory requirement exceeds the GPU capacity (with no CPU fallback allowed)
You don't have permission to view the spoiler content.
Log in or register now.
And finally an example where GPU memory is exceeded and CPU fallback is enabled
You don't have permission to view the spoiler content.
Log in or register now.
Possible note of interest, I had to load a complete environment and 6 characters (2 usind HD variant) all with different clothing and Hair to exceed the 12gb memory on my 3060 card.
If I used a product like "scene optimizer" to reduce the texture image size of some of the assets, It would be possible to easily fit more characters in a single render. However, with so many characters the scene load time and render setup time was very long, about ~6 minutes.
Last edited:
- Apr 18, 2021
- 371
- 795
Sounds like you may be falling back to CPU rendering and what fan you're hearing is your CPU cooler firing up. Follow Missfortune's advice.
Turn off render quality. Set iterations somewhere between 500-1000. A 3080 should be able to make short work of most optimized scenes. Start using iRay section plane nodes with "Camera Cutaway". It's a game changer.
- Oct 23, 2020
- 2,221
- 3,975
Thanks for all of the replies. I am looking into it again and so far Nada!! I have already looked at the log... It shows right 5.5Gb mem,,, not enough to swamp the GPU. Like mentioned the GPU is running at 98 to 100% and CPU is 8 to 12% during rendering according to log and task manager and Nvidia Performance Monitor ( Alt+R ) which is hand in hand with the Alienware Performance Monitor. I am sure it isn't reverting back to CPU Mode. I have had that happen early on before, and it is very noticeable.. Still totally stumped. I don't think it is heat?? I have the case open for that with circulation. I noticed right after getting this machine that the cooling through put was seriously lacking.. I am suspecting there was an update in Win 10 that screwed something bigtime up. I have heard of the updates from MS to do that from many people, and it did it two or three times to me with Comm channels.
I view, and render in Texture Shaded. Either through Camera, or Viewport.
I will get a screen shot of what I am talking about in a bit of the monitor, and add it here as an example..
Still trying to finger it out
I view, and render in Texture Shaded. Either through Camera, or Viewport.
I am not sure how to try that??
I will get a screen shot of what I am talking about in a bit of the monitor, and add it here as an example..
Still trying to finger it out
Last edited:
- Aug 17, 2019
- 5,471
- 8,762
Okay, so you've (at least it appears so) counted out the CPU fallback. Opening the case up is going to be better for air circulation for sure, and the GPU doesn't really appear to be throttling at all. So, that's out. I've never experienced Windows updates making Daz screwy, so I can't really speak to that, either. Maybe someone else can handle that more there. You said you already have the latest Nvidia drivers installed, so you can cross that off.
I'm not certain what you mean by this. You should be rendering via Iray (Render Settings > Engine: Nvidia Iray). While rendering, your viewport should be in Texture Shaded. Though, you may be already doing this and I misunderstood the context of what you're saying here. Ignore this, if so.
The more I look, the more I wonder if this is the issue. Nivida recently addressed transparency issue with Ghost Lights in a new update (though, I'm not sure if that was via Daz itself or via their studio drivers.). But seeing as 4.20 (and maybe 4.16? Unsure. Skipped it.) changed how Ghost Lights worked, there might be some confliction going on between the drivers and software. Though, I could just as easily be wrong about that. I'd hold off on updating and see if you can get it back in working order first.
- Oct 23, 2020
- 2,221
- 3,975
Yes that is what I meant.. Sorry bout that.
I just did the Nvidia update Tuesday. The previous driver version was 3 to 4 months old. I do that on purpose. I only get or do driver updates if needed. Just because the manufacture says you need it. If things are working the way it should or you want it. Doesn't mean you have to. I have also found that 'N . E . W' doesn't mean 'G . O . O . D' From what I have read, or think I have read on the DAZ forum the trouble in, and with V4.20 is in DAZ itself... Nvidia's update compensated for the ghost light thing, but I could have misunderstood that also. My mind is muddled from reading all of it...
Still working on it. I did manage to get an update to the game out on Patron, but it took three days to get the last 7 renders and scripted.... That SUCKS!!!!!
Thanks for the replying
- Dec 24, 2021
- 498
- 1,900
- Oct 23, 2020
- 2,221
- 3,975
- Oct 23, 2020
- 2,221
- 3,975
Yes that is what I meant.. Sorry bout that.
I just did the Nvidia update Tuesday. The previous driver version was 3 to 4 months old. I do that on purpose. I only get or do driver updates if needed. Just because the manufacture says you need it. If things are working the way it should or you want it. Doesn't mean you have to. I have also found that 'N . E . W' doesn't mean 'G . O . O . D' From what I have read, or think I have read on the DAZ forum the trouble in, and with V4.20 is in DAZ itself... Nvidia's update compensated for the ghost light thing, but I could have misunderstood that also. My mind is muddled from reading all of it...
Still working on it. I did manage to get an update to the game out on Patron, but it took three days to get the last 7 renders and scripted.... That SUCKS!!!!!
Thanks for the replying
I still haven't found a complete solution to my problem.... I am beginning to think it could be in the Duf file for the scenes ????!! Can't figure out though how all of the sets act the same I will hate to try and rebuild a start set, but may have to.
Still digging!!!!!
- Apr 18, 2021
- 371
- 795
- Oct 23, 2020
- 2,221
- 3,975
Yeah it seems to be working properly with other scene sets, or .duf files. I'm beginning to really think that something may have corrupted the one that started giving me this head ache... Funny thing is though. That at least two files from two periods are acting the same way. I may try reinstalling the assets for the offending scene set.
Still a little baffled over it...
- Aug 23, 2020
- 2,532
- 12,178
Ok guys, I'm kinda at a loss and I need some guidance.
My problems all began when I decided I wanted to shift my pirated assets over to my D drive. As I've discovered, this is a very popular, and tricky, thing to do. I've followed the instructions as best I can, but I'm hitting a dead end and frustration is getting in the way at this point.
Specifically, my problem is this: after I set up the new location to install to in DIM...what do I do next? In the videos or explanations I see, DIM has the files immediately ready for download/installation. But that isn't the case for me, so I'm at a loss for how to even get the process started and I'm extremely frustrated. I'm not a coder, but it doesn't feel like a program should be this unintuitive in 2022. It reminds me a lot of Arc GIS, just a stupidly unintiutive program.
I feel like I'm missing something stupid obvious, but I lack the vocabulary to properly search for it. Just for fun, I'll attach an image of my DIM to show how it's set up.
My problems all began when I decided I wanted to shift my pirated assets over to my D drive. As I've discovered, this is a very popular, and tricky, thing to do. I've followed the instructions as best I can, but I'm hitting a dead end and frustration is getting in the way at this point.
Specifically, my problem is this: after I set up the new location to install to in DIM...what do I do next? In the videos or explanations I see, DIM has the files immediately ready for download/installation. But that isn't the case for me, so I'm at a loss for how to even get the process started and I'm extremely frustrated. I'm not a coder, but it doesn't feel like a program should be this unintuitive in 2022. It reminds me a lot of Arc GIS, just a stupidly unintiutive program.
I feel like I'm missing something stupid obvious, but I lack the vocabulary to properly search for it. Just for fun, I'll attach an image of my DIM to show how it's set up.
- Dec 24, 2021
- 498
- 1,900
Did you point Daz to your content library? Edit>Preferences>Content>Content Directory Manager
- Aug 23, 2020
- 2,532
- 12,178
...
I fucking had Daz pointing to the wrong folder in the directory. I was so focused on DIM that I hadn't double checked Daz.
I'm both relieved, thankful to you, and EXTREMELY irritated.
Actually, while I'm asking stupid questions, I have one more. What's the difference between Daz Studio Formats and Poser Formats in the Content Directory Manager? Right now I only have Daz pointing at the folder I want under Studio Formats. Do I need to also direct Daz to look for the folder under Poser Formats?
- Dec 24, 2021
- 498
- 1,900
I'm on my laptop so I'm not sure what I have in that setting, but I would imagine that's for obj. files and would point it to a directory of your choosing.
If you aren't going to load poser files I don't see why you would need to point it somewhere.
Edit: I'm also just learning and had the same problem of sorts you did when moving to another drive. Haven't used poser at all.
If you aren't going to load poser files I don't see why you would need to point it somewhere.
Edit: I'm also just learning and had the same problem of sorts you did when moving to another drive. Haven't used poser at all.