Thu, Jan 9, 10:35 PM CST

Renderosity Forums / Poser - OFFICIAL



Welcome to the Poser - OFFICIAL Forum

Forum Coordinators: RedPhantom

Poser - OFFICIAL F.A.Q (Last Updated: 2025 Jan 09 3:46 am)



Subject: BUG or FEATURE? Spawning new morphs via .pz2 Files, no .PMD needed!


pikesPit ( ) posted Sun, 06 November 2016 at 1:15 PM ยท edited Mon, 30 December 2024 at 4:10 PM

Greetings,

this is something which I stumbled upon by accident.

In former Poser versions, when you injected a morph which didn't have it's own channel in the figure, the injected morph would usurp the first "targetGeom" in the figure, replacing it with it's own morph data.

An example:

You create a morph injection .pz2 for the V4 head actor and call the morph "PHMPeterLorreEyes".

It looks like this:

{
    version
    {
        number 10
    }
    actor head
    {
        channels
        {
            targetGeom PHMPeterLorreEyes
            {
                name Peter Lorre Eyes
                initValue 0
                hidden 0
                enabled 1
                forceLimits 1
                min 0
                max 1
                trackingScale 0.02
                keys
                {
                    k  0  1
                }
                interpStyleLocked 0
                indexes 5612
                numbDeltas 15078
                deltas 
                {
                    ### (Morph Data here)
                }
            }
        }
    }
    figure
    {
    }

}

In a standard V4 with the "Morphs++" package added, this would give you results as follows:

In PP 2012,

it would replace the morph data of the first "targetGeom" found in the figure (targetGeom PHMHeadHairShort in this case) with it's morph data, rename the channel, and it would appear in the "Morph" group because there was no other group specified.

In PP 2014,

this would create a new morph channel (!) to appear in the "Morph" group because there was no other group specified.



So, if this is a feature of PP 2014 indeed:

it would make "PMD" injections of new morphs superflous. Just create new morphs, inject them with a .pz2 file, and you're done.

Incredible flexibility!

Now you could even just delete all the empty "Community Channels (PBMDC, PBMCC)" from V4 and make the figure a bit more light-weight. If you inject a character morph which uses the now-deleted "community channels", the morph will be created "on the fly" instead.


Please, can anybody confirm that this is indeed a new feature of Poser? I'm still on PP2014 10.0.3.26510 (later SR's didn't do me good, and P11 won't work in Windows XP).

Thank you!

Peter



Boni ( ) posted Sun, 06 November 2016 at 4:42 PM

Great tip, thank you for sharing this.

Boni



"Be Hero to Yourself" -- Peter Tork


pikesPit ( ) posted Mon, 07 November 2016 at 4:45 PM

Thank you Boni,

but that didn't really answer my initial questions:

  • Is this a new feature of Poser?
  • Does it still work in Poser versions after PP2014?

IF so, it might become a new standard for morph injections, and it would be an incredibly amazing feature. However, "IF* this was just a "coding accident" which went away again in SR x.whats.its.number, then it would be utterly useless.

Think of content creators, and how easily they could develop new morphs. Not just for figures, but it could be done for any content - hair, clothing, even props to parent to a figure.

But there's more: No more need to worry for "channels" in third-party clothing: Just create a morph for a particular piece of third-party clothing, select the piece of clothing, and click. WOW!


Thus, I do repeat my question:

Does this feature still exist in PP2014 past SR3, and in subsequent Poser versions?


Thank you!

Peter


Boni ( ) posted Mon, 07 November 2016 at 5:06 PM

I will research this.

Boni



"Be Hero to Yourself" -- Peter Tork


Privacy Notice

This site uses cookies to deliver the best experience. Our own cookies make user accounts and other features possible. Third-party cookies are used to display relevant ads and to analyze how Renderosity is used. By using our site, you acknowledge that you have read and understood our Terms of Service, including our Cookie Policy and our Privacy Policy.