Sat, Nov 30, 5:36 PM CST

Renderosity Forums / Poser - OFFICIAL



Welcome to the Poser - OFFICIAL Forum

Forum Coordinators: RedPhantom

Poser - OFFICIAL F.A.Q (Last Updated: 2024 Nov 29 7:57 am)



Subject: V3 MOR pose problem: Dial values do not load


classic ( ) posted Sun, 23 February 2003 at 7:27 PM · edited Wed, 07 August 2024 at 12:12 PM

file_47424.gif

Everything in this MOR pose works fine, except the dial values for "Breast Gone" & "MP MuscleM" load up with a value of "0".

Can anyone see where I made my mistake? (see picture)

Interestingly enough, all the values for the head load up with their correctly.


Eric Walters ( ) posted Sun, 23 February 2003 at 10:59 PM

Hi Are you using Poser 4.01?? If so-upgrade to 4.03! That should fix it unless something else is wrong. BTW: I lose most of my injected V3 morphs in Propak Mac-latest upgrade/ Eric



classic ( ) posted Mon, 24 February 2003 at 12:15 AM

Thank you.

Sadly that can not be it, since I have the latest Curious Labs Service pack applied. But I appreciate the suggestion.


c1rcle ( ) posted Mon, 24 February 2003 at 1:33 AM

It could be you have them in the wrong order, MuscleM is the first injection line so that should be the first dial value as well, not the breast gone, try swapping them over.


Jaager ( ) posted Mon, 24 February 2003 at 2:05 AM

The order does not matter - you have to use the correct channel names for a pose file to work the name for the MP MuscleM is valueParm PBMDC_29 and for BreastGone is valueParm PBMBreastGone


Eowyn ( ) posted Mon, 24 February 2003 at 4:58 AM

I had the same problem before I realised the morphs were supposed to have the PBM in front of the name like Jaager said :)


classic ( ) posted Mon, 24 February 2003 at 5:11 AM

Thank you Jaager. Once I pluged in the corrected values it worked great.

Is there a table published somewere with the correct channel names for V3 morph dials? I was able to find some by tracing the ".pz2" to their "targetGeom" - but that was rather time consuming.


MarianneR ( ) posted Mon, 24 February 2003 at 5:40 AM

If I remember correctly there is an update to V3 Male Pak. Did you get that?


classic ( ) posted Mon, 24 February 2003 at 5:49 AM

"there is an update to V3 Male Pak. Did you get that?"

Yes, DAZ emailed me with a link to a full installer for the V3 Male Pack a few weeks ago.


Jaager ( ) posted Mon, 24 February 2003 at 6:42 AM

I just open the "inject" or, if you want small, "remove" files in a text editor, the targetGeom and valueParm names are there for individual morphs, but V3.cr2 for targetGeom and/or V3 BLANK for valueParms for the first two packs (they forgot to delete the valueParms from the BLANK). When you do the master dials in BODY, you need the valueParm names. As Anton said, DAZ is using up their extra channels, but the only way to know for male / set#1 is to look in the pose file in !DAZ, since their channel names are not even close to their dial names. I think DAZ should just provide a pz2 file with more slots and let users copy them in - rather than a new cr2 or raw morphs. Users who do not know how to use MM4 or MC to do a simple copy, sure aren't going to be able to convert raw morphs into inject/remove MIpose versions. And no character poses will work with these new ones because the names will be what each person decides to type in for shape1 - What you want to bet it will be the same name for everyone? Rob's new tool will automate all this character pose generation function. It will produce files that just inject relevant morphs with relevant keys, or relevant morphs and all keys. It will work off of a CR2/PZ2/FC2. The PZ2/FC2 are lightening fast, but if you set up a body the way you should = the matser dials in BODY, a pz2 is bloody useless, because Poser does not save valueParms (BODY dial settings) to a pose file, you must save a CR2 and extract it from that.


tasquah ( ) posted Mon, 24 February 2003 at 9:15 AM

.


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.