Thu, Nov 28, 9:57 PM CST

Renderosity Forums / DAZ|Studio



Welcome to the DAZ|Studio Forum

Forum Moderators: wheatpenny Forum Coordinators: Guardian_Angel_671, Daddyo3d

DAZ|Studio F.A.Q (Last Updated: 2024 Nov 28 3:41 pm)



Subject: DAZ Studio unexpectedly closes


tuxedomask ( ) posted Sat, 19 January 2019 at 5:47 AM ยท edited Thu, 28 November 2024 at 9:55 PM

Why does DAZ studio 4.10 unexpectedly close when working on a very simple scene Example : Victoria 8/ Genesis and nothing else in the render scene ?


lwperkins ( ) posted Sat, 19 January 2019 at 8:41 AM

It usually happens to me when I am fooling with the lights--sometimes there is some weird conflict between the environmental lights, the camera auto light, and the ones we load in manually. Then poof! It doesn't seem to be like Poser, where Poser bogs down with too many polygons/textures. That said, V8 and her normal maps can hit 500 mb easy, especially when you add a complicated outfit. Try adding things one at a time and keep saving your scene.


RHaseltine ( ) posted Sat, 19 January 2019 at 8:52 AM

Do you get a crash report dialogue, or does it go straight to desktop? You could try checking the end of the log file for hints - on Windows it will be C:/Users/YOU/AppData/Roaming/Daz 3D/Studio4/log.txt which you can reach by pasting this into the address bar of a file window

%AppData%/daz 3d/Studio4/


lwperkins ( ) posted Sat, 19 January 2019 at 9:42 AM

I just remembered that if you are doing a lot of renders and cancelling them, be sure to look "behind" the user interface to where the unfinished renders are still open, and close them, as they take memory too. If you cancel renders on the pane where you would normally save them, it's easier to remember to close them as the button is right there.


tuxedomask ( ) posted Sat, 19 January 2019 at 3:30 PM

Iwperkins, thanks for the the info .I'm new to DAZ Studio and just trying to get a handle on how it all works.I have been doing exactly that adding only one thing at a time to my scene eg Victoria 8 and then hair , clothes etc.I think what you mentioned about cancelling a render that is in progress could be what is causing me the problem .I'll have to try closing any part completed renders that were cancelled.


tuxedomask ( ) posted Sat, 19 January 2019 at 3:34 PM

RHasetime.My computer went straight to desktop.I'll try the end of log file for hints .Thanks for the reply .


lwperkins ( ) posted Sat, 19 January 2019 at 7:05 PM

Once you learn Daz Studio's little ways it does make such a nice render, it's worth the aggro. Also poke around in the render tab and try the different lighting methods--Dome/Dome and Scene/ and Sunlight Only. That one can be really great--you need to pick a "time" at the bottom of the pane... like around 1 Pm and just fool with it. You can turn off the camera's autolamp too and see how that works. Have fun!


tuxedomask ( ) posted Sat, 19 January 2019 at 11:04 PM

Thanks . I will .


skinklizzard ( ) posted Sun, 20 January 2019 at 7:43 PM

saving fast and furiously is probably the best advice, daz can be a perfectly well behaved beast and then it eats you in a fit of unprovoked madness especially when you get to trying to break the dforce engine.

if you're not already it might be a good idea to load items in and set up your initial scene with the preview window set to smooth shaded or texture shaded and only iray preview once everything is more or less placed as you want it. conflicting content can also cause instant crashes on attempting to load a figure (I somehow made a g8f morph that would kill my saved scene and daz on load).

the log file can get pretty long winded if you've been running for a while so you can try delete it then launch and load your scene that way there will be only the current info in the log file and it might be easier to diagnose.


Privacy Notice

This site uses cookies to deliver the best experience. Our own cookies make user accounts and other features possible. Third-party cookies are used to display relevant ads and to analyze how Renderosity is used. By using our site, you acknowledge that you have read and understood our Terms of Service, including our Cookie Policy and our Privacy Policy.