I have no issues with large libraries in Poser. I use (many) subfolders for categories and this works fine. I used to have multiple runtimes, but that made finding stuff even more difficult and tedious. Problem is that many items fall under multiple categories.
A large library makes the tree menu functionality in the library unusable (too many items with a primitive scrollbar, too slow when starting poser) but having many runtimes makes the tree menu less useful as well. When you switch it off, navigating is just as fast in a large library as with small runtimes. The lack of a tree is not a serious problem if you can navigate within a few seconds.
So I am not ready yet to add many additional runtimes.
.
Regarding the Does Not Contain rule: You can exclude words, but with many items there just are too many words to exclude (with car that would be more than 40 in my libraries). Maybe a solution would be to allow leading or trailing spaces as signficant characters: " car" or "car ". In such as a case it would find most of the items you are looking for.

Updating with new items: Scan takes about 7 minutes (40 min first time), Identifying new items takes a few hours (2 hrs now. still running, was 4 hrs first time). I hope crossreferencing goes a bit faster.

I really wonder if dividing up into multiple runtimes will significantly speed things up since the program has to handle the same number of items - crossreferencing, identifying, etc, and the bottleneck seems to be the number of items in the database.

Maybe switching to a SQL sever like solution - as svdl suggested - would help in case of a million items.

I have had no problems installing this program. I scanned my main Poser library with 850K items and it ran fine - although it took 56 hours to complete.
The program itself seems to work OK and its search works fast and does a reasonable job of finding related items. It could be better if you could specify an isolated word as filter which does not return results in which the word is part of the name (so "car"  would not return scarf of cartoon)

The scanning process influences somehow the performance of Poser in some way. During the scanning Conforming a clothing item now takes 10 seconds. Once the scanning is completed, performance returned to normal.

I will try this out a few more days, but for now I am happy enough with it to seriously consider buying it.  It certainly will save me a lot of time finding things.

For those of you who have vista: You can use the Vista Search engine to find files in the  library as well as in the texture and geometries folder.
Just make sure that you have indexed the fhe Runtime folder and add the poser file extensions (such as .obj,cr2,pp2,ppz, etc) to the index. Search in a 600GB runtime is usually within a few seconds. Use the "favorites" folder to save some search locations to speed it up even more.
I especially like to feature to use the search engine within the File Open dialog to search for mismatched texture and OBj files.

Other desktop search engines probably work too but won't have it have it integrated within the File Open dialog.

XP search was really slow, but the Vista one is much faster when the index is used.

Select DAZ Studio during install of M4 and then browse to your PoserPro runtime folder.
For some unknown reason the DAZ installer does not recognize PoserPro. It only recognizes Poser 7 and earlier.
The Poserpro runtime is likely in your User folder depending how you installed PoserPro

Regarding inflating props: You turn off smoothing for individual props in its properties

I have no problems running the script multiple times - I do it every time I change lights. So I cannot help there
It also does not turn off or negate the AO I set on other props, figures or lights.

The bad texture warning is usually a sign of lack of memory. Depending on how much you have in the scene it might have to do with the render settings. Be sure to use the external renderer, this will easy your memory requirements when rendering. Also do not use the Automatic Render settings - use the advance ones and do not set the raytrace bounce, pixel samples and irradiance caching too high if your scene is complex.
Other possible cause for running out of memory in Poser is if you have theTexture resolution in the Preview mode set too high - lower it to 512 if you have problems

Move the camera away from the eye, then you will be able to select the polygons
If you are too close, you cannot select them

P6 poser.ini is in prefs in the runtime folder
P7 poser.ini is in Documents And Settings Application DataPoser 7 folder

I don't notice any difference between software and hardware accumulation buffer for OpenGL

The Enable Hardware Settings is another setting which uses the GPU for special features and the speed depends on your hardware.
The Enable Hardware Settings is only valid for preview and only present in Poser 7
I usually have it off and turn it on to check on details for textures. In that case I also set the preview texture size at a higher value. Afterwards don't forget to set it to a lower value again since Poser needs the memory.

Groeten,
Wim

Check if "Enable hardware shading" is set to OFF in the Render Settings for Preview
If it is set to ON it can slow down the machine quite a lot especially in the UI

Wim

Netta,
if you are using V4.1, the breast morphs will not work if you use the stand-alone version.
If you use the plugin version ,they will work. After analyzing V4.1 with the plugin, you can copy the analysis data to the standalone analysis folder and it will work there.

At least, that is what worked for me

Wim

I sometimes set it to 16bpp to enable screendumps and forget to turn it back...

Best thing to do is to check for a driver update.
If there is none, then file a bugreport to E-Frontier. Since this is a relative new card, P7 might not recognized it and therefore not enable the enhanced features.
You did try the latest Service release 2, I assume?

My experience is that they take these incompatibilities (if that is what they are) very seriously and will seek or provide a solution.

Wim

If the HW Shading feature is not supported you might definitely have a driver issue, because it might not recognize all the features of your card.
Max Preview texture size should go to 4096. (although it this will take a lot of memory)

I have both an ATI X800XL and NVidia 7600Gt - older videocards - but these have all the features enabled.

Just to check - You do have 32bpp color on? If you have it set to 16bpp it will disable the HW Shading feature.

Be sure to have HW Shading disabled in the Preview Render options.
It not only slows the OpenGL preview down, but also makes the mouse behave more reliable.

With your hardware configuration you should be able to have 4-5 hires figures with clothing and hair items in the scene without too much slowdown.

Above that you might run out of memory and get into memoryswapping and that will slow things down considerably. (You can see this in taskmanager in Windows)

Be also aware that not only hires figures are memory intensive, but also some clothing items, dynamic hair and props

I have scenes with more than 10 hires figures (V3,SP3,A3,M3) with clothing and hair and props which is still manageable on a XP64. Intel Dual Core, 4GB, Nvidia 800XL and which will render 4000x3000 images. On an XP32, AMD 6300, 2GB, ATI video these scenes are extremely slow in the preview mode.

She looks great!

Would you be so kind to get me a download link too?

MAT files for hair work fine if the figure and the hair prop is active in the document window (example: Figure 1, AilaHair).
If the document window has another figure (clothing) selected with the hair prop (example: HD_Pants, AilaHair) MAT files will not work on the hair prop.

If you are in the Pose room and you select the hair prop, the figure to which it belongs is also selected. But in P6 - if you have the material room open - you can select a prop with the colorpicker. The material settings will show for the hair and the prop will be selected in the document window - but NOT the figure to which it is parented. And conseqeuntly the MAT files do not work.

So the solution is simple - select the hair prop in the document window and MAT files for the hair will work