Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
...I guess a less technical way to say it is that when selecting a controller on a rig (The Boris Rig, for example), the script seems to add in a previously unkeyed attribute of that controller. In my case, when trying to transfer the animation of my Boris Rig's jaw control from one rig to another, the ScaleX channel was somehow magically keyed by the Transfer script and set to a value of 0 (zero). The jaw in both scene files never had any of the scale attributes keyed and were at a default value of 1 (one) prior to applying the saved animation. In order to fix this, I ended up having to break the connection that was created by the transfer script and manually set the channel back to its default value. I'm not sure if this problem is rig specific or not. Also, to reiterate, only one controller was saved and applied during this experience (the jaw controller); no other controllers were selected during the backup/transfer process.
lowlight
