I owe an appology to this forum.  It seems that my photo program no matter how you change the dimentions changing the image size forgets all image dimention changes when you "save for web".  The dimentions of any cropping stay but the changes in image size have to be respecified. 
At the point when I posted I had tried 10 times and every time I tried to post the form resets the image and thumbnail names.

There's a serious suggestion for this forum.  When the thumbnail, or other items on the form are incorrect it would be more than useful if ONLY the area of the form in error were reset.  As it is now if you forget to check the item saying that this is your work of art it resets all of the form.  If it has a problem with the thumbnail it forgets which picture you wanted to upload.  Since the other information on the form is correct resetting the whole form should NEVER be done.

I could use a generated thumbnail in this case because the picture required a nudity tag and therefore a custom thumbnail.

My bad!  The hip object is where the problem is.  Not sure whether this will help anyone else but I found out what happened in my case and that V4 in that particular scene of mine is now FUBAR.
    As an explanation:  I was working on the scene in P8.  Since P8 takes a long time to come up I left it up and running while I went to take a nap.  When I got up and only after I'd resaved the scene did I notice the problem (I'd had V4, everything touching her and all lights affecting her all set).
    I tried loading the scene into P7 but had the same problem.  A bit later I noticed that the lights on my sound system were flashing.  That's an indication that there was a power fluctuation.  Not one bad enough to reboot my computer but possibly bad enough to mess up files that were in memory.
I expect the following to be true although I can't prove it:

1. If I hadn't saved the file before discovering the problem I would only have had to close Poser, reopen it and reload the scene to correct the problem.
2. all other similar problems are probably caused in a similar fashion.

If, as I have, you saved the corrupted file over your last good save the only answers are to rebuild the scene or at least reload everything associated with V4 or find a way to edit and correct the pz3 file.
Anyone know of an editor that can edit and save a pz3 file?  I really don't want to have to redo all the posing for V4.

I've just run into the problem for the very first time in hundreds of renders. :(  In my case it isn't the hip but the lower half of her abdomen.  Oddly only the lower half which is really crazy since you can't select that as a figure part.

The reason to close folders is that P8 scans or is supposed to scan all library segments 1 level down from what's open.  If the top level has 3 folders and you leave it open P8 is then scanning whatever number of files is inside the 3 folders whereas if the top level folder is closed it will only scan the 3 folder names.
     If, as an extreme example, you left all folders open it would be scanning every file in the library not just the second level items.

Closing as many folders as possible before shutting down Poser was one of their recommendations to me.  The other main one was to turn off indexing.
I have to admit that I really love the renders I've been getting out of P8.  Its render engine produces excellent results in very fast time.

A lot of the problems seem to be very individual in nature.  People have their librarys in different places which creates a uniqueness to the environment.
I've been going over things with Smith MIcro.  I'm not getting a failure or an error message.  In my case and because of the environmental items, it may be very personal, turning off indexing seems to have had at least some possitive effect.
IN my case it's now reading the runtime that it starts up with but  ot always reading any that I switch to.

Thanks John.  Do you know why it was decided to make use of IE as a part of the ibrary functions in P8?  Personally I'd prefer programs that are completely stand alone. 
    My reason is simple.  It's a lot easier to make sure that a program you've worked on is stable if you're dealing with only code specific to that program.
   I won't get into why I have issues with MicroSoft here. ;)

Sorry for my earlier frustrations. My appologys to those at Smith Micro for having said P8 is crap.  There are still some seriously flawed bits of programming in there.  My main frustration was that at the time I had NO access to anything in P8.
    What was happening was this.  P8 would go off into the boonys reading files for about 15 minutes at startup.  When disk access had slowed or stopped I'd be expecting it to have labeled all of the folders so that all I would need to do was click on a folder to open it.  Instead it was leaving all but a few with "?" on them.  The only conclusion I can come to about what was seeming to happen is that P8 was doing a complete search for content within the library and then not updating the actual displayed information in the user interface.  At that point I'd click on a folder I wanted to open and get an icon on the end of that line that looked like it should be a "working" icon.  In fact it's a refresh button that, if clicked,  forces P8 to reread the file names in that folder.   
My main frustration in the end turns out to be button which:
A) Isn't obivously a button
B) Doesn't have text or icon that are at all useful in knowing what it's for
C) shouldn't be needed
   If the button had been properly made and labeled so that it was obvious what it was for I would not have been having the frustrations that I was.  Labeling it "Refresh" comes to mind as something useful.   A scan for content that doesn't discover content that is actually there still qualifys as really bad programming.  So does a button that isn't either obviously a button or labeled in an obvious way.
The refresh button and associated code are not needed at all.  If the user clicks on a folder that P8 hasn't scanned, no matter why it hasn't scanned it, it should automatically scan the folder and open it.  Just remove the button and the code that calls that button.  Calling the refresh routine directly is much more efficient.  The user doesn't know, doesn't need to know and doesn't care whether the program needs to rescan the folder.  All he/she knows is that that's the folder he/she wants open and that the program should open it when it's clicked on.
      P8 should on initial startup and search for content be creating a permanent database of the items, poses etc that are in the library.  Displaying the number of items that are in a folder is fluff.  The user doesn't  care how many items are in a folder until it's open and he/she can see exactly what's there.  Since it's putting the number of items inside a folder on the folder that seems to require the extra scan at every program startup it's counter productive.  That's a good 15 minutes of time wasted waiting for that scan.  Which in my case it isn't even completing properly.
   On the lighter side I'm glad to see that the computer industry still hasn't changed much over the last 10 or 15 years.  The programmers and designers still don't spend enough time letting each other know what they're doing. ;)

Thanks for the feedback people.
Oh, for those with curious minds I have P8 setup as suggested by Smith Micro.  Runtimes are not only outside of C:program files but on a seperate drive.
     I think you can understand my earlier frustration.  I had access to next to nothing within P8 and the refresh button:
a) should only be required when you've added something new to the Poser library while Poser is up and running
b) a LOT more obvious in both being a button and what it's for. Um, "Refresh" comes to mind as a useful icon for that button.
At least now that I know no matter how strangely I can at least use P8 I'm laughing rather than ranting but I'm still wondering about a few things.
Primarilly, why  P8 doesn't do a single initial scan for content, build a library and on subsequent startups just read the information in and allow the user to refresh any new or updated folders?
     Does anyone else here feel that's a better working method?  It would save 15 minutes worth of disk access at startup or at least a large portion of it since it would only need to access a single file.

Just discovered something.  I may have been too POed to notice the obvious.  I had been hoping that it was something like this. 
When you click on a folder with a ? on it there's a button that appears at the end of the folder name.  That button is a refresh button that forces a scan of the folder.  The button is a long ways from being obvious.  It has a small circular arrow which I had assumed was telling me that it was working on scanning the folder.
Still not sure why they don't have it automatically scan the folder when there's a request to open it but I'll settle for usability even if it is more than a bit clunky.

Sorry, I don't normally rant but I'm ROYALLY POed at a product bug that should have been caught in Alpha testing, certainly in beta testing at the latest but still exists not only in a released product but one that has gone through a  few service releases.
Most items that I post are suggestions to others not rants.

I do now have a ticket open with Smith Micro.

I guess it's a work around or nothing for the moment.  Does anyone know if doing the posing in P7 then importing the scene into P8 and doing lighting and rendering would work?  Will P8 find the items in the folders labeled with a ? in that case or will it give you a message telling you that it can't find the object or objects?  Seems a bit counter productive since they touted the new library handling as a feature.

Glad to hear that you've found something that sort of works.
I've come to the conclusion that P8 is a piece of crap that never should have been released.  It won't even finish a scan of it's own miniscule base folder in HOURS!
All of P7, DAZ/Studio, Carrara and Bryce handle their library structures better than P8 does.  heck they all handle the P8 structure better than P8 does.
What total twit decided that he needed to know how many items were in every folder BEFORE he opened any of them?
Sorry I'm still at the POed stage.
Will rebooting help at all?  So far it's just better, easier and safer to use P7.  No point in an app that can't read it's own data structures.

Great idea except that I've been going over the boards for about 1 hour and it still hasn't scanned the whole of it's miniscule base folder.

Sorry for posting the added thread.  There are so many new threads posted here that it's difficult to find threads pertaining to a topic even if they're only a few days old.
What I want is a fix by Smith Micro not a work around.  P7 had no problem in reading the library structure why should P8?
As far as handling content goes P8 is a downgrade not an upgrade.

OK, having similar problems.  I'm using the latest Nvidia drivers but P8 MAY get to changing the ?s to numbers after several hours.  when you click on a folder marked ? P8 is too without AI to even read the content it just opens an empty folder view. :(
P8 isn't an upgrade it's a downgrade.  P7, Carrara, Bryce, and even DAZ/Studio all work better when it comes to handling content.
What was so wrong with the way P7 handled content.  Sure it took a bit of time when you went to a new library but it didn't try to read through all of them on startup and it DID always succeed in reading them.