odf opened this issue on Oct 27, 2008 · 13933 posts
lesbentley posted Tue, 11 May 2010 at 2:17 AM
Good question! I only spotted it because I was replacing the rotate channels for an experiment.
Nice job on the thumb JCM, a big improvement.
Quote - One thing I'm wondering about is whether I should retrofit the existing JCMs to be controlled not directly by their rotation channels, but indirectly through a channel in the body as I am doing here. This would make it very easy to reduce the strength of selected JCMs or turn them off completely in situations where they are not needed/wanted (as when they are covered by loose clothing and such). It would also make for shorter lists of dependencies when using P8's dependent parameter tools. Any thoughts from the experts?
I'm not sure that I'm very keen on that idea. I was going to sugest an alternative way, using valueOpTimes. So that's at least part of the answer to Amy's question.
Quote - lesbentley, what is the purpose of these tests? Are you going to utilize the "valueOpTimes" in something new?
I wanted to make sure valueOpTimes worked in D|S before suggesting you use it. It seems that valueOpTimes does work in D|S... sometimes.
Unfortunately I can't really recommend something I can't get to work reliably. Though it's probably just some stupid mistake I am making. I think I know what was causing the the problems with valueOpTimes in P7+ and have the answer to that one, but I am still uncertain about the problems in D|S. My "Pyramid_2.cr2" seemed to work for for P7, P8, and D|S 1.7.1.9, no one reported whether that version worked in D|S 3. A later version "Pyramid_3A.cr2" meant to track down the bug, did disclose the cause of the problem in P7+, but did not work in any version of D|S.
For anyone interested in my valueOpTimes method of turning JCM off and on, you can try the file attached above. This is the same file that is in my "APUtilityPoses" and available from the Antonia's Free Stuff site.