I'll bet that CL had no clue this was going on. I've sent something to their suggestions address about it, but based on past exerience I doubt they'll do anything. They say they go by frequency of complaint and I'll bet I'm the only guy that ever writes to them to complain about this sort of stuff. Frankly I wonder whether what I've written will ever even be seen by somebody that would understand what I was talking about. I only did the analysis after discovering that even when I was sure the script was working the way it was supposed to, I still couldn't get the right info into a pose for the EasyPose tube. It has exactly the sort of set-up I describe above, except that there are 47 intermediate SubMasters between the master bendAll dial and the xrot in the last body part, so the effect is.....rather noticeable. I could have probably saved myself a lot of time by thinking this through properly at the start, but at least I've learned a lot about Python so if I think of other cool things I could do with a script it won't take me so long next time. I'd rather not go as far as having the script read the cr2. If I have to do that, I might as well have a separate utility written in VB, which I probably will do now that I know Poser Python isn't going to give me a decent solution. In the mean time, I'll set up my script to just write the effective parameter values into the pose and write the valueParms as zero. It's ugly and it won't work if the ERC is driven by anything other than a valueParm, but it will have to do for now. I'm really very dissapointed. I just couldn't believe it when I realised they hadn't provided any method for reading a user's dial settings. Sigh. I wonder whether I'll have any better luck with DAZ Studio when it comes out.

View Ajax's Gallery - View Ajax's Freestuff - View Ajax's Store - Send Ajax a message