@F_Verbaas It would be great if your team would consider adding phonemes/visemes to PE's head/face controls so she could work with the talk designer. There are only 12 or so unique phonemes/visemes that are needed.
@Ken1171 - if you look in Materials/Poser 11 Content/Superfly Tileable/!Guide you'll find guides for setting up Physical Surface with Spec/Gloss & other workflows as well as Metal/Rough, so it is quite adaptable.
FYI from the latest SM earnings call: "Lastly, on to our graphics group. Fiscal 2017 was all about rebuilding, rebranding and reengaging with a significant and diverse customer base our graphics products attract. I am pleased with this significant progress that was made in 2017 as we maintained a very profitable business unit while rebuilding it from the ground up. "
My wish list would be full body and full head morph to rival genesis head and body morphs, released at the same time as the program or figure. If you want content providers to spend time developing content, people need to use the figures. They don't use the figures from poser because no one makes morph packages and the couple of morphs that come with each figure don't amount to anything worthwhile. Not everyone is an expert user, some of us just like to play and knock out a semi reasonable image, spin dial shaping is what we want.
From what I see, Daz gives a free program, free base figures. then sells the pro packages. If you buy a couple of pro packages, you have paid a similar price to Poser Pro. The only thing you don't have with Poser for the same price is the morph packages.
I prefer to use Poser for my renders and I like the walk generator as it is so much better than Daz's animation blocks, which again rely on content developers and money to buy.
So I don't see the point of isolating macOS. Maybe Apple considers that macOS users are captive and will not move, and therefore developers will be forced to develop games/etc... for two APIs even if that means increased costs for them. Really fascinating move.
I'm like every other creative type - I am planning my transition from OSX to Windows. A MacPro 5,1 makes a helluva windows workstation.
@Zaarin I'd like to see that done again but this time try to add the beard using the hair room, I've played with it from time to time but my results have been less than stellar when it comes to short beards or the 3 day growth look.
Good idea, but I'm allergic to the hair room... ;) I have tried Mec4D's Unshaven (the original one for Genesis) exported from DS, though, and it looks good (as long as you keep the expression pretty minimal). And I think I have a couple hair room beards floating around somewhere, like the one by Brahann--though that's a little more bushy. When it comes to light stubble, though, I think it generally looks okay to just use painted textures + EZSkin, as long as the bump map is decent.
@amethystpendant Yes, those outfits are amazing. I really love them. Not easy to wear, they are heavy, compared to our modern outfits, rigid, stiff ,the corset was a pain, even when it was not so tight, but make difficult to turn and bend. But I really love them because so beautiful made. Hope we will have another opportunity to wear them again :)
I think for this outfit you need to rig one part. The corset with laces and the whole top part.
Only the skirt dynamic.
@barnardino Yeah, we pretty much are. I can control the selected actor, as I do with my duplication. That said, that was one of the more tricky parts of my script, because of Poser's random behavior.
Mind, I still haven't tested ProcessCommand() to see if it works. It's logical that it will given that deleting with the GUI works, but given I can't even begin to fathom what went wrong with the update to cause this problem, I'm not betting on anything.
I, too, am concerned about existing scripts. This is an entirely fatal error. If it just didn't work, that would be bad enough, but it fully crashes Poser. I had to debug this, but normal people will probably just avoid those scripts like the plague if they encounter this problem. IMHO, it makes the script look dicey. I mean, I would expect a script that completely crashed Poser after an update to be doing something really klugey, overly complicated, with a whole bunch of erroneous assumptions. I wouldn't expect the problem to be just using a common officially documented method.