If that's the case, please do contact Smith Micro about it, http://support.smithmicro.com/

It helps SM to get a better view of the problem and look for solutions.

Why am I posting this? I've contacted tech support with a problem and there looking in to it. They  did a good job in solving the main one, it was some conflict between P8 and my firewall. The disappearing library issue was solved also, but took a few steps to get it sorted out. So, that's cool. Still there are problems left and I'm pretty it's a bug, but due to the few instances files, support isn't sure about it. Besides me only 2 people reported the issue.

BUT...... I've read post from a lot more the 2 people encountering the same problem. Posting only here isn't going to solve the problem, contact tech support. They're the people that need to know about it, they need to get a good view of the problem and as much as information as possible.

Yes, post the issues you have with P8 here, but make sure you contact SM also. Don't be put of by the 'that wasn't reported in beta testing, so it's your problem' comments certain people make when you post a problem here. Beta testers aren't perfect and if you've been using Poser long enough you notice a lot of issues slip through the beta testing, we all know that. I'm not trying to be mean about the beta testers, but it's a fact that they didn't come across every issue there is, even though they've tried there best. I wouldn't be surprised if the poser testing team is to small and the way they go about beta testing Poser Pro 2010 looks very good to me.

Poser 8 is great, but far from perfect and we need to help SM make it more perfect.

I couldn't agree more :o).

Laurie

Hi, I've just submitted a support report at Smith Micro regarding material room crashes, seems there's a lot of people with this issue in one respect or another. The more people who let them know the problems they're having the more likely to get it sorted in the first service release. Fingers crossed :)

Well, their protocol for dealing with bug reports is not much good, and there is no visibility at all of what bugs they are actually working on.

I reported a problem with Poser 8 Room Help screens (on Mac), and I got the reply "We can't replicate that here. Try restarting Poser".

I won't say what I replied to that suggestion, but it seems they finally got the message that I was reporting a Poser 8 bug (Poser 7 and Poser Pro Room Help both work fine on my computer).

Then today I received an email saying that the case is considered closed because I have not responded to it in four days. What's that about? They won't investigate this bug unless I keep pestering them every few days? So it seems.

I'm actually very much on SM's side in this, but they are not helping themselves.

Thanks for this thread.. I will add a little insight for those wondering.. I am one of several staff members handling the reports from, you the customer and we do have some method to our madness. So, how reports of issues dealt with?

The method is the same as with all the companies I have worked with doing Alpha, Beta, and Bug Hunts (that is my term for those issues that crop up after the release), so there is nothing earth shattering

Customer reports of issues. We get specific details and then try to duplicate. Currently, I have 12 Systems at my disposal for testing reports of issues. I try to first duplicate it on three main machines on the PC side and one on the MAC side. If I can, I then try to duplicate it on the opposite platform (to see if it Platform specific) I then file the steps to duplicate as a bug report.

If I can not, I then try to match closer to the system details (OS version, System Details, Install Locations, etc....)

If you report an issue and you get a one or two line response, thanking you for reporting the issue, it means it already has been filed and the cause determined (which means it has been duplicated, discovered the cause, and they are working on a solution.)

If you get a request asking for more details, it means either we want to verify your issue matches one that has been filed as a bug report or it is a reported issue, but the cause has not been determined.  (or you are already working with Support and patiently verifying checks, details, etc... Thank you!) In both of the latter cases it means we have not duplicated the issue.

Important... If you get a request for trying some steps, it means there are several levels of the issue and we need to verify what issue you have.. The Blank Library in Poser is a great example of this...Most are resolved with updating their System and verifying a few details. So try those tips.. those tips come from the feedback from users and our own testing, in trying to reproduce the issue. Those that this does not resolve the issue, there seems to be multiple levels of the issue being reported. One is permission issue. These are those that can view it in their IE Browser or in Firefox, but not IE. The others, can not see anything in either browser or the program after doing all the updates. All of these we still try to duplicate. I am hoping that we will figure out the permission issue soon.

At this time I am working on trying to break it on one system... with little luck I will add.. I did succeed in hosing my Network connection.

I want to add, just because something does not work on your system, does not make it a bug. Just because we can not duplicate it, does not make it NOTa bug. All of these issues need to be reported. Many issues are settings and the Support Staff (as well as some members of the forums) can help you resolve. Do not assume if you run into an issue, that it is known or that it is not addressible at this time. Most contacts to support can resolve issues with installing updates or missing files from their system.

If you are using a Download of Poser and you get an invalid File error or some other error during installation.. the file is corrupted, you need to redownload (contact Support for some tips) and reinstall. There is nothing wrong with the files on the Servers.

If there is a conflict with another program or setting, that also is not a bug, but we still need to know, so if you encounter an issue that is other than an error during installation or missing updates, and you resolve it, please let us know that as well.

In case of the automated Closed Response, it means either you missed a reply from us where we requested some feedback, or notified you it has been filed (Duplicated and they are working on a solution) and the system is now closing it due to lack of activity on the response.

Being Closed or Solved in the Support System has only to do with your communication on the issue. Unfortunately we will not notify individuals when the fix is available. That will be when the Service Release is announced. If you get the automated response about being four days since the last response, look at the history if you do not recall a response prior to that. There should be one asking for details or letting you know it was filed. That notice only goes out to incidents we have replied to and no response has come back in the past four business days.

Hey they got you guys working weekends too eh?

Everything i posted on my thread here..http://www.renderosity.com/mod/forumpro/showthread.php?thread_id=2778694
I have sent into SM. But, unfortunatly they have not experienced the same issues.

I'm sorry I would love to help but I felt like the email I got back was more of an accusation that I was telling lies, rather than a "Thank you for helping us improve our software."
I'm not gonna send in 50 screenshots and keep a note and time stamp of when I got the bug issue and what I did exactly before and after the issue happend. Yes there are mat pose issues, the Alyson mesh is full of bugs ...

they reply I got was like a slap in the face. Since then I WILL NOT be waisting my time reporting issues. Sure I might post it on my thread but I can't believe the "warm welcome" i got from SM trying to report bugs. I'll just take the "someone else will take care of the problem" approach... and pray it will get fixed.

By the way, if you didnt visit my thread, this picture is what happends to Alyson when you replace her with herself sometimes...... not an opengl issue, it's a, alot of the verticies are not welded and don't try to export the mesh to look at it without welding verts issue....

ratscloset - thank you for the explanations. I did not think you had no method, or even that you are mad!

I actually have some sympathy with you for having to work with the limited tools at your disposal, which were designed for individual user support, not post-release bug reporting and tracking.

But clearly some reports are not handled according to the protocol you describe. In my case, the last communication I received said, in effect: "Oh, now we understand what you meant." (following my clarification of the error). No request for further information, no notification that it was under investigation or filed. There was nothing I could add, so I did not reply. Then yesterday: Case closed. Will it ever be investigated? I have no idea.

I have some faith that SM will fix most Poser 8 bugs, big and small. It's just not very nice reporting a (relatively minor) bug, having been encouraged to do so, and then being left wondering if anyone really cares about it.

Of course I know that you and your team do care, and are dedicated to the task - I certainly would not dispute that. These are just glitches.

I saw your incident myself, and I also tried to duplicate it. I also saw the response and it apologized for the troubles and asked for more details, explaining what was attempted on our end, in hopes our steps would point out what we did not do.

This is one of those cases we need more information. I am sure you encountered the issue, but until someone is willing to provide the assitional details, if there is an issue, it will most likely never get fixed. I show the incident waiting for a response at this time.

Quote - Everything i posted on my thread here..http://www.renderosity.com/mod/forumpro/showthread.php?thread_id=2778694
I have sent into SM. But, unfortunatly they have not experienced the same issues.

I'm sorry I would love to help but I felt like the email I got back was more of an accusation that I was telling lies, rather than a "Thank you for helping us improve our software."
I'm not gonna send in 50 screenshots and keep a note and time stamp of when I got the bug issue and what I did exactly before and after the issue happend. Yes there are mat pose issues, the Alyson mesh is full of bugs ...

they reply I got was like a slap in the face. Since then I WILL NOT be waisting my time reporting issues. Sure I might post it on my thread but I can't believe the "warm welcome" i got from SM trying to report bugs. I'll just take the "someone else will take care of the problem" approach... and pray it will get fixed.

By the way, if you didnt visit my thread, this picture is what happends to Alyson when you replace her with herself sometimes...... not an opengl issue, it's a, alot of the verticies are not welded and don't try to export the mesh to look at it without welding verts issue....

Quote - ratscloset - thank you for the explanations. I did not think you had no method, or even that you are mad!

You do not know me very well then, do you!

Seriously, the tools are not limited. I have access to all the engineers and the Content Team for any and all issues. The Support Team communicate back and forth, often confirming results or having others try to duplicate the issue if there is any question. Generally, an unconfirmed issue is taken ownership by one of the team to follow up on, and as more reports come in, they are transferred over so there is more data. We have meetings where we go over those issues that are still active to see if anyone may have something related or insight.

Basically, the only limit is the data. Usually, it is because we have not asked the right question.

NOTE: Previous post should have been Additional details, not assitional!

ratscloset would you ask the engineers about adding a user option to revert P8 to non-Flash based library in the next patch? Just something that lets the user choose which they want to use in the preferences or something similar. You can have a cookie if you do. ^__^ 

That has been asked by others, but I am not sure it is possible, so I am not sure it could be done.

I posted a few things in this thread: ttp://www.renderosity.com/mod/forumpro/showthread.php?thread_id=2778606&page=5#message_3502134, but will send on to SM.

My experience as a beta tester for software was that even when I did report a number of serious issues with the software, they ignored it.  One company I beta tested two versions of their software and both times, they chose to ignore all bug reports.  I stopped doing it for them.  Since then, a well-known company bought them out and they still produce buggy software.  So it may not necessarily be the beta testers fault.  Their own bug submissions were probably ignored.

Link was messed up for the other thread.[

http://www.renderosity.com/mod/forumpro/showthread.php?thread_id=2778606&page=5#message_3502134](http://www.renderosity.com/mod/forumpro/showthread.php?thread_id=2778606&page=5#message_3502134)

Quote - ratscloset would you ask the engineers about adding a user option to revert P8 to non-Flash based library in the next patch? Just something that lets the user choose which they want to use in the preferences or something similar. You can have a cookie if you do. ^__^ 

That has my vote as well!

When you say "revert" what do you mean?

The old library doesn't exist. It would have to be written from scratch, like the rest of Poser 8 GUI was.

Quote - ... My experience as a beta tester for software was that even when I did report a number of serious issues with the software, they ignored it.  ....

I had an experience like that myself. It was my first and last experience, I can tell you ;o).

Laurie

Quote - When you say "revert" what do you mean?

The old library doesn't exist. It would have to be written from scratch, like the rest of Poser 8 GUI was.

If that's the case, then get rid of the current one and replace it with something like XL eXtended Library. Works much better, great options, a lot more flexible. Imo they should have never gone with a flash addition......

If I wanted to get rid of Poser Pro, and shift to Poser 8, would I just copy the runtime file from Poser Pro to Poser 8, or is that asking for trouble?  My Poser 8 works perfectly - far better than Poser 7 - faster and the renders are faster (running VISTA 64 with 8 gigs memory, latest updates).  seems like a waste to keep separate runtimes. 

 Under scripts>partners>(forget the next part as I am at work, but I think it is shaderworks), there is a script that searches your hard drive and imports your Poser Pro runtime. The one that ships with P8 works with Win. There is an update for the mac found in the poser forums at RDNA. Works relly well as I used it to import my PoserPro runtimes to p8.

IMO, intergrating the two runtimes will lead to disaster.  File components essential for current version Poser integrity may get overwritten.  If there is no urgent reason to delete PoserPro, simply use it's runtime as an external link.  External runtimes help in organizing content as well as keeping the workload overhead down when running your application.  I have both Poser 7 and PoserPro runtimes feeding Poser 8 without any problems.

Yep....

That new GUI and especially the library is very impractical and slow.

With the old GUI, I can go from THIS:

Quote - Argh - I have lost the preview-window in the P8 materials-room...
does anyone know how to get it back?

In the preferences (on the interface tab) change the launch behavior to "Launch to factory state" and then restart Poser.

I'd suggest to use the UI dots to save some room layouts so you can just get the window back by clicking the UI dot the next time :-)

...with a single click each.

I have hundreds of highly organized "micro"-runtimes so I never need to search for stuff or suffer from long Poser loading times as my main runtime is complete empty.

With Poser 8, you have to disable docking to prevent you from moving elements accidentaly around.
Both docked and unocked windows now use up a lot more valuable space than before.

The GUI is also pretty slow and unresponsive.
While moving the camera is quite fast, actally posing is jerky and like moving through molasses.

Leaving the material room is also slow.

Browsing through the library is a mess.
Having to click on every thumbnail just to see what it is, is a joke.
Having to select something just to add a pose or figure again is a joke.

I constantly use the memory dots because I do my own posing, but whenever I start Poser the memory dots revert from "pose" to "gui".
Again an aditional mouseclick that could have been avoided with a little less "awesomeness" and a little more "efficiency" in mind.

I think this GUI was made with only the "casual" "play with Poser" users in mind which just load ready-made content, but it is very unsatisfactory for those of us who actually try to WORK with Poser.

Besides, Adobe and flash have a very BAD general reputation (flash cookies, flash-ads, info harvesting) and a lot of people rather not have this stuff on their systems.

Thank you!

just to agree with OP, in addition to submitting bugs to SM, post them here as well, in case it's actually a feature (not a bug) and somebody knows how to fix it.  that way everybody learns something.