The textures and morphs that are really there I swear
spearcarrier
Posts: 686
DAZ has cropped up a new weird problem, and it's... seriously put my work flow to a halt.
When I try to load a custom character, it tells me that textures and morphs aren't where they're supposed to be. I seem to recall when this happened before it would ask me to find them and I would, and all would be well. It doesn't do that anymore (which is a big issue) and... well.... I go to the places the items are supposed to be and lo. There they are. So DAZ is just ignoring them.
Is this a bug? Should I open a ticket? Definitely roll back to a version that didn't do this cuz not getting work done is a serious issue?
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
There was a bug which wouldn't ask you to find the textures in an earlier version, but that shouldn't happen in the latest. What's the full path (i.e. starting from the drive letter) of an item which isn't being found?
Can you go to Edit > Preferences > Content Library > Content Directory Manager, expand the "DAZ Studio Formats" and "Poser Formats", and post a screenshot?
I'll try to do that, yes. In the meantime I'm trying a database reset. Another thing that has cropped up are dozens and dozens of "orphan file" references when there never were before. I even told it to do a new library scan, which I do often because I manually move things around.
Well none of that helped. The library is pointing to the correct place- a place I've been using for years and was working well with just last week. I only just installed the latest version of DAZ a couple of days ago and this is the first time I've tried to create a fresh file with it. Not liking it so far.
So bug? Not bug? Support ticket? No? Easy answer to be had with someone who knows? (Please dont' tell me to change my directory path. I'll assume then it's a bug and not do it.)
Aaaand its fixed. So weird.
I wouldn't call my libraries "Runtime" as that could confuddle the computer, remember they are just trumped up calculators and dumber than a lump of silicon.
I did that because I'm also running poser, and that simplifies a lot of things. And hey, remember when I said I'd been doing that for years with no problems? :-p Bwahahahah. My runtime library is on a separate hard drive for a reason.
What is likely happening is that the Studio format is running into a 'nesting' problem...
You probably have a X:/Runtime/data, X;/Runtime/<other Studio folders> and an X:/Runtime/Runtime <<<<< and THAT is the problem!
Maybe. I've checked, though, because I've been cleaning the mess of the library and don't have anything like that. I have no explanation! I'll just go with yours. Sounds good.