Loading...
> >

Scenes created under BETA 4.12.1.117 no longer load under Production version of 4.12.1.117

CA415CA415 Posts: 165
in Technical Help (nuts n bolts)

Last week, I created a number of complex scenes under the Beta version of 4.12.1.117, and now, using the new Production release 4.12.1.117, the scenes no longer load.  They originally loaded under the Beta version of DAZ Studio in about 4 minutes, now DAZ Studio just sits there for hours trying to load the scenes.

Has anybody elese noticed serious memory management and file I/O problems with the new version 4.12.1.117?

Comments

  • DAZ_RawbDAZ_Rawb Posts: 817

    The code for the beta and the release of 4.12.1.117 is the exact same.

     

    However, the settings for the two versions is different. Part of the difference is the set of plugins you have installed, could you try launching the production release and disabling all plugins to see if that helps?

  • fixmypcmikefixmypcmike Posts: 19,583

    The Beta 117 and production 117 are the same, so there must be a difference in the settings.  Does Content Directory Manager show exactly the same folders in the same order?

  • CA415CA415 Posts: 165

    Thanks for the quick responses everyone.

    The new production version of DAZ Studio uses the Microsoft Visual C++ 2015-2019 Redistributable (x64) - 14.23.27820.  This collection of dynamic link libraries appears to be the source of the problem - depending on the installation destination of DAZ Studio.

    When I test Beta versions of DAZ Studio, I create manual installation directories on D:\ for each new Beta version.  

    The DAZ Studio default installation destination is C:\Program Files\DAZ 3D\DAZ Studio4\.  If I manually create an installation destination at D:\DAZ Studio-Prod-4-12-1-117\ and copy all of the production build files to that location, and launch the DAZ Studio executable from there, the scene files load correctly.

     

    Scene Files:

    "Castle-Standalone.duf" [Requires 26.5 GB Working Memory]

    Success:                           Fail:
    4.12.0.86-Prod [D:]            4.12.1.117-Prod [C:] [Fails @ 5.5 GB Memory allocation]        
    4.12.1.76-Beta [D:]
    4.12.1.117-Beta [D:]
    4.12.1.117-Prod [D:]

    "Castle-Group.duf" [Requires 32 GB Working Memory]

    Success:                           Fail:
    4.12.0.86-Prod [D:]            4.12.1.117-Prod [C:] [Fails @ 5.5 GB Memory allocation]        
    4.12.1.76-Beta [D:]
    4.12.1.117-Beta [D:]
    4.12.1.117-Prod [D:]

    I'm guessing that specific calls to the DLLs in the new VC++ Redistributable need to be corrected to resolve this issue for the default installation location of DAZ Studio.  In the meantime, I'm forced to launch the DAZ Studio production build from the custom installation directory on D:\.

  • CA415CA415 Posts: 165

    The latest DAZ Studio Pro Public Build 4.12.2.6 appears to have resolved this issue.

    Large, complex scene files are now loading correctly under the new BETA build.

    Thanks to the DAZ Studio development team.

  • Richard HaseltineRichard Haseltine Posts: 100,781
    Colin said:

    The latest DAZ Studio Pro Public Build 4.12.2.6 appears to have resolved this issue.

    Large, complex scene files are now loading correctly under the new BETA build.

    Thanks to the DAZ Studio development team.

    The change log doesn't indicate anything that would affect saving times, I suspect any change is down to settings or the like. http://docs.daz3d.com/doku.php/public/software/dazstudio/4/change_log

  • CA415CA415 Posts: 165

    Thanks, Richard.  Sorry for the long delay in responding.

    I appreciate your thoughts and feedback.

    Yes, it isn't clear from the change_log how the file load and/or memory allocation problems were fixed.  

Sign In or Register to comment.