![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
Some thoughts on Poser 6
May. 4th, 2005 01:03 am(For those of you who are not interested in computer graphics software, please feel free to ignore this post.)
For the entire lifespan of "Requiem" all of the people who walk through it's dysfunctonal universe have been created with a program called "Poser". "Poser" is just about the only program made that is dedicated to designing people in an artistic setting. IThink of it as "Identi-Kit" except with much better lighting. Overall version 5 (which I was using) was pretty damn good. Occasionally it would freak out on things, there would be problems with getting clothing to show up properly on people instead of having the skin poke through in odd spots, and some lighting issues here and there.
About a month ago, I made the plunge and upgraded to the just released version 6.
I am still trying to deal with it.
There are some great things that have been added to it here and there that lead me to believe that when the bugs are worked out it will be a hell of a moving unit. Complicated render settings (aka stuff with a lot of reflections) render faster...the computer actually seems to be using it's resources more efficiently. Heck, I've ran P6 with a 1.25gig swap file going and still been able to use other programs on my computer pretty good. Overall, I like it.
But there is a catch...and yes it is a hell of a big one. There is a major bug in it that has to do with how much memory gets allocated for files in it. Suddenly, a file that you have done in P5 is now unusable in P6 because you don't have enough memory. Right now, I am using a gig of ram in my PC...RAM should not be a problem, The good thing is that the makers of Poser know about this bug and are working on fixing it. The problem is that I have a schedule that must be kept.
7 comics a week, 21 panels total of Requiem, plus the weekly Renderosity strip, plus (hopefully) another issue of "Pryce" before I die or grow fucking senile.
And this bug just shows up and doesn't give any warning before it pops up the error message...and in the process sometimes burns hours of work.
So for now, I am back on P5 and waiting for the bug fixes for P6...It makes me sad really, P6 is so close to being perfect.
Oh and examples...the Vance Greylock section starting at http://erech.keenspace.com/d/20050328.html is all Bryce 5 and Poser 6
The Arthur/Leah section at http://erech.keenspace.com/d/20050323.html is all Poser 5 (and is a section I cannot do in P6)
And April 2 http://erech.keenspace.com/d/20050402.html until http://erech.keenspace.com/d/20050413.html is all Poser 6...until I found out that I damn near couldn't render out two chicks standing in front of a mother fucking car.
(There wull also be a few more P6 examples on DEVART tonight as well)
At any rate...if you are interested in Poser, my advice to you is to buy a copy of P5 (which with P6 out now) should save you some $...then when the first set of major bug fixes come out buy the upgrade to P6. When the bugs are fixed P6 will be wonderful...but as it stands now, I cannot recommend it from a reliable production standpoint..
For the entire lifespan of "Requiem" all of the people who walk through it's dysfunctonal universe have been created with a program called "Poser". "Poser" is just about the only program made that is dedicated to designing people in an artistic setting. IThink of it as "Identi-Kit" except with much better lighting. Overall version 5 (which I was using) was pretty damn good. Occasionally it would freak out on things, there would be problems with getting clothing to show up properly on people instead of having the skin poke through in odd spots, and some lighting issues here and there.
About a month ago, I made the plunge and upgraded to the just released version 6.
I am still trying to deal with it.
There are some great things that have been added to it here and there that lead me to believe that when the bugs are worked out it will be a hell of a moving unit. Complicated render settings (aka stuff with a lot of reflections) render faster...the computer actually seems to be using it's resources more efficiently. Heck, I've ran P6 with a 1.25gig swap file going and still been able to use other programs on my computer pretty good. Overall, I like it.
But there is a catch...and yes it is a hell of a big one. There is a major bug in it that has to do with how much memory gets allocated for files in it. Suddenly, a file that you have done in P5 is now unusable in P6 because you don't have enough memory. Right now, I am using a gig of ram in my PC...RAM should not be a problem, The good thing is that the makers of Poser know about this bug and are working on fixing it. The problem is that I have a schedule that must be kept.
7 comics a week, 21 panels total of Requiem, plus the weekly Renderosity strip, plus (hopefully) another issue of "Pryce" before I die or grow fucking senile.
And this bug just shows up and doesn't give any warning before it pops up the error message...and in the process sometimes burns hours of work.
So for now, I am back on P5 and waiting for the bug fixes for P6...It makes me sad really, P6 is so close to being perfect.
Oh and examples...the Vance Greylock section starting at http://erech.keenspace.com/d/20050328.html is all Bryce 5 and Poser 6
The Arthur/Leah section at http://erech.keenspace.com/d/20050323.html is all Poser 5 (and is a section I cannot do in P6)
And April 2 http://erech.keenspace.com/d/20050402.html until http://erech.keenspace.com/d/20050413.html is all Poser 6...until I found out that I damn near couldn't render out two chicks standing in front of a mother fucking car.
(There wull also be a few more P6 examples on DEVART tonight as well)
At any rate...if you are interested in Poser, my advice to you is to buy a copy of P5 (which with P6 out now) should save you some $...then when the first set of major bug fixes come out buy the upgrade to P6. When the bugs are fixed P6 will be wonderful...but as it stands now, I cannot recommend it from a reliable production standpoint..
