Ajax opened this issue on Aug 18, 2003 ยท 25 posts
Ajax posted Tue, 19 August 2003 at 7:57 PM
The memorise idea I had won't work because it seems that Poser Python doesn't have an methods for querying memorised values - just for restoring whole actors or figures. My aim is to provide an alternative to the usual pose saving interface that offers more options, including the ability to save poses which are ERC based. Currently in Poser, you can get a nice ERC based pose (such as a fully body morph or an EasyPose pose), but you can't save it. Poser completely ignores the valueParms and writes a pose that just sets all of your rotation dials to whatever setting they would have if ERC relationships were ignored and doesn't set the valueParm dials at all. This is useless and means that in general you can't save poses for EasyPose figures and you can't save FBM poses etc. I want to give users a way to save a pose exactly as they see it in their document window - but also allow them to leave out bits they don't want. For example, I've got checkboxes to let users decide whether or not to include translations or rotations of the Body, so they can make poses that do or don't position the figure in the universe. If they want, they can make a pose that will put the figure in a particular location without changing its posed body parts at all. I'll also let them decide whether they want scale dial settings to go to the file - so after you've morphed and scaled your figure to your ideal figure shape you can save a pose with just morph and scale information to recreate that figure shape any time you want. Ideally, I'd like the user to be able to save the pose exactly as it is, so if you have an FBM setting you want saved, say the FBM dial is set to 1 and all of its slave morphs are set to 0, it should be saved as a zero setting for each slave morph and a settting of 1 for the FBM dial. However, I guess an acceptable workaround would be to save each of the slave dial settings as 1 and not save the FBM, or save the FBM as 0. I'm not entirely happy with that approach, but it will do for the first version. In the longer term I'd like the user to be able to save a pose that will set all of the dials to exactly what they are shown to be in the user interface. The problem with the example you've given is that the equations aren't quite right. We should have: let a suffix of "P" designate the effective Parameter value as returned by Value() let a suffix of "D" designate the visible dial setting (which is what the pose will set) BodyP = BodyD ChestP = ChestD + (BodyP * 0.7) LeftArmP = LeftArmD + (ChestP * 0.4) Therefore LeftArmP = LeftArmD + (ChestD * 0.4) + (BodyD * 0.28) So you see there's no way to shortcut - you have to know every relationship in the chain :-(
View Ajax's Gallery - View
Ajax's Freestuff - View
Ajax's Store -
Send Ajax a message