Drop Down Menu Messed up

I have DS 4.8, Somewhere along the line, the dropdown menu for the Content Library tab got messed up.  There is only one divider line at the top, and the menu items are now scattered in different order. I have tried all kids of things in the work space, the style, etc, but I can't find anything to set this back to default.  Any suggestions besides delete and reinstall? Thanks.

Comments

  • This is a screen shot of the issue

    Context menu.jpg
    300 x 458 - 61K
  • ChoholeChohole Posts: 33,604

    Run the Update and Merge Menus script

  • Thank you for the answer. Where do I find that? I looked at all the top menus and didn't see anything that said either Update or Merge Menus. What am I missing?

  • ChoholeChohole Posts: 33,604

    DAZ Studio Formats>My DAZ 3d Library>Scripts>Utilities   ....     assuming you use the default My DAZ 3d Library for content

  • Found it, ran it but it failed, the log returned this:  

    Loading script: C:/Users/Tiffanie/Documents/My DAZ 3D Library/Scripts/Utilities/Update and Merge Menus.dse
    Failed to load script: C:/Users/Tiffanie/Documents/My DAZ 3D Library/Scripts/Utilities/Update and Merge Menus.dse

    So, it's broken.

  • If iI re-installed 4.8 over this installation, would it likely fix it without killing my content Library modifications?

  • ChoholeChohole Posts: 33,604

    Passing your problem over to a colleaugue (or two) who know far more than I do. They said :-  That sounds like a version mis-match - a binary script (compressed .dsb or, as here, encrypted .dse) will not run if the version of DS it was saved from is newer than the version being run.

    Hang on in there. Someone will be back to you hopefully.

  • If you have updated the Default Resources package more recently than your copy of Daz Studio then the script will be a newer version and will not run, as Cholhole explained above.

    Updating DS will not break your existing content (though moving from 4.8.x to 4.9.x  you should back up your database as insurance - go to the Content Library option menu, the lined button in the top corner, seelct Content DB Maintenance, and check Export User Data then click Accept). If you are still using the old Valentina database you will need to install PostgreSQL and run the Convert Valentina to PostgreSQL tool (it appears in DIM - instaling it is actually running the converter). You can check which database you are using either by going to Edit>Preferences and looking to see if there is a CMS Settings tab to the right (probably partially hidden by the dialogue frame) or by looking in Task Manager to see if there are several isntances of PostgreSQL in Processes while DS is running.

  • I Have 9 instances of PostgreSQL running. But I was pretty sure I only had that one running, I converted from the Valentina a long time ago. So, back up the User Data and then reinstall?

  • mjc1016mjc1016 Posts: 15,001

    I Have 9 instances of PostgreSQL running. But I was pretty sure I only had that one running, I converted from the Valentina a long time ago. So, back up the User Data and then reinstall?

    No, multiple instances of Postgre is perfectly normal.

  • If iI re-installed 4.8 over this installation, would it likely fix it without killing my content Library modifications?

    It probably won't make any difference — reinstalling D|S will not affect your Content Library setup because it's held in a separate setup file which is not overwritten by reinstalling. Unfortunately, exactly the same thing happens with whatever went wrong with your menus; when you reinstall, they'll still look exactly the same because D|S is reading the same independent setup file.

    I used to have a similar problem several months back, most of my menus were displaying backwards due to a corrupted setup file. I'll try to find the forum thread where I discussed how I fixed it.

  • Thanks for the help. I ended up opening my 4.9 version (which was also messed up) and ran the script there (I had tried the reinstall 4.8 with the same issue afterwards, just like SpottedKitty said) the script fixed the issue in 4.9, so when I reopened 4.8, it was fixed there, too.  So, thanks, by combining the various answers from everyone I was able to fix it!

Sign In or Register to comment.