Thanks folks.

@LostAlien, still in beta testing. Progress is being made. More details are Uh, sure to be forthcoming in due course and the fullness of time, moving forward. ;-)

I hope that we'll hear if anyone using Poser 11 has a really old macOS, like 10.9.5 Mavericks.

Hi RAGraphicDesign, you should be fine with 16GB RAM :smiling:

Watching this with interest.

I'm sure my horoscope was mistaken when it assured me I would be mugged in a dark alley by a group of former friends, and actually meant that I would be gifted a new Apple Silicon powered Mac during this calendar year :winking:

Hi RAGraphicDesign, that certainly seems plausible. Perhaps of more importance than just the CPU and clock speed are the amount of RAM and video card installed on your iMac.

Looking at the online lists, that looks like the CPU from an early 2013 15" MacBook Pro, rather than an iMac. In any case, just on that CPU alone, you should certainly be able to run Poser. Having more RAM will mean you can open larger scenes and render them easily. Render speed will be something that only you can judge, though :-)

Choosing About this Mac from the Apple menu will get you lots of information, but whether it's an iMac or a MacBook Pro, as long as you have the maximum memory that those systems can be expanded with, you will get their best results. For machines of that age, the RAM should be quite cheap, now, and can be user installed. I have two iMacs from 2011 and 2013, and have upgraded both to 32GB, which was completely painless.

If the custom morph on the head actor of V4 doesn't have any valueOperations (ERC) to control it from the Body, when it copies to the cowl figure, there may not be any valueOperations driving the copied morph.

Do you have Include morphs when conforming checked on the cowl? If not, you could add a valueOperation to it to follow the morph value on V4's head

This was in my inbox on 16th December 2020.

Beyond that, I have no information.

Yes, but you want an inverse square falloff of the amplitude with distance from the focus/centre. Or even a linear falloff. It just depends on what you want it to look like. If it looks right to you, then it's right. Just tell folks it's a non-newtonian fluid if they complain about variations from reality. ;-) If you use a math power node, you have infinite variability available by changing the exponent.

Indiana Jones was nearly killed by a Mystery Date! Tragically the poor monkey took one for the team :-( Bad Dates!

If a whole actor is being replaced with another rigged actor, even if there are mesh/geometry changes, Poser should still correctly handle the actor seams during bending, so no overlap should be required. Geografting in Studio effectively introduced new actor seams, even if there were no joint parameters directly affecting those seam vertices.

In Poser, provided the replacement actor is UVmapped exactly the same way as the original actor, at least for the identical vertices, then the appearance should be seamless.

Unless there is a drastic change to the Poser CR2/PZ3 file format, which removes features present for Traditional rigging, there should be no reason why a body part replacement with an actor containing its own mesh definition (not referring to a named group within the figure obj file) can't be done.

What Poser lacks presently, is any automated mechanism to transfer morph deltas to an unmorphed replacement actor. However, if the replacement has the majority of its vertices and facets in identical positions to those of the original actor, it is eminently possible to transfer morph deltas to the matching vertices via python script.

That could possibly be worked around by creating a dummy figure, whose only actor with geometry is the one which will replace an actor on the original figure. Conforming the dummy figure to the original, would then allow the Copy Morphs From feature to be applied. Identical vertices should get a very close match to the original deltas, while vertices further away from the original actor's surface will probably need some manual adjustment, in the same way that clothing does.

Maintaining vertex order and the mapping from the original figure's replaced actor to the replacement actor is difficult but certainly not impossible.

It will take some experimentation to see what the eventual internal unimesh Poser changes in how figures are handled and morphs transferred. Lots of things which are difficult now will hopefully be possible, if not actually easier when that change comes through.

Dreadfully late to this promising playground. My solitary contribution, with the sincere hope of avoiding offence (razor-wire or other), I give you:

Seal Seal Seal Seal

What version of Poser are you using? If you have Poser11, you should be able to select each hand and change individual scaling. If the dials are not visible, use Show Hidden Parameters.

It might help to see what render dimensions you're using, and whether that matches the preview window and the proportions of the background movie.

"sl 1" might appear to be an unused feature, as I've never seen anything other than 1 as its value, but it's probably related to layers in some way (which I never use), so you can ignore that. it may be possible to remove it altogether, but why bother? Perhaps one of the Poser developers could answer that question better.

"sm" is the smooth setting for the Spline Break function. The other possible value for it is "br", standing for Break, which stops interpolation of previous frame values affecting subsequent frame values.

The component between those two lines, for completeness, sake, is the interpolation type, supporting values of "con" for Constant, "lin" for Linear, and "spl" for Spline.

What's the feature of 3.8 you've used the most, @adp001? Walrus assignment, or f-strings? I can certainly understand the frustration of upgrading code to find out it's still not supported.