Missing Assets - Starter Essentials

Leonides02Leonides02 Posts: 1,379
edited December 2019 in The Commons

Hi All,

Hoping for a bit of help. I'm suddenly having a very irritating issue. For every scene I open, I'm receiving this error: 

 

This prevents the scene from opening unless I click either "Install Selected" or "Skip."

I've "Installed" many times. I've also uninstalled via DIM, and re-installed. 

This error is also occurring with Genesis 3, and happened with "Glute Control" as well. 

Anybody have any idea what's going on? 

 

P.S. I have opened a help ticket, but I suspect the Daz folks are taking a well-deserved holiday rest.

 

 

Post edited by Leonides02 on

Comments

  • Do the products show as installed (colured thumbnail) in the Products tab of Smart Content when you start DS, before trying to install them again?

  • Leonides02Leonides02 Posts: 1,379

    Do the products show as installed (colured thumbnail) in the Products tab of Smart Content when you start DS, before trying to install them again?

    Thanks for the reply, Richard.

    I can't click out of the box without slecting either "Install Selected" or "Skip."

    But if I click on "Skip" the content looks exactly as it should in Smart Content:

  • How about when you open DS, before loading the figure - or is th figure set to load with DS? If so you could try turning that off temporarily in the Edit>Preferences pane and restart DS?

  • Leonides02Leonides02 Posts: 1,379

    Hi Richard -

    Yes, if I open a blank Daz scene, the thumbnail is colored in and accessible (i.e., I can load a base G8 figure).

  • duckbombduckbomb Posts: 585

    This happens to me, as well, with both this and the female expression auto-enhancer one.  It sucks, because it pauses my render queue and I have to keep manually checking.

    I can confirm the same exact behavior as described above, and that for all intents and purposes the packages look to be installed correctly.  The strange thing is that I recently just built up a new computer, and the behavior "moved" from that one to this one.  I built up the library through DIM, and uninstalling/reinstalling doesn't fix it.  It's weird

  • Leonides02Leonides02 Posts: 1,379
    edited December 2019

    double post

    Post edited by Leonides02 on
  • Leonides02Leonides02 Posts: 1,379
    edited December 2019
    duckbomb said:

    This happens to me, as well, with both this and the female expression auto-enhancer one.  It sucks, because it pauses my render queue and I have to keep manually checking.

    I can confirm the same exact behavior as described above, and that for all intents and purposes the packages look to be installed correctly.  

     

    Thanks for confirming I'm not going crazy, duckbomb.

    And you know what? It happens on AutoFace Enhancer for me, too!!! I opened a ticket for that one awhile back, but it wasn't repeatable. It happened in some files, but not others. Same thing with this... One scene I'll open with a G8 and I get the error, in another I don't. Seems random.

    And the render queue is the exact reason I find this troubling.

     

    The strange thing is that I recently just built up a new computer, and the behavior "moved" from that one to this one.  I built up the library through DIM, and uninstalling/reinstalling doesn't fix it.  It's weird

     

    Well, shoot. I was hoping a total re-install might fix the issue. There must be something weird happening with the Metadata?

     

    Post edited by Leonides02 on
  • duckbombduckbomb Posts: 585

    If it's you and me, it has to be others. I'm only on a "pit stop" build, as I'm gonna be moving to a new drive, and was going to mess around with it more, then.  I agree with what you said about it seeming to be random.  The AFE one pops up in scenes where I never used it, and other times doesn't even when I know I have.

    i won't be back in town until next week, so I won't be much help until then, but if they get back to you I'd be interested to know what the fix is.

    if they don't, I'll try my own troubleshooting now that I know it's not just me.  Honestly, I had thought I just screwed something up, so it's encouraging to know it's replicatable.  That means it's fixable.

  • Leonides02Leonides02 Posts: 1,379
    duckbomb said:

    If it's you and me, it has to be others. I'm only on a "pit stop" build, as I'm gonna be moving to a new drive, and was going to mess around with it more, then.  I agree with what you said about it seeming to be random.  The AFE one pops up in scenes where I never used it, and other times doesn't even when I know I have.

    i won't be back in town until next week, so I won't be much help until then, but if they get back to you I'd be interested to know what the fix is.

    if they don't, I'll try my own troubleshooting now that I know it's not just me.  Honestly, I had thought I just screwed something up, so it's encouraging to know it's replicatable.  That means it's fixable.

    Thanks and likewise! 

     

  • Leonides02Leonides02 Posts: 1,379

    duckbomb and Richard Haseltine, just a new discovery:

    If I click "Install" and then save the scene, the error doesn't appear again for that scene even if I save it under a different name. 

    Very strange!

  • duckbombduckbomb Posts: 585

    Wow!  Really!  Oh that's exciting!  Not a fix, but a workaround for sure.  I know I've done the install, though, and saved it before closing out, and I've still gotten the pop up down the road, but perhaps saving it right after install makes it better.

    I also felt rebooting the machine caused it to come back, but not every time.

    Thank you, I'm excited to try this out!

  • Leonides02Leonides02 Posts: 1,379

    Another odd thing...

    I've noticed I need to do this seperately for both the regular 4.12 and the Beta. 

    The "fix" doesn't seem to carry over between the versions.

  • Leonides02Leonides02 Posts: 1,379
    edited May 2021

    This problem is happening agin.

    Anyone else and have you found a solution?

    (reinstalling doesn't work)

    Post edited by Leonides02 on
  • BejaymacBejaymac Posts: 1,897

    Simple fact that the error is showing starter essentials, tells me that you have a corrupt database/metadata.

    The scene DUF file doesn't have a clue what products it needs to load, instead it will just have pathways to DSF files in the data folder.

  • PerttiAPerttiA Posts: 10,024

    I think mis-configured content libraries

  • ZippyGuitarZippyGuitar Posts: 849
    Ah, I've tried figuring out the 'why's' since it started happening to me about a year and a half /2 years ago. I 'think' it began shortly after installing the DS 4.12 Beta but had to take it back off due to the increased iRay requirements. I'm almost certain there was also a G3&G8 update some time after that. The only time I might get these errors is using the Timeline to drape using dForce. Close Daz, open the same scene with the Timeline usage and I'm likely to get the warning. I always skip and never get the warning again from the same scene. If I drape just using the Current Frame and no Timeline, I never get the warning. It's annoying as hell, but does not impact the scene/characters at all except the slight delay in load times.
  • Leonides02Leonides02 Posts: 1,379

    Bejaymac said:

    Simple fact that the error is showing starter essentials, tells me that you have a corrupt database/metadata.

    The scene DUF file doesn't have a clue what products it needs to load, instead it will just have pathways to DSF files in the data folder.

    That seems likely. I have uninstalled and re-installed the Starter essentials, to no avail. Any suggestion on how this might be fixed?

     

  • Leonides02Leonides02 Posts: 1,379

    GlenWebb said:

    Ah, I've tried figuring out the 'why's' since it started happening to me about a year and a half /2 years ago. I 'think' it began shortly after installing the DS 4.12 Beta but had to take it back off due to the increased iRay requirements. I'm almost certain there was also a G3&G8 update some time after that. The only time I might get these errors is using the Timeline to drape using dForce. Close Daz, open the same scene with the Timeline usage and I'm likely to get the warning. I always skip and never get the warning again from the same scene. If I drape just using the Current Frame and no Timeline, I never get the warning. It's annoying as hell, but does not impact the scene/characters at all except the slight delay in load times.

    Glad I'm not the only one!

    When this impact me the most is when I'm using ManFriday's RenderQueue. It stops the whole render train.

  • PerttiAPerttiA Posts: 10,024

    There is no general fix.

    If you have installed the Starter Essentials and DS is complaining that it is missing, the installation has been done incorrectly or your database is corrupt.

    As we can not see, how your DS is set up, we have nothing to go on.

Sign In or Register to comment.