DAZ Studio getting very slow with no big scene at all

YanaYana Posts: 5
edited December 1969 in Daz Studio Discussion

I thought my Mac wasn't that bad. However DAZ Studio is getting very slow on an early point. I'm talking about having two figures in the scene. Or just one Environment from Stonemason. (The problem is getting worse with these Environments. That is kind of frustrating, because I love them so much)
When I try to move the camera around, the actions are so extremely delayed, that it's no fun at all to search for the right camera position. When I change the view to wireframe instead of texture shaded it's getting a little bit better. But that cannot be the solution. I just can't believe, that the performance of my Mac is that bad! Has anyone an idea how to fix that problem.

My system:
iMac 27'' late 2013
3,2 GHz Intel Core i5
16 GB RAM
NVIDIA Geforce GT 755M with 1024MB
OS X Yosemite (the problem did also appear on Mavericks)

Comments

  • Richard HaseltineRichard Haseltine Posts: 100,781
    edited December 1969

    What settings do you have in Edit (or possible Apple menu)>Preferences>Interface tab, in the OpenGL group?

  • YanaYana Posts: 5
    edited December 1969

    Per Pixel Shading: Off
    Hardware Anti-Aliasing: On
    Display Optimization: None
    Backface Lighting: On
    Texture Resources: ca. 30%
    Pixel Buffer: Off 1k x 1k

  • Richard HaseltineRichard Haseltine Posts: 100,781
    edited December 1969

    Try setting Display Optimisation to Best. If that doesn't work try Better. I am using an older, but not mobile, nVidia GPU (450GS I think) and best works fine.

  • YanaYana Posts: 5
    edited December 1969

    It's slightly better, thanks. There's still a delay when moving the camera - I let go of the mouse button and it slides further - but it's lighter than before.

  • Steven-VSteven-V Posts: 727
    edited December 1969

    Turn your texture resources all the way down to "Performance." You don't need to see texture resources accurately in the edit window, just in the render.

    Also, check the parameters (General) and look to see if any of the objects have "interactive update" checked to "on." Turn it "off." I have noticed this usually with clothing, so if you don't have clothing this may not be an issue. But for me, whenever even one object, like a pair of pants, is set to having Interactive Update "on," the entire edit window bogs down to molasses.

  • 3WC3WC Posts: 1,107
    edited December 1969

    I don't mean to hijack this thread, but I've been having a similar problem lately--keep meaning to ask about it, and this thread reminded me.

    Anyway, DS 4.7 has been very slow to start for me lately. After clicking the icon, I sometimes have to wait a solid MINUTE for it to do anything. Then the startup splash screen appears, and goes through its thing for about another 30 seconds before the program opens.

    I have a fairly basic system, Win7 Home Pro on a Corei3 system with 4G Ram. But, havin said that, I never had any problems before just a few weeks ago. Was there an update that slowed things down, or could I be having other problems?

  • WendyLuvsCatzWendyLuvsCatz Posts: 38,204
    edited December 1969

    I personally think both DAZ studio and Carrara got slower after my last nVidia update
    in fact I have been trying wireframe with the octane render viewport open in preference to using the openGL viewport in DAZ and Carrara have been switching between openGL and software in preferences trying to figure out which is the least laggy, again Octane render seems unaffected and smooth with the assembly room in wireframe which suggests it is an openGL issue.

  • fixmypcmikefixmypcmike Posts: 19,583
    edited December 1969

    wwes said:
    I don't mean to hijack this thread, but I've been having a similar problem lately--keep meaning to ask about it, and this thread reminded me.

    Anyway, DS 4.7 has been very slow to start for me lately. After clicking the icon, I sometimes have to wait a solid MINUTE for it to do anything. Then the startup splash screen appears, and goes through its thing for about another 30 seconds before the program opens.

    I have a fairly basic system, Win7 Home Pro on a Corei3 system with 4G Ram. But, havin said that, I never had any problems before just a few weeks ago. Was there an update that slowed things down, or could I be having other problems?

    Do you have Reality 4?

  • 3WC3WC Posts: 1,107
    edited December 1969

    wwes said:
    I don't mean to hijack this thread, but I've been having a similar problem lately--keep meaning to ask about it, and this thread reminded me.

    Anyway, DS 4.7 has been very slow to start for me lately. After clicking the icon, I sometimes have to wait a solid MINUTE for it to do anything. Then the startup splash screen appears, and goes through its thing for about another 30 seconds before the program opens.

    I have a fairly basic system, Win7 Home Pro on a Corei3 system with 4G Ram. But, havin said that, I never had any problems before just a few weeks ago. Was there an update that slowed things down, or could I be having other problems?

    Do you have Reality 4?

    No.

  • WendyLuvsCatzWendyLuvsCatz Posts: 38,204
    edited December 1969

    wwes said:
    wwes said:
    I don't mean to hijack this thread, but I've been having a similar problem lately--keep meaning to ask about it, and this thread reminded me.

    Anyway, DS 4.7 has been very slow to start for me lately. After clicking the icon, I sometimes have to wait a solid MINUTE for it to do anything. Then the startup splash screen appears, and goes through its thing for about another 30 seconds before the program opens.

    I have a fairly basic system, Win7 Home Pro on a Corei3 system with 4G Ram. But, havin said that, I never had any problems before just a few weeks ago. Was there an update that slowed things down, or could I be having other problems?

    Do you have Reality 4?

    No.
    I do

  • Harry DresdenHarry Dresden Posts: 376
    edited February 2015

    Do you have Reality 4?

    Hah, I know why you asked that Mike. Reality can end up making them load times longer for sure. Used to drive me crazy but it seemed to get fixed along the way although I'm still stuck with 2.50.

    As for the topic at hand I can't say I've noticed any problems loading or navigating scenes in DS 4.7 but then I'm forever updating drivers and everything else. Swyditch, I would suggest maybe starting there. Update all relevant drivers and OS stuff and see if that helps.

    As for wwes, get a new computer. I don't mean that in a bad way but you'll find texture sizes are getting bigger and bigger and models are getting more and more polygons as content creators strife for reality. At the bare minimum get more RAM if you can't afford a big upgrade right away. Presuming of course you have a 64 bit OS.

    Post edited by Harry Dresden on
  • 3WC3WC Posts: 1,107
    edited December 1969

    As for wwes, get a new computer. I don't mean that in a bad way but you'll find texture sizes are getting bigger and bigger and models are getting more and more polygons as content creators strife for reality. At the bare minimum get more RAM if you can't afford a big upgrade right away. Presuming of course you have a 64 bit OS.

    Yeah, at least more RAM is in order for the time being.

    But textures shouldn't be loading when the program is first starting up, should it? I have DS set not to load any scene at startup, so 90 seconds just to open seems a bit excessive. And as I say, it's only been that way for a few weeks. My tiny computer has had no problems thus far. That's why I was wondering if something in a recent update to DS or the CMS has slowed things down for me.

  • KeryaKerya Posts: 10,943
    edited December 1969

    Starting time for DazStudio depends for me on which of my external DazStudio Libraries or Poser Runtimes I had opened when I closed DS ... some of those are BIG, others smaller ...
    Just an idea for you to check.

  • 3WC3WC Posts: 1,107
    edited December 1969

    Kerya said:
    Starting time for DazStudio depends for me on which of my external DazStudio Libraries or Poser Runtimes I had opened when I closed DS ... some of those are BIG, others smaller ...
    Just an idea for you to check.

    This actually led me to the answer. It didn't matter which library/runtime was open, but... I was earlier trying to test all the paths in a product I was making, so copied it all to another computer on the network. That way I could tell if the paths were relative. So apparently CMS was spending a lot of time trying to find that runtime location on another computer. Once I removed that path from the content directory, my load time went from 90 seconds to 9 flat.

    Thanks.

  • KeryaKerya Posts: 10,943
    edited December 1969

    Yipppiiiee!

  • ColemanRughColemanRugh Posts: 511
    edited December 1969

    Excellent thread! very helpful! Thanks!

  • stormqqstormqq Posts: 76
    edited December 1969

    I had the same issue so I made it default and now it's perfect.

  • MaxHancockMaxHancock Posts: 226

    For the longest time I didn't realize that DAZ throttles the pan movements of the camera using the standard mouse controls... because it's set for subtle movements around a figure, and it's very irritating when you are working on a large scene, it takes forever to move the camera from one side the building block to the next with the mouse.  

    Instead you need to familiarize yourself with the key controls to make movements much much faster.  You use the W A S D keys to move the camera in space.  Q and E to move the camera up and down. There are others for tilting the camera but I forget what they are. U O maybe.  And, to speed up or slow down those movements use the bracket keys, [ to slow down ] to speed up.  

    DAZ anti-aliases wireframes by default, and that can make a dense mesh really slow, slower than if you were using full texture shaded mode.  You can speed wireframes up by going to your preference and turning off anti-aliasing, restart DAZ to see the change.  

     

  • OHG @RichardHaseltine - you are a mega genius. Thanks for sharing your wisdom

  • Kerya said:

    Starting time for DazStudio depends for me on which of my external DazStudio Libraries or Poser Runtimes I had opened when I closed DS ... some of those are BIG, others smaller ...
    Just an idea for you to check.

    Yes, that's why I close all libraries to their main headers, before closing DAZ Studio. Every little bit uses RAM, and without a lot of RAM on my machine, I need to be careful about how I do things.

  • Steven-V said:

    Turn your texture resources all the way down to "Performance." You don't need to see texture resources accurately in the edit window, just in the render.

    Also, check the parameters (General) and look to see if any of the objects have "interactive update" checked to "on." Turn it "off." I have noticed this usually with clothing, so if you don't have clothing this may not be an issue. But for me, whenever even one object, like a pair of pants, is set to having Interactive Update "on," the entire edit window bogs down to molasses.

    Try setting Display Optimisation to Best. If that doesn't work try Better. I am using an older, but not mobile, nVidia GPU (450GS I think) and best works fine.

     

    Bumping to say that these two were really helpful for me.

     

Sign In or Register to comment.