Since Poser stopped using Adobe Air for the library, Poser became very slow if one uses heavy Libraries like 90 GB and above. I have set up Win 10 on a brand new ssd with the capacity of 1TB. I placed my main Library into the Document folder and gave it full access rights. The reading time for the pose library is 1.5 minutes, what means I choose a folder in this Library and poser needs 1.5 minutes to just open the folder. If there is a subfolder, it takes a 1.5 minutes to open the next stage as well. On the very same system I have poser pro 2014 installed. It has the same main library from the same source and it handles the same task in seconds. Is there a reason why poser pro 11.2 is that slow in this regard? Had some of you the same issues? Please let me know. In addition to this, I have I installed poser pro 2014 an 11.2 on linux mint, on this system both Libraries are working better.

Is poser 11.2 still indexing your libraries? There is an icon, an orange circle if I remember correctly that shows it is indexing. Until this is finished I found the poser 11.2 library very slow on one of my machines.

@ Nails60 I know what you mean. After i connected my Main Library with Poser, i open the library and let the indexing took its time. I deactivated the option for refreshing the index on every start of the library so the software should use the first index file. If i add new content, i normaly push the refresh button so the indexing prozess can include the new items into the database. I also set the search for items from deep to low, but this had no effect what so ever. It could be that there is a native limit for a single Library and my Library seems to scratch this limitation. I have tryed to fix this problem by creating smaller Libraries, for every Figure Generation a seperat one, but this is simply to time consuming.

@blackbonner: It's not the size of your storage what bothers Poser. It' s the number of directories and contained files that has to be check. Don't forget that Poser is something like a grandfather in his special software department. So is most of the code inside Poser. At times nobody could think about so many content could be available.

Simply solution: Split the content in several runtimes (or do you really need all content at once in one project?).

Try to keep yourself and your 3D-work organized! That will help Poser to work as fast as you expect. Another solution is (if you aren't willing to care and keep the problem away from yourself): Get faster hardware - and pay for it.

It's not the size of your runtime. I have over 170 GB in my V4 runtime without seeing this issue.
What happens if your runtime is not in documents?

@adp001 I use Poser since Version 5 and i am storing content since back then. So yes, i am aware of the fact that Poser is pretty old software. But this issue is not there if i run the same content library under the same conditions with Poser Pro 2014. One would think, that the jump from Adobe Air to what ever they use today to run the library engine is meant to be an improvemen, right? But it seems not to be the case. I came to the same conclusion you do, i sorted out items that i haven't used for years and gave each figure generation it's own department. I ended up with 5 Runtimes, plus my own stuff that is separate from all the other content. This was a solution for my initial problem, but now poser couldn't find textures or obj files, because of the many runtimes. This happened from time to time, not really on a regular basis, but searching 5 Runtimes manually is really a pain in the butt. My system is build on an i7x with 12 native cores and 16 GB of ddr4 Ram. I recently upgraded my Grafik Card from ATI Radeon 5900 HD to an Nvidia GTX 1050ti. This is not the newest or fastest piece of hardware, I know, but that's what i have and it works for DS, PP2014, Paint Storm Studio, Gimp and half a dozen other apps without any problems in regards of lacking or timeouts or crashes what so ever. But thank you for answering, i appreciate your comment and take that into consideration.

@donnean I was trying several places for storing my Runtimes. I keeped them for safety reasons on an external harddrive, a HDD with 2TB of storage capacity. My initial thought was that this HDD was the bottleneck and therefore I recently purchased a bigger SSD to run the system. The former SSD had 250 GB and with Windows 10 and all my Software installed there was not much left for having all the content. So i installed the Runtime on one of my internal HDD. Under PP2014, this was no problem at all, everything worked well. Since PP11, this became an issue. I thought, if i place my Runtime next to the Runtime Poser creates during the installation, it will run them faster. With the new SSD I have more then enough space for storage, so i placed my Runtime on it. First i choose the Document Folder under c/username/documents and run some testing. This was not successful, the library is slow and it takes forever to open a folder and load an item. Next i used the c/public/documents directory, like Poser do. Same result as before. I have no idea how to fix this problem.

donnena posted at 1:17PM Thu, 16 January 2020 - #4376742

It's not the size of your runtime. I have over 170 GB in my V4 runtime without seeing this issue.
What happens if your runtime is not in documents?

I would confirm your experience that it is not the size that is the issue, I have over 330g of content on an external 500G SSD and the library is fine. I takes a a minute or two when I first launch Poser but after that access to any content is a matter of seconds. Under the main folder of Poser Content there are over fifty runtime sub folders as I have broken the content down considerably. Each figure I use, Dawn, Dusk, M4 and V4 have separate runtimes and the poses are stripped out to further runtimes so that is eight runtimes already. I have a great deal of Sci-Fi related content so that is spread over three runtimes, sci-fi, space craft and space. Other runtimes include rooms, buildings, cities, medieval, equipment, containers, robots, plants, flowers, ground cover, lights, environment, HDRI scenes and materials to name but a few. I think this so does slow the library down when first opened but after that I find the library very responsive and even searches are usually less than a minute.

So, it seems the issue is not Poser, but something specific to the PC it's living on. Is your Antivirus active at the time you're trying to use poser?

@donnena I have windows defender running on my system and it's always working. The question is, why should a running antivirus software react differently to two pieces of software (PP2014 and PP11.2) if both programs are trying to access the same runtime. Seems not logical, right?

The question is Why does it work perfectly for me (and others), but not for you! What's different between our machines and/or Set ups. Hornet3D ruled out the external HDD possibility, as that works for him. I am assuming you are using USB 3 or Firewire? Some really fast connection for your external drive?

@donnena At first I used an external HDD on a USB 3.0. But I suspected that this was the bottleneck and I bought a internal 1TB SSD to run the OS (Win10) and all programs and databases. I used different settings inside Poser11.2 for the Libraries, the indexing process and the search for content inside the property's segment as well. I also used different directories for the runtime. But the runtime is stubborn as a mule. If I use DS and load my Main Runtime into it, everything is pretty fast. Like I said, in Poser 2014 everything works fine. Only Poser Pro 11 seems to think about the Universe and the purpose of life and one eternity later it came up with 42 as a solution. But it's funny to think that i am the only one who has this problem. Am so special!

there can be issues with windows search, you should try turning the indexing service off

Open an elevated command prompt. ( run as administrator )

Type the following commands:

sc stop "WSearch"
sc config "WSearch" start= disabled

The first command will stop the service.

The second command will disable it.