Does anyone know if there is a publically available list of known bugs with Poser Pro 2010 beta? I can't find one so far.

If there isn't, then perhaps this thread could be the start of one!

Cheers!

They are releasing updates almost daily ... any list would be obsolete as soon as it was posted.

Hmmmm.

There must be different levels of involvement in the Beta program for Poser Pro 2010. I have only received the first download, with no almost daily updates.

lmk

Attached Link: http://poser8.smithmicro.com/poserpro_2010beta/bugform.html

However, the linked page is the original announcement of the beta programme, at the bottom of which is this:

Poser Pro 2010 beta known issues

• To be listed...

BTW: I don't believe SM are releasing any updates for an unsupported beta product still in development. If I'm wrong and they are, as far as I'm concerned they can keep them. I'm using Pro 2010 now, but I'd rather wait for the full release.

@Gareee, are you sure? Do you have the link? Thanks!

@lkendall, "almost no updates"? That implise there are "some". Have you got a link?

@anyone, anyone seen a better list than SM's "To be listed... " ??

Well, the communication channel SM -> "open" beta users (those owning Poser 8 and Poser Pro and thus having access to the beat) is obviously bugged...

@dizzi: ???

Not bugged. The way I see it, the Pro 2010 Beta user bug-reporting channel is intended for one-way traffic: Beta users -> SM development team. "No support" means no updates for Beta users.

The only thing I would expect SM to provide at this stage is the list of known bugs on that there web page. First because it's a sensible thing to do, and second because they said they would.

 If I remember right Gareee was a beta tester of P8. So one would have to assume he is more involved then the  P2010 public beta I am guessing.

Yes, I 've been a beta tester for poser for the past 4 years or so.. and odds are they have release levels when they feel they have a good solid release for the general public.

I've actually got announcements of two new beta verions today alone! I'm actually having problems keeping up with the new versions.. I think I'm seeing 7-10 a week.

Which is part of what impressed me about SM... they are giving these guys the funding to really dig into issues and add features as well as squash bugs pretty quickly. Sometimes they really amaze me.

I think for poser 5, a few days before the surprise launch, I had run into a "showstopper" issue.. and I had 8 new versions in one day alone, trying to work that kink out before they could claim gold, and announce the release date.

The developement team are really great hard working guys.

All except that Bagginsbill guy.. he's such a slacker! LOL!

I, for one, can't complain. The first (and so far only) Poser Pro 2010 release for the public Beta, seems to be Poser 8 with 64 bit rendering and Gamma Correction, but it works great, and I feel lucky to have this much extra ahead of the actual product release.

I am glad to hear about the progress of Poser Pro 2010. We will expect great things from this version.

lmk

Well Gareee, I do wish you would pass some feedback from the beta testing community to SM that it really would be good to have a list of bugs available for us. Its pointless us sending them issues that they hav resolved and pointless sending them duplicate issues. There are a load of open source bugtrackers out there, maybe if they set one up and made it available they would get much more useful inf from the community.

With things the way they are I for one don't feel much like spending a lot of time reporting problems when I have no idea of knowing that what I send is useful or not.

Also, if they have newer versions, why dont they make one available to us? This also would provide them with valuable feedback.

Please pass this on to SM. Thanks!

I think it comes down to which would you prefer: they work as hard as hell as fast as possible, or they take someone off developement, slow down developement and keep the general user beta testing current.

Personally, I prefer they crank out bug fixes as fast as possible. Since my last reply here, I've had no less then 8 new beta versions! Its actually been hard for me to keep up with the new versions the past week or so.. but I would MUCH rather have that problem, then see them go to weekly, or monthy updates.

Yes 8 updates in 5 days was hell, let me tell you.

I'm so glad I'm done. I was working on the new GUI night after night - I was so tired I felt like throwing up.

Now, I'm painting a bathroom instead of coding and testing, and I love it.

Hello,
I wished there was one update per month. From posts in other threads I take it that
the issue with the long startup time has been fixed.
In general, I was very happy with the beta, except this single problem, but that exactly is very
annoying so I have momentarily stopped further testing until that thing is sorted.
I had infrequent crashes when saving new items to the library, but trying to make that
reproducible would need a faster startup time.

Best regards,
   Michael
 

Knowing the developement team, they are busting chops working towards a final release candidate or date.

It would be kinda silly releasing a beta update, and then 2 weeks later release a final version.

bagginsbill - So, what shader are you using on the bathroom? Glossy? Blinn? Are you using IDL? Could you post some renders, please?

Whichway

@Gareee... You guys who are beta testing are a limited resource. There are few of you and many of us. with the best will in the world, you WILL miss bugs. With many many "amateur" esters that could be utilised as a great free resource it really does make sense to give someone the task of scanning through properly filed bug reports.

The more machines the code is tested on the more chance there is of a combination of different software environment and beta release turning up buigs that you guys will never encounter.

Putting a product out to market with more bugs than it need have will mean much more very expensive support after the fact. It is much more economic to release good code and have to provide much less support. It also gives a much better impression of the product to the consumer base.

Why does Micro$oft relese betas of its operating systems months in advance of RTM? Because they know that investing in soe time fixing bugs before release will save them millions of dollars.

So, in answer to your posited query, would I rather they cranked out fixes to the bugs they have or spend some time checking through bug reports an afternoon a week for one person? I would MUCH rather they checked the bug reports and lengthen the project by a week or two.

You aren't talking a huge developement department like microsoft.. you are talking something a fraction of the size, with a fraction of the manpower and budget.

Just the fact that they have given you guys an early beta to play with is surprising, and I think you should be greatful for that.

I think if they did an open beta to the general public with full input, you'd be looking at 6 months to a year added to developement, and odds are new features not even posible because of budget constraints.

Look at the fully open Daz Studio beta as an example.. 5 years later, and they still haven't managed to figure out propagating scaling, and instead developed thier own system, claiming that poser's was "broken" instead. And they can't even do a reasonable conversion of a poser basic mat, let alone displacement.

The biggest complaint about Daz studio from content developers? Too many beta versions, too many different compatibility issues between versions. And what do they point out as a shining example as an alternative?

The way Poser has been released.

I thought I had found a bug in Poser Pro 2010. The library kept freezing, I found that if I richt-clicked it I could get the focus back and make sellections again. The I started having problems with the choices in the properties pallet. Finally, if I clicked something in the material room, an animation simulation would start up.

It turned out to be the mouse. That mouse works with every other program, but not with Poser Pro 2010. Maybe it is a Vista 64 problem, but I changed the mouse, and now Poser is behaving normally.

lmk

@Gareee  I realise they are a small team but from personal experience know the benefits of running my code on as many different machines as possible. At the very least they could see if there is something pervasive that has been overlooked.

As far as me being "greatful" for their kindness in releasing a beta... that is rather condescending and probably worth an apology.

poser pro 2010 is open to the public? where can i download it?

Quote - bagginsbill - So, what shader are you using on the bathroom? Glossy? Blinn? Are you using IDL? Could you post some renders, please?

Whichway

:laugh::laugh::laugh::laugh::laugh:

Whichway, if they gave out an award for the post of the day, week or month, this is it!!!

:thumbupboth:

Can picture the poor guy at the paint store and BB showing him some variations in Matmatic. "Look, just raise the diffuse by pi r squared....no, no, no, I wanted the R channel at 215, not 225"

I think we should make BB post a copy of his material room settings-shader set up for the wall paint too!

Quote - @Gareee  I realise they are a small team but from personal experience know the benefits of running my code on as many different machines as possible. At the very least they could see if there is something pervasive that has been overlooked.

As far as me being "greatful" for their kindness in releasing a beta... that is rather condescending and probably worth an apology.

I don't think its condencending at all, so don't hold your breathe waiting for an apology.

They have NEVER in the past EVER included the general public in beta releases. Perhaps you'd prefer they chose not to do it next time around?

Do you ever get included in beta releases of Photoshop? Nope. Vue? Nope. Companys do not HAVE to include the general public in beta developement. When they do, I'm always very greatful they included me, and want my feedback.

But I guess some people feel entitled.

There will always be people who get worked up about things not being done the way they would expect. That's human.

But I don't think SM needs to be defended at all. My answer would simply be: "No disrespect, but this is the way SM are managing it. Your option is to not participate."

My only request would be for SM to provide some visibility of the bug list, as they said they would. I don't mean every little code bug that gets sorted out quickly and without any fuss - just the big ticket items, and whether or not they have already been resolved.

There's no point in we Beta users reporting bugs in our original Beta release that have already been fixed in the latest test version. On the other hand, there is every point in reporting bugs that have not been seen yet -- but we don't know if they have or not.

I think the point of the public beta was to get initial bug reports from you guys... They have had quite some time to gather up the show stoppers, and I think that was the real point.

And I agree.. if you don't like how they are handling beta testing, don't participate, and just wait for the final release.

@Garee I did NOT in any way imply I was entitled. SM have extremely and very graciously deigned to offer existing owners of Poser Pro and Poser 8 to take part in their beta. I simply do not understand why, after doing us this exceedingly great honour, they don't use any of the probably quite valuable data that we are able to give them.

I have been involved in the software industry for 36 years now. I am quite probably able to submit a bug report as well as anyone and my feedback is probably in every way as good as you "professional" testers.

Don't bother replying. I am not monitoring this thread any more.