Long Load Times - Fixing Warnings

ForceXForceX Posts: 52
edited June 2019 in Daz Studio Discussion

I've been fixing all the warnings when characters are added to a sceen and am finally down to my last 3 warnings but have not idea how to resolve them.

 

2019-06-29 14:20:20.487 JSON interpreter warning: Unexpected member object: pSadation2019-06-29 14:23:09.843 WARNING: ..\..\..\..\..\src\sdksource\fileinput\dzassetdaz.cpp(7848): Failed to add user alias property to node.2019-06-29 14:23:09.843 WARNING: ..\..\..\..\..\src\sdksource\fileinput\dzassetdaz.cpp(1451): Failed to create alias!2019-06-29 14:25:05.070 Begin Loading Character Addons...2019-06-29 14:25:05.579 File loaded in 0 min 0.4 sec.

 

As you can see these 3 issues are taking 5 min to resolve when loadign a G8F character.

 

Error # 1 JSON interpreter warning

2019-06-29 14:20:20.487 JSON interpreter warning: Unexpected member object: pSadation

 

Eror # 2 & 3 Failed alias

2019-06-29 14:23:09.843 WARNING: ..\..\..\..\..\src\sdksource\fileinput\dzassetdaz.cpp(7848): Failed to add user alias property to node.2019-06-29 14:23:09.843 WARNING: ..\..\..\..\..\src\sdksource\fileinput\dzassetdaz.cpp(1451): Failed to create alias!

 

The warnings do not appear to be obviously linked to an asset as per usual debug log standards.

If anyone has any information regarding either of these any help would be much appreciated.

Post edited by ForceX on

Comments

  • due to the long load time, it's probably looking for something that isn't there.

     

    Have you tried searching the data folder for the pSadation?

    It's entirely possible it's a typo,within a dsf, and honestly you may never find it.

     

     

  • ForceXForceX Posts: 52
    edited June 2019

    Yah I've run a file search for pSadation, no luck.

    I would love to read the "dzassetdaz.cpp" file. However I have the feeling it's a virtual file only stored in memory. Or sense it's a C++ compiler file, locked away in a DLL somewhere.

    Post edited by ForceX on
  • 3Ddreamer3Ddreamer Posts: 1,312

    Load times have been getting longer and longer - those you have fixed you should feed back to the Developers and see if they can fix them for all of us in the next Beta. I've noticed the log looking for files I don't own on characters I have dialed from scratch :-(

  • Richard HaseltineRichard Haseltine Posts: 102,301

    The listed .cpp files are indeed referecnes to the source files. They tell you which bit of the application is throwing the error.

    How have you been fixing issues? It's quite possible that a fix has in fact broken something.

  • ForceXForceX Posts: 52
    edited June 2019
    3Ddreamer said:

    Load times have been getting longer and longer - those you have fixed you should feed back to the Developers and see if they can fix them for all of us in the next Beta. I've noticed the log looking for files I don't own on characters I have dialed from scratch :-(

    All the fixes were asset related, not DAZ code related. The bulk of fixes were related to duplicate or missing assets. IE having an asset but not having the primary or supporting asset, and properties that were not saved correctly such as a character preset master slider that did not update the head slider only the body, because, reasons. Those were easily fixed by removing the offending property or updating to the correct property (via property editor) and re-saving the asset. The missing refrences were fixed by removing the asset requesting the missing file.

    The listed .cpp files are indeed referecnes to the source files. They tell you which bit of the application is throwing the error.

    How have you been fixing issues? It's quite possible that a fix has in fact broken something.

    Unfortunately, these errors have persisted from the beginning and is the reason why I spent the time attempting to clean up as many errors as possible in hopes of solving these remaining issues that just happen to be the ones taking the bulk of the loading time. See response to 3Ddreamer for how errors were fixed.

    Richard, is it possible to view the .cpp file or export it to a plain text? It would help in hunting down the offending asset.

    Post edited by ForceX on
  • Richard HaseltineRichard Haseltine Posts: 102,301

    No, only Daz has the .cpp files (they are the DS source code, and so they are proprietary information). There are not, I think, that many aliases - it might be possible simply to scan through and find the issue by hand (I assume it's in the base figure with no add-ons installed).

  • ForceXForceX Posts: 52

    Understood. I'll check a clean G8 resource folder and see if the same errors are present. I’m not sure what an alias is or is referring to in regards to DAZ. Scanning the G8F Data\\Morph folder I get a bunch of alias_xxxxx.dsf files. It seems to be a common prefix that content creators use. But without something more descriptive in the Log file I’m not sure where to look. I guess I'll start with the clean G8F first.

  • ForceXForceX Posts: 52

    No supprise, a clean G8F resource folder results in no issues. G8F loads in <= 5 seconds. The hunt continues. At least I know it is an after market asset causing the problem.

  • Richard HaseltineRichard Haseltine Posts: 102,301

    An Alias lets you have the same property ccontroller in multiple places, so that changing any one changes theunderlying property and all other aliases (unlike ERC, where changing a controller chnages the sub-component but not vice-versa). They are used for things like the Bend/Twist bones, so that you can adjust both by selecting only one, and for some of the pose controls, so that you can for exampel control the hands from the hand boen or the figure (I'm not sure whether the bend/twist are aliases or links, though).

  • ForceXForceX Posts: 52

    Ok, thank you for the explanation of Alias, I was unaware of them before.

  • ajh296ajh296 Posts: 1
    edited September 2019

    I recommend Notepad++ -- Search in Files... also for editing change language to JSON, for color and stuff. :P

    This is mispelled.

    In my case I found it in Amira Expressions -> data\DAZ 3D\Genesis 8\Female\Morphs\bluejaunte\Amira Expressions\alias_head_eCTRLAmiraSadHD.dsf : line:19

    pSadation   -> presentation

    Post edited by ajh296 on
  • JD_MortalJD_Mortal Posts: 760
    edited November 2019

    You, sir, are a life-saver... I still have tons of animation errors and the other errors like you mentioned, but that one is shot down now...

    pSadation -> presentation

    Seems to have happened when the person did a "search-and-replace", for the phrase "resent" and replaced it with "Sad".

    pRESENTation -> -[resent] = p_____ation -> +[Sad] = pSADation

    ;P (resent = resented =>?? Sad)

    I guess the emotion was previously "AmiraResentHD". Damn manual editing...

    Post edited by JD_Mortal on
  • DekeSladeDekeSlade Posts: 127

    I hate being stupid but let me see if I can start with what I hope is simple.

    What is meant by "a clean G8F resource folder results in no issues. G8F loads in <= 5 seconds" ... what is that? Isn't just a base G8F?

    Next with this "alias" stuff, what file are you looking at to fix these? Or how do you know which file to fix?

    Sorry for being so green but I think this has been a huge reason I've had issues and am more than a little desperate to find some resolve, or at least hope for a resolve. Thanks.

    - pxlzXppl

  • Catherine3678abCatherine3678ab Posts: 8,384
    edited March 2020
    pxlzXppl said:

    I hate being stupid but let me see if I can start with what I hope is simple.

    What is meant by "a clean G8F resource folder results in no issues. G8F loads in <= 5 seconds" ... what is that? Isn't just a base G8F?

    Next with this "alias" stuff, what file are you looking at to fix these? Or how do you know which file to fix?

    Sorry for being so green but I think this has been a huge reason I've had issues and am more than a little desperate to find some resolve, or at least hope for a resolve. Thanks.

    - pxlzXppl

    Not speaking for what others have said as to what they meant. For myself a clean G8F resource folder means [close D/S] digging into the data folders: data\DAZ 3D\Genesis 8\Female\Morphs\ ... and removing [slide to a folder on the desktop or someplace where you can find it but D/S won't] all save those that are made by the company DAZ3D. Close that folder, open D/S, clear the log file, load a figure, check the log file.

    Then close D/S, go back to the data folder and slide back in ONE of the morph folders that had been removed. Close the folder, open D/S, clear the log file, load the figure, check the log file.

    Wash, rince, repeat until the log file shows the problem. THEN you have indentified the morph that causes the error message or the long load times or whatever.

    n.b. sometimes just by reading the log file the offending morph can be discovered.

    n.b. for some bizarre reason yes we are getting a lot of error messages which for the most part for the enduser can be ignored. They don't [normally, drastically] affect load times - the more morphs any figure has, the longer the figure will take to load BUT AFAIK [as far as I know] the load time should be in the seconds or minutes and seconds, NOT hours.

    A number of error messages can be had by morphs seeking control morphs or vice versa which not everybody has.

    Post edited by Catherine3678ab on
  • maw3dartmaw3dart Posts: 1
    edited April 2020

     

    pxlzXppl said:
    n.b. for some bizarre reason yes we are getting a lot of error messages which for the most part for the enduser can be ignored. They don't [normally, drastically] affect load times - the more morphs any figure has, the longer the figure will take to load BUT AFAIK [as far as I know] the load time should be in the seconds or minutes and seconds, NOT hours.

    Heck, first time writing a post in the DAZ forums :-)
    Just stumbled across this one - so I am NOT the only one having this problem that G8F has loading times up to 20 mins?! I have tried to locate and minimize the reasons as well and also followed up the progression of what exactly is happening using the Process Monitor from the SysInternals, but because of that I also have the feeling that sometimes DAZ Studio is just "hanging around" doing nothing at all like a brick in the memory and then starts working again.
    (during the time I wrote this post I loaded up G8F - loading time 17 mins and 9.4 seconds) ;-(

    Post edited by maw3dart on
  • maw3dart said:

     

    pxlzXppl said:
    n.b. for some bizarre reason yes we are getting a lot of error messages which for the most part for the enduser can be ignored. They don't [normally, drastically] affect load times - the more morphs any figure has, the longer the figure will take to load BUT AFAIK [as far as I know] the load time should be in the seconds or minutes and seconds, NOT hours.

    Heck, first time writing a post in the DAZ forums :-)
    Just stumbled across this one - so I am NOT the only one having this problem that G8F has loading times up to 20 mins?! I have tried to locate and minimize the reasons as well and also followed up the progression of what exactly is happening using the Process Monitor from the SysInternals, but because of that I also have the feeling that sometimes DAZ Studio is just "hanging around" doing nothing at all like a brick in the memory and then starts working again.
    (during the time I wrote this post I loaded up G8F - loading time 17 mins and 9.4 seconds) ;-(

    If it's taking that long check your log file.  You can get there via Main Menu -> Help -> View Log...

    Check for various problems with duplicate or missing products and try to resolve them.  I wish I could be of more help in how to resolve them, but I'm not qualified to give that advice.  The things I've done tend to do as much harm as good, so listen to others. :-)

    If you've bought Auto Face Enhancer be aware there were some issues that seriously increased load times.  The problems were suppose to have been fixed but check the product's thread over here to see more.

  • Silver DolphinSilver Dolphin Posts: 1,614

    Sounds like we need a nuclear option script!!! Destroy ofending folder and reinstall. Install errors what a pain.

  • BejaymacBejaymac Posts: 1,897

    Sounds like we need a nuclear option script!!! Destroy ofending folder and reinstall. Install errors what a pain.

    Doesn't have anything to do with install errors, the problem is that a product (or two) they have installed has ERC links that are looking for files in products they don't have installed and probably don't even own.

    Some of them might be due to pathway/file name/property name changes after the ERC link was made, but those are rare to find.

Sign In or Register to comment.