Adding to Cart…
Licensing Agreement | Terms of Service | Privacy Policy | EULA
© 2025 Daz Productions Inc. All Rights Reserved.You currently have no notifications.
Licensing Agreement | Terms of Service | Privacy Policy | EULA
© 2025 Daz Productions Inc. All Rights Reserved.
Comments
You're welcome! :)
I'll let you know if I should get virtually thirsty... :)
Wish it were that simple, but the answer for me would be no. My updates are scheduled for 5am-7am's.
I've had more crashes tan before, too. What I did notice is that DS doesn't properly clear out of the system's memory when you close it or it crashes, but remains in it for quite a while. I also have the problem that when I start a render in Iray, and stop it, and make some small changes in position, and start a new render of the same image, the render then switches to CPU mode. If I save the file and reload it, it renders perfectly fine in GPU mode again.
I regulary have to start the task manager and manually close the DS "ghost". This happens with both, DS 4.8 and DS 4.10 Beta, though more often with the Beta.
DS has always taken a while to finish its clean-up, after the application has gione from the task Bar or Dock, depending on what was loaded. If it's taking extra-long then that may indicate that the crash was a memory issue. As tiem goes by out base figures accumulate more morphs, and those seem to me to affect clean up time (it's worse with Genesis 3 loaded than Genesis 8, for example) so if it is memory related that might account for its seeming to get worse recently.
Daz lingering in memory after I've closed it doesn't seem nearly as noticeable to me as it used to, despite the increase in crashes. I'd almost forgotten how often I used to have to close it properly via task manager.
I haven’t used DS much since installing the Starter Essentials updates but I do get a crash almost 100% of the time when I try to fit a G3 hair to G8.
I'm using 4.9 and 4.10 public beta on a Mac with no crashing problems whatsoever. (Well shadermixer triggers some random crashes but it's always been unstable.) I render exclusively in 3DL, I don't know, is it an IRay thing? Oh and I haven't downloaded the starter essential updates.
Could be IRay. I don't use 3DL at all any more.
...Is there still the issue of VRAM not being freed up after a render process in Iray completes or is terminated early?
Seems to be
...thanks. Guess I'll just wait for Octane4.
Just wanted to chime in and say I'm getting crashes suddenly too. Making me lose tons of work all the time. What a freaking pain. Almost makes me want to quit DS till this is sorted out.
I hope you don't quit! I totally get the frustration though!
Also using 4.9 and 3Delight with no major crash issues. Did have some crashes a month or so ago but determined it was a memory issue related to an anti-malware program running in the background.
I got another crash... Ugh... 86 percent...... Module screenshot attached....
I see that access violation fairly frequently.....
https://www.migenius.com/doc/realityserver/4.4/resources/general/iray/api_reference/iray/html/group__mi__neuray__ineuray.html
Looks like memory was attempted to be accessed that does not exist. You should file a bug with DAZ.
I will file a report next error I get. Unfortunately I do not have great luck with tech support so I usually do not bother.
Doesn't happen for me. You do need to close the render window.
You're awesome! Thanks so much! ::Does a happy dance::
You're welcome!
I just had a crash, a scene I had JUST rendered with everything in the scene, no problem. Took out about 40% of the items when I changed the camera angle, so much less in the scene, and it crashed after about 45 seconds. This is just garbage. Renders fine with everything in the scene, crashed with less. And the scene wasn't challenging. Just a set, no characters, nada.
Here's my latest:
Nother crash here as well. Had another odd thing happen as well. I've got my scene set to a custom size ( I render at 2000 and above) so I had it set to Wide2000 which is just 2000 x 2300 if I remember correctly. I ALWAYS render to a custom size. I started my render and it started rending to active viewport view instead. I've NEVER seen it do that and I have zero reason to want to do that. My scene was still set to my custom settings, which I always check before hitting render as I need the higher resolution. It was still set to my custom setting despite it rendering to the active viewport view. I'm only mentioning this because its like the third time its happened in the last couple of weeks and because Studio crashed right after that.
This script will disable all additional plug-ins, leaving just those published by Daz and AniMate - it might be worth seeing if that helps with the crashing http://docs.daz3d.com/doku.php/public/software/dazstudio/4/referenceguide/scripting/api_reference/samples/plugins/plugins_load_config/start
My special library of DAZ crashes seems to continue to grow.... I guess its like Pokeman, I need to get every posisble error there is. =-)
Tonight my machine crashed twice while rendering the new Winter Men's outfit.
Those crashes are in the same two functions that the earlier two crash reports you talked were in. If you save the scene, & both crash dump files it should be easy for DAZ support to at least state the reason why the crash is happening both times. If it's a problem in an external library like iRay they can't really fix it unless they are sending the library bad data.
Are you iRay preview rendering in your viewport instead of openGL preview rending in your viewport?
I don't know how to see what my viewwport preview method is. It
In the past, I've never been asked for a scene file when I submitted crash dumps. I usually submit the log. I've only ever gotten one response to a log submission and it was too long after I submitted it to answer questions of what I was doing when it occured. I get one of these at least every other day to once a day now.