Loading...
> >

Files not found after updating

Reality1Reality1 Posts: 115
in Daz Studio Discussion

When opening some of my projects created in an earlier version of Studio, 4.21 is not finding them in the mapped content folders.

Additionally, when I manually locate and reconnect them, it acts like it found them and then when the project loads up it lists all the reconnected files, saying they were not found.

Any think I can do about this?

Comments

  • Richard HaseltineRichard Haseltine Posts: 100,765

    That sounds as if the paths have changed - either the actual paths on disc or the ones stored in DS. If you installed through Connect (through Daz Studio itself) it may also be a database issue.

  • Reality1Reality1 Posts: 115
    edited August 2023

    Richard Haseltine said:

    That sounds as if the paths have changed - either the actual paths on disc or the ones stored in DS. If you installed through Connect (through Daz Studio itself) it may also be a database issue.

    The projects opened fine in 4.15 and still do in the public beta I'm using from a year ago.

    Studio doesn't usually complain when files are moved as long as they stil in the content tree, and from there the paths are the same.

    The more concerning thing is that it can't seem to reconnect them, even when I locate them manually.
     

    Post edited by Reality1 on
  • Richard HaseltineRichard Haseltine Posts: 100,765

    What are the content diectory settings in the two versions of DS?

  • barbultbarbult Posts: 24,240

    Could this be one of those //runtime issues? Daz Studio used to accept the error of //runtime in paths, but later Daz Studio versions do not accept that error; They demand only /runtime.

  • Richard HaseltineRichard Haseltine Posts: 100,765
    edited August 2023

    barbult said:

    Could this be one of those //runtime issues? Daz Studio used to accept the error of //runtime in paths, but later Daz Studio versions do not accept that error; They demand only /runtime.

    That is possible, I thought there was a rference to the beta though - which would have the same issue, as far as I know. Edit, from a year ago - that might just be old enough not to be affected.

    Post edited by Richard Haseltine on
  • Reality1Reality1 Posts: 115

    Richard Haseltine said:

    barbult said:

    Could this be one of those //runtime issues? Daz Studio used to accept the error of //runtime in paths, but later Daz Studio versions do not accept that error; They demand only /runtime.

    That is possible, I thought there was a rference to the beta though - which would have the same issue, as far as I know. Edit, from a year ago - that might just be old enough not to be affected.

    Sorry I didn't reply right away, busy with other things. Here's what I know so far:

    This is when I updated to 4.21 from a previous release, not from the beta. The beta I have installed in parallel opened the same projects before and after without a hitch. There was a brief splash screen from the intaller saying it was repairing something? 

    I don't use Connect, I use DIM and really like it.

    I checked the content folder tree in DS in the new install and while it was still there, the one with the missing textures it was busted- appeared to be empty in DS. So I removed it and added it back. This fixed the missing textures, but the HDRI dome file was not found. 4.21 is also not looking in the local directory for some reason.

    Four glitches total if you include the broken locate feature when it doesn't reconnect the missing files when located manually.

    None to difficult for customers to compensate for, but better to be fixed in the code, IMO.

    Thanks!

    -JB

  • Richard HaseltineRichard Haseltine Posts: 100,765

    You shouldn't see the folder with the textures in DS, let alone the textures themselves, if that is what you mean.

  • Reality1Reality1 Posts: 115

    Richard Haseltine said:

    You shouldn't see the folder with the textures in DS, let alone the textures themselves, if that is what you mean.

    That's not what I said. The content folder also contains runtime/textures where my custom textures also reside. The content folder itself, that aslo contains the custom textures, appears empty unless I remove it and re-add it.

    I just discovered that this does not survive a restart of studio. It looks like a database corruption of some sort. 

    I've tried deleting all folders from the DS and Poser trees and restarting studio, and it restarts with the same folders, including the one that's empty until I re-add it.

    Is there a way to get studio to flush and rebuild the database?

     frown
     

  • Richard HaseltineRichard Haseltine Posts: 100,765

    The Content Library pane>Daz Studio Formats is not, other than the Daz Connect virtual folder, dependant on the database for file listing (it does use the database for things like the content type tags, of course).

  • Reality1Reality1 Posts: 115
    edited August 2023

    Richard Haseltine said:

    The Content Library pane>Daz Studio Formats is not, other than the Daz Connect virtual folder, dependant on the database for file listing (it does use the database for things like the content type tags, of course).

    Hmmm.

    Is the content directory list stored in a registry entry or an ini file that can be deleted manually?

     

    Post edited by Reality1 on
  • felisfelis Posts: 4,309
    edited August 2023

    The content library is based on the actual files there are in that library, i.e. what DS can read from the desk.

    Post edited by felis on
  • Reality1Reality1 Posts: 115

    felis said:

    The content library is based on the actual files there are in that library, i.e. what DS can read from the desk.

    When you add a directory to the content library, that information must be stored somewhere, and wherever that is has become corrupted, or studio isn't updating it for some reason.

    Read the thread above.

  • Richard HaseltineRichard Haseltine Posts: 100,765

    Reality1 said:

    felis said:

    The content library is based on the actual files there are in that library, i.e. what DS can read from the desk.

    When you add a directory to the content library, that information must be stored somewhere, and wherever that is has become corrupted, or studio isn't updating it for some reason.

    Read the thread above.

    That sounds more like the drive sleeping until activated. What happens if you right-click on the content Diectory name and select Refresh?

  • PerttiAPerttiA Posts: 10,024

    Richard has a point, one should not let drives go to sleep, ever.

    On the other hand, you haven't told us, where your content directories are located (the full path for all of them, starting from the drive letter)
    The base folder of the content libraries are specified and stored in Content Directory Manager

  • Reality1Reality1 Posts: 115
    edited August 2023
    Richard Haseltine said:

    Reality1 said:

    felis said:

    The content library is based on the actual files there are in that library, i.e. what DS can read from the desk.

    When you add a directory to the content library, that information must be stored somewhere, and wherever that is has become corrupted, or studio isn't updating it for some reason.

    Read the thread above.

    That sounds more like the drive sleeping until activated. What happens if you right-click on the content Diectory name and select Refresh?

    That's one of the first things I tried. And giving you the details about which directory is irrelevant. It works fine with the public build, and it worked fine before I did the update. If you could tell me if there's a way to delete that information manually (the information studio is storing about the content directories) that might take care of it. I've already tried uninstalling completely, deleting the directory in the roaming folder, and the application folder in the program files directory. That didn't work directory still comes back broken. Even though that directory mapped exactly the same way is working fine in the public beta, and worked fine before I did the update.
    Post edited by Reality1 on
  • Richard HaseltineRichard Haseltine Posts: 100,765

    Edit>Prefrences, go to the Content tab, and seelct Content Directory Manager.

  • Reality1Reality1 Posts: 115

    Richard Haseltine said:

    Edit>Prefrences, go to the Content tab, and seelct Content Directory Manager.

    I had a chance to work with it again, and same behavoir when working with the Content Directory Manager. I even created a new content set with alternate directories, and no dice.

    In addition none of the interface preferences such as tabs, last content directory used, or recent files are being stored on exit.  When Studio starts up, it's locked in the former state that even survives a reinstall.

    Anyone know where is this preference information being stored so I can manually remove the file or database?

  • Richard HaseltineRichard Haseltine Posts: 100,765

    What security software are you using? Are you allowing Daz Studio to close itself or are you force quitting?

  • Reality1Reality1 Posts: 115
    edited September 2023

    Richard Haseltine said:

    What security software are you using? Are you allowing Daz Studio to close itself or are you force quitting?

    Studio is quitting normally as far as I can tell. The process does hang in the background for a while before exiting completely, but this isn't new.

    Windows firewall is on but, there is no special security software. Defender isn't set for active scanning.

    I reinstalled windows on a clean drive and reinstalled Studio and it's working normally with the clean install, so it's not the hardware. It may be that Windows 8.1 install is corrupted in some way.

    I'd still like to try manually deleting the preference files if you know where they are because reinstalling all the other software is a chore.

    Post edited by Reality1 on
  • Richard HaseltineRichard Haseltine Posts: 100,765

    Most settings are in %appdata%/daz 3d/studio4/ but not the content directories or serial numbers, I suspect those are in the Registry.

Sign In or Register to comment.