VexingHeadache: where are all Daz-user Associations Stored?
![Saxa -- SD](https://farnsworth-prod.uc.r.appspot.com/forums/uploads/userpics/987/nXJJ25YVCJEPV.jpg)
Need Help please.
This is a bit complicated to explain. Please bear with me.
In a nutshell: Was working with geoshells and geografts in Public 4.12.0.86 and an existing geograft working product got "wacked". Say whacked because there is some artifical extra surface mat, like a ghost, or 2nd one affecting the main product. Think it got baked in somehow (though I didn't save that geograft itself.)
But, I can still see product work as intended in DazStudio Beta 4.12.1.86 (which have not been using).
To start maybe could ask: Where are changes for associations per DazStudio Version like Saved scenes and new ERCs and morphs stored or recorded?
What I mean is, am looking for where is the cache for one DazStudio version stored (like 4.12.0.86 VERSUS another version like 4.12.1.40)?
Things like ERCs, new saved scenes and such are not necessarily auto-associated to other Daz Studio version.
For saved scene when you switch over to other DS version, I first have to go through open submenu and manually point it. That is even though I have both versions sharing same directory always.
For morphs in new directory structures (maybe even existing?) you need to add somehow to get into other version. In 4.12.0.86 where I added them, they are always instandtly there with each new session. With 4.12.1.86 will probably to publish. Hadn't got that far yet.
Am focussed on this issue instead.
More Importantly, in the case of my Daz-headache, I know this is a "cache" related issue because:
I can Iray preview the exact same saved scene in the Beta 4.12.1.40 and the product works as it should. Luckily had not been using Beta. So i got this clue.
Reload a 2nd session with Beta and issue is still not there, so good thing is it's not auto updating from the Public version.
Save that good scene, open in Public and issue is back. So it has to be a deep-seated cache thing, and not the dufs or saved scene.
Very important to note. This "change" is just like the ERCs, morphs and scenes I made in 4.12.0.86. None of those are automatically updated or shown in Beta 4.12.1.40 either. And they say morphs are missing when load the scene in 4.12.1.40, which were made and used in 4.12.0.86.
>>>>Was guessing it is all stored in CMS - sorted and separated by Studio Versions? But apparently that's not it either.
>>>>Already did two resets of CMS/and re-import Metadata. Not lucky. 2nd time I just deleted the whole CMS directory and it updated meta-data on it's own. Issue still there. so loaded saved scene into Beta, and again geograft previews properly (and still gives me errors about my new morphs in a new folder - both those morphs have nothing to do with this geograft)
>>>>>Before that cleared both temp and DSON (deleted and let it auto-generate) and that did not fix my issue.
Am a bit bewildered why I can't find why Beta vs Public iray-preview the identical saved scene very differently all of a sudden. Has been working fine for months as intended in both versions. As I say my changes were working on geografts/geoshells. What I had installed for bought stuff, I already uninstalled too. Plus new content isn't really viable cos it doesn't explain why it works in Beta.
Any ideas where to look?
Comments
I'm really not sure what you are asking. The DSON cache is set in Edit>Preferences, but I'm not sure that is relevant. I'm not sure what you mean by "both versions sharing same directory always" - is that the (or a) content directory?
Yes!! I fixed it!
@RichardHaseltine
You won't believe what the issue was LOL!
In Public 4.12.0.86,
I had made a new root directory for all my morph work and added it to the ContentLibrary>Content Directory Manager> Current Directories>Daz Studio Formats>(mynewrootfolder).
Do this for my 3rd party stuff and some of other own stuff to keep things separate and clear.
So this is where my new body morphs were stored. Had done that weeks ago before this issue suddenly appeared (this fact added to my confusion alot)
What I did NOT do yet was update the ContentLibrary in Beta 4.12.1.86 with this new root folder for content.
Which is why it didn't know the morphs existed.
While figuring this all out, I added the morphs into Beta to see if it would trigger my issue.
Morphs showed up and issue still not showing up in Beta. I was still confused.
So went back into Public 4.12.0.86 and you know what?
The geograft was working properly again! And that's after 2 days and 3 PC shutdowns and many new this and that. So the fix was definately adding the moprh directory to Content Management.
Only Conclusion can offer.
By having the moprhs recognized in one version and not the other DS version, there was some shift in the CMS data occurring? Maybe a wierd averaging? No idea.
But funny enough the version that didn't know about the morphs worked fine,
and the one that did have the moprhs recognized and working had that ghosted appearance.
And why did the issue appear all of a sudden after working for weeks with my new morphs without issue?
Glad it is fixed. Just confused why that was the fix.
On the Plus side, my DazStudio is way faster and snappier having rebuilt the CMS from scratch.
Think will do that now every +500 products added.
An update to finish what I started with this OP.
Had issue appear 2 more times.
Issue arises when using geografts & Figure with GeomEditor in a certain way.
Certain actions trigger "breaking" the geograft and the fix is a bit odd. But that's another story.
My question in the OP was about where are all the associations stored for DazStudio.
Idea was to reset or clear bad associations.
In this case, repeated several times
(1) rebuilding CMS
(2) clear DSON cache
(3) clear Temp.
None of those things fixed this issue.
And the issue is 100% for sure limited to the one installed DS version.
Beta, which I currently don't use, worked fine each time after 4.12.0.86 got the "issue".
Instead, Had to figure out what cause it and how to manually reset/update in Daz Studio.
So to conclude my adventures, I still don't know where DAZ Studio stores all of it's changes.
Perhaps this "breaking of the geograft" is saved alongside workspace changes? Don't mean the manual save of my preferred layout. Mean DS auto-save so it remembers certain settings.
If anyone knows where this information is stored or parsed, would be nice to know. Thanks.