Loading...
> >

Large Setting - Running Slow

CostelloCostello Posts: 97
in The Commons

Hi! I have created a large city setting and, probably not surprisingly, DAZ is now running quite slowly for pretty much every operation I try to make. The ovearall file size is about 32mb, which sounds pretty small, but I guess is pushing things in DS. 

 

I am using a MacPro 2013 and am mostly working in wireframe mode to make things run a bit faster than in the shading mode. I am looking for any memory or setting tricks to make things run faster. Any thoughts you have would be greatly appreciated. 

Comments

  • Ken OBanionKen OBanion Posts: 1,455

    That file size doesn't really mean all that much when it comes to how much memory your scene is using; the DUF file only contains reference to the assets used by the scene, which are then loaded as the file is read.  So, depending on what you are using, you could have some seriously huge objects in your scene.

  • CostelloCostello Posts: 97

    Thanks. Is there a way to sort a scene and see which objects are using the most memory? Also, are there just some general settings that can be set differently to speed up the process?

  • MaxHancockMaxHancock Posts: 227

    Actually, texture shaded is faster than wireframe mode (command-9), unless you are using the very lowest (command-1, wire box).  

    Also, customize your interface so it doesn't highlight everythign when you hover over an item in the scene, that will speed up your work flow a bit. 

    Turning off some interactive updates for figure clothing will speed things up too. 

  • MaxHancockMaxHancock Posts: 227

    This thread might help you: 

    http://www.daz3d.com/forums/viewthread/52331/

     

  • Ken OBanionKen OBanion Posts: 1,455
    Costello said:

    Thanks. Is there a way to sort a scene and see which objects are using the most memory? Also, are there just some general settings that can be set differently to speed up the process?

    Since you're using a Mac, is there any utility that does the same as Task Manager in Windows?  (Shows what apps are loaded, running, how much RAM they're using, disk I/O, and such; it's been quite a few years since I've used a Mac, and I've downed a lot of Martinis since then...!)

    Other than that, I'm not aware of any tools that can tell you exactly what's using how much RAM (although there's probably one out there somewhere, and I just haven't stumbled across it yet; if not, maybe I should write one...), short of opening the scene's DUF file, noting what it's loading, and then looking up each file's info.  It might give you a ball-park, SWAG-ish estimate.  Rather a chore, that would be!

  • CostelloCostello Posts: 97
    edited May 2016

    Thanks a lot! You've both given me good stuff to try. I use DAZ all the time but I'm working on a large scale set of downtown Victorian era London (multiple city blocks) so this is definitely pushing the usual envelope for me.

    Post edited by Costello on
  • 3delinquent3delinquent Posts: 355

    The more you have in the scene the more studio has to redraw every time you orbit, zoom or pan the camera. Running the auxiliary viewport can slow things down depending on what you are doing. High resolution meshes or many objects (lots of polygons), high res textures and materials, smoothing, your computers processing capabilities and a whole bunch of other stuff can slow things down.

    There is a thread somewhere that says something about clearing cache as it could be causing problems. If you know what that is exactly then you're ahead of me.  Maybe someone can comment.

    Hiding stuff in the scene while you are not working directly on it or with it is supposed to help. It doesn't seem to work much for me but that could also have something to do with the cache thing. Turning off smoothing on stuff with it applied generally does speed things up, especially hair and anything with very high smoothing settings. Of course you have to remember to turn everything back on before you render.

    If when you orbit in the scene a little orange progress bar appears beneath the viewport for a while, then you know studio is catching up to your computers capabilities in this. The longer that progress bar take to progress, the more heavily you are taxing it.

    These things may not be your problem but it was all I could think of.

  • cosmo71cosmo71 Posts: 3,609
    Costello said:

    Hi! I have created a large city setting and, probably not surprisingly, DAZ is now running quite slowly for pretty much every operation I try to make. The ovearall file size is about 32mb, which sounds pretty small, but I guess is pushing things in DS. 

     

    I am using a MacPro 2013 and am mostly working in wireframe mode to make things run a bit faster than in the shading mode. I am looking for any memory or setting tricks to make things run faster. Any thoughts you have would be greatly appreciated. 

    alone my character file AVA with all hair and clothes and accessoirs is about 360MB and slows my system not down and when I load another character with a file size around 100 MB and some other stuff into the scene it also takes my system not down dramatically. That happens first when I load some special hair with lots of transmaps into the scene, too, then it begins to slow down and I have just 6GB ram.

  • cosmo71cosmo71 Posts: 3,609
    Costello said:

    Thanks. Is there a way to sort a scene and see which objects are using the most memory? Also, are there just some general settings that can be set differently to speed up the process?

    What takes a lot are trans maps, so if you have a lot of trees in your scene this could be an issue.

  • CostelloCostello Posts: 97

    I do have a lot of trees in the scene. I'll maybe have to whittle them down or find some lower rez trees.

     

  • mjc1016mjc1016 Posts: 15,001

    If they are the same tree...load them as instances instead of duplicates. 

  • HavosHavos Posts: 5,576
    cosmo71 said:
    Costello said:

    Hi! I have created a large city setting and, probably not surprisingly, DAZ is now running quite slowly for pretty much every operation I try to make. The ovearall file size is about 32mb, which sounds pretty small, but I guess is pushing things in DS. 

     

    I am using a MacPro 2013 and am mostly working in wireframe mode to make things run a bit faster than in the shading mode. I am looking for any memory or setting tricks to make things run faster. Any thoughts you have would be greatly appreciated. 

    alone my character file AVA with all hair and clothes and accessoirs is about 360MB and slows my system not down and when I load another character with a file size around 100 MB and some other stuff into the scene it also takes my system not down dramatically. That happens first when I load some special hair with lots of transmaps into the scene, too, then it begins to slow down and I have just 6GB ram.

    360 MB is pretty big for a character file, a fully dressed character should be savable in a file of 2-3MB or less. I am guessing that you have either a lot of auto-fitted clothing on her, or you have injected additional clothing morphs with something like fit-control. Either way it is a good idea to save the clothing items as figure/prop assets, then delete them, and reload the saved item. Otherwise all the mesh info etc gets stored in the scene file, which takes longer to save each time you make a change.

  • PlantPlant Posts: 127

    I've found if i save the file before rendering close Daz studio down then start afresh and render it speeds things up quite alot

  • cosmo71cosmo71 Posts: 3,609
    Costello said:

    I do have a lot of trees in the scene. I'll maybe have to whittle them down or find some lower rez trees.

     

    I would guess the trees make the trouble

  • cosmo71cosmo71 Posts: 3,609
    edited May 2016
    Havos said:
    cosmo71 said:
    Costello said:

    Hi! I have created a large city setting and, probably not surprisingly, DAZ is now running quite slowly for pretty much every operation I try to make. The ovearall file size is about 32mb, which sounds pretty small, but I guess is pushing things in DS. 

     

    I am using a MacPro 2013 and am mostly working in wireframe mode to make things run a bit faster than in the shading mode. I am looking for any memory or setting tricks to make things run faster. Any thoughts you have would be greatly appreciated. 

    alone my character file AVA with all hair and clothes and accessoirs is about 360MB and slows my system not down and when I load another character with a file size around 100 MB and some other stuff into the scene it also takes my system not down dramatically. That happens first when I load some special hair with lots of transmaps into the scene, too, then it begins to slow down and I have just 6GB ram.

    360 MB is pretty big for a character file, a fully dressed character should be savable in a file of 2-3MB or less. I am guessing that you have either a lot of auto-fitted clothing on her, or you have injected additional clothing morphs with something like fit-control. Either way it is a good idea to save the clothing items as figure/prop assets, then delete them, and reload the saved item. Otherwise all the mesh info etc gets stored in the scene file, which takes longer to save each time you make a change.

    have a lot of clothes (different outfits to mix and match) fitted and adjusted and some hair and stuff, I begin to save the clothes out as scene subsets, that is a need because they are adjustet sometimes to my character. And yes, there are outfitet and fit control clothes in the file also "real" pubic and armpit hair besides normal head hair

    Post edited by cosmo71 on
  • HavosHavos Posts: 5,576
    cosmo71 said:
    Havos said:
    cosmo71 said:
    Costello said:

    Hi! I have created a large city setting and, probably not surprisingly, DAZ is now running quite slowly for pretty much every operation I try to make. The ovearall file size is about 32mb, which sounds pretty small, but I guess is pushing things in DS. 

     

    I am using a MacPro 2013 and am mostly working in wireframe mode to make things run a bit faster than in the shading mode. I am looking for any memory or setting tricks to make things run faster. Any thoughts you have would be greatly appreciated. 

    alone my character file AVA with all hair and clothes and accessoirs is about 360MB and slows my system not down and when I load another character with a file size around 100 MB and some other stuff into the scene it also takes my system not down dramatically. That happens first when I load some special hair with lots of transmaps into the scene, too, then it begins to slow down and I have just 6GB ram.

    360 MB is pretty big for a character file, a fully dressed character should be savable in a file of 2-3MB or less. I am guessing that you have either a lot of auto-fitted clothing on her, or you have injected additional clothing morphs with something like fit-control. Either way it is a good idea to save the clothing items as figure/prop assets, then delete them, and reload the saved item. Otherwise all the mesh info etc gets stored in the scene file, which takes longer to save each time you make a change.

    have a lot of clothes (different outfits to mix and match) fitted and adjusted and some hair and stuff, I begin to save the clothes out as scene subsets, that is a need because they are adjustet sometimes to my character. And yes, there are outfitet and fit control clothes in the file also "real" pubic and armpit hair besides normal head hair

    Saving out as sub-sets does not really help, as they will still drag in all that data when merged into the scene. Thus it is better to save them as prop/figure assets, so that all the geometry, morphs etc sits in your data directories, and then including them will only add a few 10s of kilobytes to your scene file.

  • 3delinquent3delinquent Posts: 355

    Nice to know that Havos. Thanks.

     

  • RuphussRuphuss Posts: 2,631
    Plant said:

    I've found if i save the file before rendering close Daz studio down then start afresh and render it speeds things up quite alot

    the case is studio has a weird ram behavior dont know since when

    i had a scene where everything was deleted so nothing in the scene left

    but still 13 gb ram used and no way to get rid of it

Sign In or Register to comment.