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
Same here. Another vote for no updates/no crashes. I render 8-24 images per day, complicated scenes and 2-8 characters each.
The only crashes I've had recently have been because of Predatron's latest products, and they don't even begin rendering before failure.
My apologies. I was thinking about the computer's BIOS, (might be called something different for a Mac,) and how the computer handles hardware interrupts. I don't think it's limited to DAZ, as I've had issues with mice for years, even before loading my first copy of DS. However, the render process is very CPU intensive and makes my computer, even the beast, useless for multitasking during a render.
It's really irritating to be using pencil or brush in Photoshop, and suddenly the cursor is, literatly, several inches further along. Or using the draw mask feature and the computer processes a double-click when I click once.
That doesn't mean Daz Studio isn't culpable for any mouse issues. I've never had a program that randomly selected things when clicking on the page, or refused to acknowledge a mouse click the way DS does after it selects bones I wasn't trying to select. That's definitely a problem with Daz Studio, whether or not tech support wants to acknowledge it.
Your monitor going to black sounds like a video card issue. Have you tried updating the driver?
No problem, computers are a mystery sometimes. :) I'm used to the camera freaking out if I try to rotate it with a tablet pen, but the fact that this problem seems fairly recent and that DAZ doesn't seem to think it is a problem at all is troubling.
Same here. Looks like DS works differently than other 3D apps when it comes to mouse control. I tried to install Synergy a while ago but the DS controls went completely nuts on the slave machine when using the mouse. No problems with Hexagon and other 3D apps. A few years ago there were also problems with the mouse jumping if you had a Wacom driver installed.
DAZ usually doesn't monitor forums unless a specific thread is brought to their attention, so if you have a bug to report send a ticket to support.
I'm using version 4.9 of Studio. I have not downloaded any updates to Starter Essentials but I have continued to download Win 10 updates.
So far, I haven't yet encountered the types of problems people here are describing. However, a couple of strange things did happen to me yesterday while working on projects.
1. I was setting up an animation so that I could render some motion blur in a 3DL scene. For some reason, a car I had in the scene actually rotated on its y-axis over the course of the frames I had reserved for the motion for. I did not select the car itself for rotation. I'm willing to dismiss this as some type of flukey side effect of me selecting the wheel to rotate and Daz somehow overgeneralizing as it was a model car a friend created and which isn't for sale in the store. If something hasn't gone through QC, I don't expect it to be perfect.
2. Daz locked on me when I tried to fit some old Genesis clothing on a Genesis figure. The product is one I've used forever and had no problems with. The vendor didn't set up the collar or the shoes to autofit to Genesis (not a terribly big deal IMHO), so I've autofitted it to Genesis many times before. I needed to go into Program Manager and shut Daz down that way.
Normally, I wouldn't pay any attention to either type problem because DS isn't the most stable software on the planet anyway. Given this thread, I am a little more concerned.
Within the last year I've had
1 scene with frames inexplicably blacked out beyond frame 33. Copied the scene, deleted existing frames from the copy and carried on.
1 scene became corrupted and unreadable a little more than 2 weeks ago. I've gotten in the habit of saving a working scene and a backup original which I probably should have been doing anyway.
3 crashes in the last year that I can recall, one of which I suspect was a conflict with a game I was running in the background, one that I suspect was actually Netflix crashing.
I haven't seen any difference in DS performance in the last few weeks except that corrupted scene file.
Using Windows 10, always updated to latest. DS always updated to latest. Computer was self built Dec '16 with a 1050ti and this December upgraded to 1080ti. I'm more than satisfied with the performance and would have expected more crashing considering how far I tend to push DS.
My crashes started shortly after the updates to the starter essentials which I had installed through DIM. I updated my nvidia driver to the latest version (I had been using one from last November) and have had no crashes since. A scene that was routinely crashing on the second iray render now works fine. That may not be the cause for everyone's crashes but it seems to have played a role in mine.
Just for simple video editing Windows Movie Maker has "autosave" for those moments. I also have Corel Video Studio, with a full timeline and video effects, music, sound effects...the software would crash on me but thank the gods for autosave and I could keep right on going afterwards. But in Daz's case 22hrs into rendering an animation, it crashed. Fortunately for me I chose to render it as an image series so I could pick up from the frame that it crashed to continue. It happened 5 times total, plus I did not enjoy loading at least 500 frames into Corel Video Studio just to get an Avi file that Daz was able to do before without crashing. Sorry for the rant, but this thread pretty much nailed it for me.
I don't get crashes either. I am less terrified though since my installation doen't seem to have nearly as many issues as some. I realize I've probably cursed myself now. I have installed updates vis DIM. Studio 4.10.0.123, Windows 7.
Just out of curiousity, is there any other background process that kicks in while you folks are rendering to cause the crash like a scheduled/unscheduled Virus Scan / Malware Scan / Backup, etc?
Could there have been an update to your anti-virus or malware softwre that is conflicting with DS?
That is a possible graphics driver; also is it possible you have a fault, or something has worked loose. But tbh, troubleshooting with guess work is sure to only frustrate one, as opposed to locating the problem.
Brand new machine, up to date graphics driver.
Not every day, across multiple machines sometimes several times a day.
I just lost a 20 hour render for a promo. I clicked to stop the render as it was far enough that it was usable. As soon as I clicked on yes I want to cancel the render it crashes. Why does Studio not have someithing that autosaves while in progress? Or at least saves the actual render itself? Its in a separate window. Did I save the scene? Yes. Does it matter? No. I don't have time to render this for another 20 hour long time period. This is totally unacceptable. I have to walk away for a bit. I'm sincerely pissed off now.
So where do I find the render it was working on?
Sometimes if you don’t reopen Studio the render is saved in a temp file on your computer. I’m not sure right now as I’m at work the specific location.
It goes in the temp folder, which is cleared when DS closes (properly, not for crash) or opens. You don't want to do this if you haven't yet restarted DS, since doing so will wipe any temp files, but for future use you can run this script (by Rob) to open the render temp folder and place a bookmark on the desktop:
The default location, if you need to manually navigate to check for the current render, is C:\Users\YOU\AppData\Roaming\DAZ 3D\Studio4 Private Build\temp\render
Yes, don't reopen studio or the render WILL be lost. Replace my name with your computer name of course ;)
What we really need is a script that will copy the temporary render file, (r.png on my computer,) into a specified folder with a date/time stamp in the name, and then open Daz Studio. Then we can run that script to open DS and if there's a render file in temp, it gets saved automatically and we don't have to worry about it.
Well, to run the script DS would have to be open. Once you knew the location it would be possible to write a batch file or the like to do the copy, then launch DS, but that would not (I think) be able to read the location from the system for itself - or at least not easily.
Any possibilty of convincing the development team into creating a function to do this when DS is opened, before it clears out the temp file? That would really be an awesome feature…
Well, thanks for that anyway. Too late for this last render since I already redid the scene and started over. But thank you, that may save my poor husband's ears.
Until then, here's one for Windows, if anyone want to test it (works fine for me).
It's pretty straightforward:
1. to configure it press Shift while starting it, to open the configuration window. After it's been configured, close it again. You must do this the first time you run it.
2. to back up, just start it (no Shift), and it will automatically copy the render (if there is one) to the backup folder, confirm the render has been backed up, and start DS. If there is no render, it will just start DS.
Requires NET 4.0.
http://taosoft.dk/software/freeware/rb-daz/RenderBackupDAZ-a0500.zip
Well that turns the frown upside down! Thanks!

Remind me I need to buy you a virtual beer ;)
Laurie
I have had crashes lately too and never had it crash on me before that.