byAnton opened this issue on Apr 18, 2005 ยท 5 posts
byAnton posted Mon, 18 April 2005 at 6:41 PM
Hello, Backstory: For those who don't know. The sensitivity of a dial is determined by Tracking scale. However with morphs, changes in Poser last only for that session. Everytime you load a cr2, it will randomize the sensitivity(TrackingScale) for all TargetGeom dials. That sucks and it still exists in P6. Makes Anton sad. with one exception..... the binary morph thing seems to have custom code that sets sensitivity consistantly to .02 which would seem like a fix but without binary lines in the cr2 it goes back to randomizing the tracking scale values for TargetGeom. Now you would think they would have fixed it. :( I tried a readScript to reset the trackingScale but it won't work. Anything short of Python, has anyone had any luck? Anton PS: Any P6 beta people, pleae try to get them to fix Poser so it doesn't randomize sensitivity on loading the cr2.
-Anton, creator of Apollo Maximus
"Conviction without truth is denial; Denial in the
face of truth is concealment."