MNE opened this issue on Sep 11, 2022 ยท 43 posts
MNE posted Thu, 20 October 2022 at 9:32 AM
MNE posted at 5:24 PM Sun, 16 October 2022 - #4446809
JAFO posted at 6:40 PM Sat, 15 October 2022 - #4446732Poser 12 is not only about bug fixes, it's also about an inevitable migration to Python3,x, to compensate SmithMicro's desparing silence once they introduced superfly. It was a known fact that Python 2.x was about to die, and they let things evolve in the wrong direction. I'm calling this "irresponsibility"...I wonder how many of those who suggest Poser isn't being improved even bother to look at the change logs available with every update?
Seems those bellyaching haven't even upgraded. They all insist they're not upgrading because.... How can you present a valid argument against the current release without having tried it?
I started using POSER4 and upgraded to the last version of POSER 12.0.1029.And I think that POSER12 was all about bug fixes.So, in terms of improvements, it may have been accomplished.It is true that there are some optimizations in rendering and some improvements in the material room.However, I am talking about new technologies in 3DCG today.Since its launch, POSER has evolved with exciting new technologies with every update.However, POSER 12 has yet to support unimesh, although it was initially released, and there are many new technologies that have stopped the evolution of POSER in the last few generations, such as each system room, and the new technologies that are being realized in various areas.And the introduction of new technologies that have been realized in various areas.If you are satisfied with the current system, which has been in use for several generations, you may be fine.But those who love POSER and use it with several other CG applications are frustrated by POSER's delays.
Poser12 is also about some very welcome optimizations, noticeably in terms of superfly's speed, Cycles2 implementation instead of Cycles1 which had many errors.Unimesh? they're have been speaking of it for a long time, yes... But the idea is to avoid to break anything, so that it take time, even though if they seem relatively silent.
Same for a Cycles2 preview mode and quite deeply hiding bugs in that area, among them many assets are still crashing the couple Cycles2 + OptiX (I've a bug filed for some time now, and they're still opened)