Forum Coordinators: RedPhantom
Poser - OFFICIAL F.A.Q (Last Updated: 2025 Jan 03 7:06 am)
Yes, memorizing a second time overwrites.
I made a multi-memorize Python once. It probably doesn't work in versions after 8, but you could try it.
http://ockhamsbungalow.com/Python/MemRes2.zip
And yes, Restore uses the InitValue (not the keys value).
My python page
My ShareCG freebies
I just checked out your scripts, ockham. Wow! Have you ever given any thought to updating some of them to Poser 9/2012, especially "Snap To", and "Variant on Snap To"? Those look extremely helpful.
The Old Phones you have on Share looks great. I was looking for something like that a few months ago, now I definetely need to re-do my image.
Quote - - Memorizing a second time will overwrite the values memorized the first time?
- The memorized values are reflected by the initValue Parameter in the cr2?
Both the above statements are correct. 'initValue' is also very important in conformers, as when an item is conformed its initial state appears to be set by the initValue(s) of the conformer, not its 'keys' (dial) values.
Q: Les, the conformer is the "cloth" or is it the "human" who carries it?
A: The cloth.
Q: I read today that conformed items should be zero-pose memorized. Is this what you are pointing out?
A: It relates closely to what I said.
Q: I wonder now, if zero pose memorization is the only way, why doesnt poser just ignore the memorized parameters of a conformed item?
A: I'm not sure why. Perhaps it was that it allowed you to apply an offset to a joint rotation of the conformer in a way that would not be wiped out by using the 'Zero Rotations' command in the Joint Editor. But that's just a guess. Another reason might be that an end user might save a conformer back to the library in a none zero pose, and if conforming were working off the 'keys' values, a none zero pose would mess things up. The Memorized state is less likely to be changed by the end user than the pose. Whatever the reason, Poser does not use the 'keys' values in the conformer for rotetions, the conformer gets its rotations directly from the target figure.
Quote - Les, the conformer is the "cloth" or is it the "human" who carries it?
I should add that the "human" is usually called the "conform target", or "target figure", or just "target" for short, when the context makes it clear what you are talking about. Also I sometimes use "character figure" and "conforming figure" to differentiate them.
I do not seem to manage to break a cloth by using memorize. Is there any easy procedure to break a conforming cloth in such a way that it wont be repaired by just using the zero pose function? Tried in PoserPro 2012. I tried to pose it, memorize, then conform. Looks odd. But zeroing it (without re-memorizing the zero thing) seemed to work in my special example.
Quote - I do not seem to manage to break a cloth by using memorize.
Experiment #1.
The following assumes that you have the P4 legacy content installed. Posette (the 'P4 Nude Woman') is memorized in a none zero pose, so we can use her to quickly confirm the hypothesis that a conformer should be memorized in the zero (or other planed) pose.
Load Posette, then load the P4 'Catsuit'. Instead of conforming the Catsuit to Posette, conform Posette to the Catsuit. You will clearly see that the conforming in incorrect.
Now unconform Posette. Zero Posette, and again conform her to the Catsuit. The conforming is still incorrect.
Unconform Posette. Zero Posette, and Memorize her (Alt+Ctrl+F). Now conform her to the catsuit. This time she conforms correctly. This is confirmation that a conformer should be memorized in the zero state.
Experiment #2.
Load Posette, then load the P4 'Catsuit'. Apply the pose 'Excercise1' to the Catsuit. You will find the Pose in the path:
RuntimeLibrariesPosePeoplePoser OriginalsGymnastic Pose SetsExcercise1.pz2
Memorize the Catsuit. Zero the Catsuit. Conform the Catsuit to Posette. The conforming in incorrect. This demonstrates that a conformer memorized in a none zero state will not conform correctly.
Quote - I tried to pose it, memorize, then conform. Looks odd. But zeroing it (without re-memorizing the zero thing) seemed to work in my special example.
The above step may fix the conforming (though I can't guarantee it), but the need for an extra step in order to fix it, proves that it was broken in the first place. Also the 'Zero Figure' function as implemented in P9/PP2012 does not exist in previous Poser versions ('Zero Figure' in P6 only zeros rotations). So zeroing the figure is a more lengthy process in previous versions.
In the above I have talked of memorizing the conformer in a zero pose, but this is not strictly correct. The conformer should be memorized in the pose that best fits it to the target figure, most of the time this is a zero pose, but not necessarily. For example the P4 Catsuit has the hip xScale Memorized at 105.2%. If you were to conform the Catsuit then use (P9) 'Zero Figure', the fit would be slightly different.
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.
Hi all, the memorize and restore functions that can be used on a figure, I would have a question: - One can memorize only once? Memorizing a second time will overwrite the values memorized the first time? Or is there even a multi-version memorization? - The memorized values are reflected by the initValue Parameter in the cr2? Thanks, col