Hello! I’m working on a custom rig and wanted to use the mGear RBF manager to help with a skirt. When I have multiple driven controls and set a pose, it saves the value of the first driven control, but then also takes that numerical value and puts it on every controller.
Here is a link to a video: https://drive.google.com/file/d/1ep02_P8sIXcfYT6KqpLn5TXJGlxNGL6Z/view?usp=drive_link
Any assistance would be greatly appreciated! Thank you 
What if you change line 719 in /release/scripts/mgear/rigbits/rbf_manager2/rbf_manager_ui.py in refreshAllTables() from:
for rbfNode in self.currentRBFSetupNodes:
to
if drivenWidget.rbfNode in self.currentRBFSetupNodes:
rbfNode = drivenWidget.rbfNode
It looked like the tables were getting set from the first rbfNode, and were not updated.
Sorry for the delay, tried that out, seems to still not work but for a different reason. The values are no longer duplicated across all driven, but now the driven value just never reaches the pose. Visually it just jiggles around 0. First object in the driven list still works tho! Pretty strange lol
Creating RBFs is often tricky and sometimes “fails inexplicably”… What you showed in the video, though… the way you add the poses, might not be the best way to use the tool, definitely not the way I do. Although logically correct, I don’t think it is supported. My approach to setting them up is way more cautious, adding one by one, and exporting the setup each time I manage to get one done.
So combining Chris’s fix with his other fix here: Bug: RBF Manager 2.0 reorders driver attributes after RBF Node creation
solves it! I can now add as many driven nodes and it will save all the poses properly
I should have done that, I was trying to follow an Mgear video from 8 years ago, which is probably outdated by now! https://www.youtube.com/watch?v=VyWCaE-YOwk
I never experienced that issue before when the connection order is wrong. Is @Miquel aware of this “bug”?
