Award for stupid problem
bicc39
Posts: 589
My search content does not work, (separate problem)....crashes system
Have 35 Runtimes
To find an item have to open each runtime... go to section etc
At the end have many runtimes open....which stay like that.
So.
How Do I collapse all of them when done!
Thank Yoo
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
Right-click>Refresh seems to collapse all, I don't see another route.
Maybe you have your good reasons for having 35 Runtimes, myself, I have only one.
Daz recommends no more than ten, as each one slows the loading of assets (because the reltive path for a file is added to each Content Directory in turn until the file is found or the list of Content Directories is exhausted - so there is a lot of checking in the wrong place before the thirty-fifth folder is tried).
Each runtime has over 70 gbs.
Additionally have over 30 Poser Runtimes.with an average of 50 gb
All are stored on interna/external drives
Imagine the file size with only one.
Imagine
Once again, Richard, you have walked on water!!!!!!!
Righk click refresh worked
Thank you !!!!!!
There is an "Allow Container View Collapse" setting, what does that do?
I didn't know that was there. it tuns on/off the little widget in the fivider between the item list adn the cotnainer list, so that people don't have to risk losing their cotnainer list (and so not being able to get to any files) which used to be a fairly frequent issue. http://docs.daz3d.com/doku.php/public/software/dazstudio/4/referenceguide/interface/panes/content_library/container_view/start
Ah, OK. File Browsers sometimes have a "Close Unused Folders" setting where if you expand a base folder it collapses any other expanded base folder, to avoid clutter. Thought it might be something like that, but it didn't seem to have that effect.
As there is a limit as to how much can be put in one folder for the OS to read it, I rather doubt it would work lol ...
Possibly you have some content that could be retired to a storage folder or 34, that would lessen the amount of content to sift through for D/S. Simply renaming the main folder can "hide" it from D/S. To reinstate, rename it back. [only do this type of thing when D/S is closed]
A 3-4 terabyte "runtime" (ie. single content library) would be no problem.
Very serious questions (work And Problem involved)
Just take 35 runtimes created for Daz. As now stands each has over 65 gbs.
To create one major runtime would have to have a drive that supports that much (no Problem)
Would have to take one runtime and then copy and paste 34 separate runtimes into one,
The good part would that is it would find duplicates.
This would take an enormous amount of time (would be worth it)
I would not of course delete the 34 runtimes until the end
Again
Is it possible to have one major runtime as described.
Is there a minus to this I am missing?
What is the size of your one?
Thank you.
For NTFS the maximum number of files in a single folder is 4.294.967.295 but that is also the maximum number of files on a disk (partition).
But that is also a lot of files, if we say that a 1 TB runtime contains on average 2 million files that means that even if you fill a 256 TB disk (max disk size for NTFS) up with runtimes the number of files will be about 500.000.000 which is less than 1/8 of the max number of files the disk potentially can contain.
All I know is that one day I realized all the images I had been downloading in one download folder, were no longer being 'read' until I moved them out into other folders. It was a scary moment lol ...
As to merging Runtimes, rather than copy/paste [which would take forever 'cause you'd have to do it piecemeal], I would try renaming the folders, sliding one folder over to merge with another, that type of thing. Tell the system to 'skip' duplicates 'cause one would have to manually verify those.
Or, if one has most of those products from one location, i.e. Daz3d, then I'd go for renaming the official 'content/mylibrary' collection folder to something else and make an empty one bearing the required name. Delete any metadata from DIM's collection, sign in at Daz3D the store, then run DIM to download and reinstall everything to the one location. It's the fastest way. Keep in mind though that the install location is correct before starting ;-) And of course make sure that said location is large enough to accept it all.
And unless there's some very good reason for downloading/installing 'everything' -- might want to size down the request aiming for the products truly in use or expected use for now and the near future.
I discovered that folder read limit with my image collection too
I don't think it's well known as people tried to tell me my drive must be failing
now I chop my image folder up into smaller folders and roughly catagorise them into cats, scenery, fantasy etc
As far as I understand how DAZ Studio and the windows file system works, I don't see any practical limitations for how large a runtime / content library can be on the current premises. The only problems might be the Content Library browser in DS becoming slower proportionally with the size of the runtime, plus the limitations disk size and the amount of available memory sets. And maybe the DS database, I'm not sure how that interacts with the Content Library and what limitations it may have.
My own runtime is currently 1.8 TB containing almost 2.500.000 files and 360.000 folders. The DS Content Library is still quite fast browsing the content but it's also only a relatively small number of files in the runtime that are referenced in the Content Library. There's no point in storing paths to texture files and other content files for example, as these are accessed by scripts only through a different process. So you only need to have the references to these scripts in the Content Library browser.
My guess is it's a limitation in the software you are using, or you don't have enough available system memory. If you can write the files to disk in the first place there must also be a way to read them otherwise it would be a disaster, technically.
I would advise against putting everything in a single Runtime folder if you have that much content -- NTFS performance is terrible when the number of files goes into millions, especially if the files are small. I once had a folder with 3+ million small log files (don't ask how it happened) -- Windows Explorer or Total Commander would just get stuck on it trying to figure out the size and number of files, much less show the list, and it took 15 minutes to delete the folder from command line and that's on Samsung 970 Pro M.2 SSD.