Why no cancel option?
alan bard newcomer
Posts: 2,151
At times it's not worth locating or doing anything with a file that has missing links (simplier just to start a fresh scene) ... so why can this load just not be canceled? Killed dead in the water?
I can do it with the task manager. but then have to restart daz.
--
And the install files button doesn't say "Connect Install missing files"
Since I don't have my daz logged in I didn't have to cancel a connect download when I decided to "install missing files"
---
So the whole missing files window is let us use connect to install them?
It would be nice to have the option of having dim install them.
why no cancel.jpg
2309 x 1125 - 232K
Comments
Daz Connect is, among other things, a way for daz Studio to know about products and to be able to spot the missing product when a fiel cannot be found and offer to install it. Daz Studio and Install manager are not connected in a way that allows DS to identify a product from the file name without having the metadata from connecting to Daz (DIM would have to search each Zip for the relative path in the manifest, which would be very slow - slower than filtering by relative path in the isntalled tab, where it has direct access to the manifests).
thanks
Okay... and I did figure out in some case involving morphs it's my using riversofts morph loading system.
Which does have a work around... put the scene files in a daz directory and click on the file and then the enable morphs button in the riversoft menu.
---
But this does remind me... when DIm starts it retraces the paths?
so that even old scene will be linked to new locations of the directories
Seeing as I blew out the 3tb drive and to move some folders to another drive.
----
I am not sure what you mean here.
I think this image helps explain.
13 products didn't show up in the programs first check to open the scene, usually when this happens you're going to have a scene with many gray boxes and it also means more than one missplaced texture. In this case 5 or 6 directories were listed as being on E in the content directory manager when they were really still on G.
So once you get this screen at the start of a scene load
1) you can try to locate each file one at a time
2) you can let the entire scene be loaded and admire the lack of what you thought you would have.
What we don't seem to have is option 3 which would be "Daz cancel this right now" don't load anything just consider it's time to load a new scene instead of spending time trying to fix this one.
The first image shows us where the problems are but then we're still stuck to load it and attempt to fix it one at a time or when it's loaded and unusable. at that point we say "new scene". Would just like the ability to say "whoops ... I shouldn't have starting loading this... can we stop and start over" without going through the entire scene load.
I know I've done 20 to 30 thousand renders that's given me a lot of chances to go "oh xxx, why did I do that?" and then sit out the load of the stuff I don't want" or just use the task manager to kill Daz but that means I still have to sit through all the start up stuff over again.
If you ever saved any properties from those assets but then these products were uninstalled no matter from Daz Connect or Daz Library, you would see this dialogue ~~
You can open your scene file with Notepad++ to dbl-check if you have such a case ~~~
This was a simple one... the directory list in DIM said E when the products were in G ...
the error message could have said "hey stupid... the relative path for this item is drive E and this directory is not on drive E"
The info is available when the program tries to load the item so it would be nice for the program to share that info.
Relative paths aren't on a drive - that is the whole point. Daz Studio does not check anywhere but the mapped directories, otherwise if it checked every possible location on the system as a starting folder a single missing file could take forever to resolve.
they don't check all drives ... they check a relative path to a Drive whose ID they pull out of Dim or the Directory path.
To not look everywhere the relative path has to start somewhere.
But if the prog won't tell us where that relative path started then the part that starts runtime/..... doesn't have any real information... because thousands of daz items are in paths that include runtime.
But since Daz doesn't check all drives or all folders but specific directories whose intial point is stored some where ... dumping the full path would be valuable.
And since that path had to be put in the programs "mind" to look there ... then before it's cleaned out of memory if the item couldn't be found dump the entire "relative path" to the error report.
driveID/directory name/Runtime/Textures/esha/ForestScout/blaze hood_Belt1.jpg tells me where the prog looked for it.
and is a start for figuing out the issue
/Runtime/Textures/esha/ForestScout/blaze hood_Belt1.jpg doesn't give me that info.
To be clear ... the programming on the many things the program does in using the data is incredible.
But this is just I/O and an error report. Which I expect is coded into a module that is called as needed by the main exe.
So adding a feature to that shouldn't affect the regular program flow at all?
You ar enot understandign how relative paths work. All that is in the file is, for example,
\Runtime\Textures\MyMaps\Skin.jpg
if the content directories are
D:/My Content
E:/Daz Content
F:/Their Content
then DS will look for
D:/My Content\Runtime\Textures\MyMaps\Skin.jpg
and it hat doesn't exist it will look for
E:/Daz Content\Runtime\Textures\MyMaps\Skin.jpg
and if that doesn't exist it will look for
F:/Their Content\Runtime\Textures\MyMaps\Skin.jpg
and if that doesn't exist it will report that \Runtime\Textures\MyMaps\Skin.jpg is missing.