@kobaltkween Yeah, it seems to look that way. Personally, I have never agreed with their decision to make copy morphs a Pro-only feature. This makes no sense, since this is something we have to do all the time, since most clothing do not include all the morphs. There is also the fact that DS does it automatically, making this look overdue in Poser. SMS is not exactly in a position to remove things from Poser that should be there by default. In particular, this is not something related to content creation, but instead regular daily usage. Coming from that, last night I have asked SMS to rethink that idea. As a content creator, I have to be able to offer morph transfers from my product to the clothing. Since the standard Poser cannot do it, at least I should be able to get that from Python and add it to my product, or otherwise customers will be held hostage of the Poser version they own.
Yeah, this gets to my belief about their problem being who they've made Poser for and how they think it will be used. I still remember Teyon, who is both very talented and very kind, who listened to the community very well, suggesting a solution or idea that totally misunderstood the problem because he couldn't see the problem from the perspective of someone who doesn't make their own content. I wish I could remember the details to back my point, but the issue was that even though (because of his experience) he understood, for instance, the need for good UV maps, topology, and rigging, he couldn't see what an actual user who needed to use someone else's copyrighted works would need. And he was one of the best of them.
I totally get why they think of making morphs as content creation. But that's not really what you're talking about. You're talking about fitting clothes, which anyone who uses Poser will want to do.
Right now I'm working on a character, and it renders _so_ much nicer in Blender that I'd like to give away the Blender "materials." But to do that I'll have to write a Blender plugin to enable it, because Blender's concept of materials is essentially a combination of scene-wide material zone + node tree, where Poser's is just the node tree, with material collections being zone_names_ and trees. Because Blender assumes (correctly) that its users are pretty much always working with their own stuff or stuff they have full rights to. It has no notion of making add-ons for a particular commercial mesh, so I will personally have to create the means to save and apply a set of node trees to existing material zones.
The content community has unique needs, and therefore requires unique tools to support creating and using an interdependent content ecosystem. And while DAZ has been whole hearted in that regard for obvious reasons, the Poser team has inexplicably focused on both positioning themselves and selling themselves as primarily a professional tool while seeming to be financially dependent on the content community.
