Repair Feature for DAZ Install Manager
Ohgun the Awakened Prodigy
Posts: 21
Today has been a very awful day when it comes to working with metadata in DAZ Studio and some of the products I've been using lately. Because of this, I would like to suggest a repair feature that can help fix broken files, metadata, and even databases of content downloaded through the Instal Manager. I think that file integrity is an essential component of functional databases and programs, and that is why I made this suggestion.
Post edited by Ohgun the Awakened Prodigy on
Daz 3D is part of 
Connect
DAZ Productions, Inc.
7533 S Center View Ct #4664
West Jordan, UT 84084
Licensing Agreement | Terms of Service | Privacy Policy | EULA
© 2024 Daz Productions Inc. All Rights Reserved.
Comments
Sort of related I would like to propose that the bloke writing the conversion scripts when updating the Daz Studio with newer versions of PostgreSQL gets sent on a course to learn what he is doing. Daz2.3 to 4.7 no problems. Going to 4.8 had to convert Valentina. The script does not work in one go. I have to break my content database into sections, convert in smaller chunks, join it back together and check for any errors. 3 months later I'm back in business with PostgreSQL. Hurrah. Then Daz4.9.1 comes along. Another conversion needed. Same story. Three weeks later fixed. Earlier experience helped. Then 4.9.2 conversion script bombs out with duplicate keys found in the database. I file a bug report but nobody addresses the issues found in the log.txt file. I get a series of e-mails detailing common faults which have no bearing on the actual problem. Yes if you erase your content management DS 4.9.2 will work. Hardly surprising but no use to anyone. Need a script writer not a general computer admin type. Agree to wait till next upgrade.
What makes me cross is that none of this was necessary. Users had no desire for the product centred 4.9 or Daz Connect. I don't like DRM but I might tolerate it if it worked, but it doesn't. Daz Studio has had loads of new features successfully applied but every time Daz touches the content management system things go wrong. Having to spend hours fixing things until next upgrade is not a hobby of mine. If you are going to mess with the content database learn what you are doing or stay well clear. When you have around 8000 products you can't recreate the categories in any sensible time frame. As a user of 8 years I need backward compatabilty. If I don't get that I have to give up. I've spent thousands of dollars on your products. Daz play fair.
I frequently have issues with the database or cntent getting installed and then not finding it in product view and having to reimport metadata for each item. This has happened since 4.8-9 I also find that daz studio frequently insists on installing on c drive even putting content there even though e is selected. In the age of having multiple drives installed many manufacturers are making c a solid state drive. I want my stuff to install where I want not where studio wants to put it
What conversion utility? You should run the valentina to PostgreSQL conversion tool only once - though if the valentina database is on the verge of corruption (and its vulnerability was one of the big reasons for switching to PostgreSQL) then the process might not succeed. In any event, exporting user data from the Content DB Maintenace dialogue should give you a back up that you can reimport - see the Content Library pane option menu, the lined button in the top corner or right-click the tab.
To set the location for DIM to install to go to Settings > Installation, and make sure the Current path is the correct location -- you can also tick the "Show More" box at the bottom of the "Ready To Install" tab to ake sure it has the correct path before you install anything. To set the location for Connect to install go to Edit > Preferences > Content Library > Content Directory Manager and make sure the "Daz Connect Data" path is correct.
What should happen and what actually happened are two different things. I was willing to keep an open mind about Valentina database corruption at the time even though I had never experienced any corruption. Then the same thing happened with Postgre SQL going to 4.9.1. Again never experienced corruption and unlikely to have occurred within a few months on 4 separate PCs. The fact the conversion process worked with smaller chunks rather than doing it all in one go suggests it wasn't corruption but some size limitation of the script. I don't doubt that the scripts work with most users. As long as the problem is something that the admins can solve on the forums you get a quick response. Bug reports are a different matter and I've never had one solved yet. I think that is because the programmers would rather work on the next upgrade than look back and work out why their existing works dont work. Normally I'd go along with that as a more efficient use of resources but when the same type of problem occurs three times in one year you begin to lose faith that its worth it.
Still at least 2 other users are getting the same problem and the log.txt error message is very specific so it should be easy to diagnose. We will see what happens in the next upgrade beyond 4.9.2.70. My problem and log.txt file looks exactly the same as http://www.daz3d.com/forums/discussion/89536/4-9-2-updating-cms-takes-too-long-to-load#latest. Imagine what would happen if everytime Microsoft Windows was updated your existing programs didn't work and you had to start from scratch. Backwards compatability is very important to existing users but when you think of loss of poser compatability and the closure of Artzone maybe not Daz's strongest suit. Probably the thing that users beef about the most.
Did you contact support as DAZ_Rawb suggested in that thread?
Yes