Rigify UI doesn't show when linking in more than one character #51729

Closed
opened 6 years ago by RubenLopez · 14 comments

Partially related to blender/blender#29501 . See that one for context on rig_ui.py.

Steps to reproduce:

  1. Create two blender files with two characters using rigify.
  2. Create a third blender file and link the objects for both characters
  3. Link also the rig_ui.py script of both characters (since it includes the ID of the rig)

Expected:

  • Two animatable characters with their rig UIs to conveniently enable IK/FK controls

Actual:

  • The rigs work, I can manipulate their controls and they do what they are meant to do.
  • I tried linking the script once or multiple times. Regardless, I only get the rig UI in one character, not the other.
  • I tried appending the characters instead of linking them and got a different behavior, only the script for the first character I append is working. Others' are ignored.

Note:

  • I also tried creating two rigs on the same scene with rigify, to see if the behavior was different, but that doesn't seem to work. The second rig deletes the first one.

Configuration:

  • Blender 2.78 - Ubuntu 17.04 - GeForce GTX 1050 Ti
Partially related to [blender/blender#29501 ](https://developer.blender.org/T29501). See that one for context on rig_ui.py. Steps to reproduce: 1. Create two blender files with two characters using rigify. 2. Create a third blender file and link the objects for both characters 3. Link also the rig_ui.py script of both characters (since it includes the ID of the rig) Expected: - Two animatable characters with their rig UIs to conveniently enable IK/FK controls Actual: - The rigs work, I can manipulate their controls and they do what they are meant to do. - I tried linking the script once or multiple times. Regardless, I only get the rig UI in one character, not the other. - I tried appending the characters instead of linking them and got a different behavior, only the script for the first character I append is working. Others' are ignored. Note: - I also tried creating two rigs on the same scene with rigify, to see if the behavior was different, but that doesn't seem to work. The second rig deletes the first one. Configuration: - Blender 2.78 - Ubuntu 17.04 - GeForce GTX 1050 Ti
Poster

Changed status to: 'Open'

Changed status to: 'Open'
Poster

Added subscriber: @RubenLopez

Added subscriber: @RubenLopez
mont29 commented 6 years ago
Owner

Added subscriber: @mont29

Added subscriber: @mont29
mont29 commented 6 years ago
Owner

Well, if both use same py script name, I would not expect this to work indeed, even less if it is not possible to create to Rigify rigs in same local file…

Not sure whether this is known/intended limitation or actual bug, but seems to be a Rigify issue, not really Blender/linking one.

Well, if both use same py script name, I would not expect this to work indeed, even less if it is not possible to create to Rigify rigs in same local file… Not sure whether this is known/intended limitation or actual bug, but seems to be a Rigify issue, not really Blender/linking one.
Poster

Thanks for triaging so quickly. Agreed, it seems to be a Rigify issue. I certainly hope it is not a limitation (it is not documented). It is quite common to have shots with more than one character on them.

Thanks for triaging so quickly. Agreed, it seems to be a Rigify issue. I certainly hope it is not a limitation (it is not documented). It is quite common to have shots with more than one character on them.
LucioRossi was assigned by mont29 6 years ago
mont29 commented 6 years ago
Owner

Added subscriber: @LucioRossi

Added subscriber: @LucioRossi
mont29 commented 6 years ago
Owner

@LucioRossi think you are the one to answer here too? :)

@LucioRossi think you are the one to answer here too? :)

Added subscriber: @icappiello

Added subscriber: @icappiello
Collaborator

there's more than a issue here.

  1. automatic linking of ui the python script.
  2. rig_ui.py should have a unique name for each character
  3. multiple rigs generation in the same file

It should be all fixed in rigify 0.5. In the while you can manually make it work:

automatic linkingafter rig generation, select the armature in object mode, then switch to the 'game logic' window layout. With the rig still selected, under 'controllers' click on 'add controller' and select 'python' from the dropdown menu. Then select the character's rig_ui.py as script input. Save the file.
From now on when linking the character in a new file blender is forced to autoload the ui.py along with the rig. Just link the rig in a new file, save it, reload and should be ok.

unique rig_ui.py script name
simply go in the text editor and rename each rig_ui differently. You can just pre-pend the character's name like: character-one_rig_ui.py. Save the blend file.

If you switch to new rigify rigs (formerly known as pitchipoy) you will benefit of advanced generation options features in rigify 0.5 that's included in blender 2.79.

Let me know if this helps.
Cheers,
Ivan

there's more than a issue here. 1) automatic linking of ui the python script. 2) rig_ui.py should have a unique name for each character 3) multiple rigs generation in the same file It should be all fixed in rigify 0.5. In the while you can manually make it work: ***automatic linking***after rig generation, select the armature in ***object mode***, then switch to the 'game logic' window layout. With the rig still selected, under 'controllers' click on 'add controller' and select 'python' from the dropdown menu. Then select the character's *rig_ui.py* as script input. Save the file. From now on when linking the character in a new file blender is forced to autoload the ui.py along with the rig. Just link the rig in a new file, save it, reload and should be ok. ***unique rig_ui.py script name*** simply go in the text editor and rename each rig_ui differently. You can just pre-pend the character's name like: *character-one_rig_ui.py.* Save the blend file. If you switch to new rigify rigs (formerly known as pitchipoy) you will benefit of advanced generation options features in rigify 0.5 that's included in blender 2.79. Let me know if this helps. Cheers, Ivan
Collaborator

Changed status from 'Open' to: 'Resolved'

Changed status from 'Open' to: 'Resolved'
icappiello closed this issue 6 years ago
Collaborator

closing the tasks as resolved since rigify 0.5 addresses all 3 issues.

closing the tasks as resolved since rigify 0.5 addresses all 3 issues.
Poster

The workaround works great, thanks! Also, I'll use pitchipoy for new characters until 2.79 is out.

The workaround works great, thanks! Also, I'll use pitchipoy for new characters until 2.79 is out.

Added subscriber: @karlisstigis

Added subscriber: @karlisstigis

Thank you very much, I will try that!

Thank you very much, I will try that!
Sign in to join this conversation.
No Label
good first issue
legacy module/Animation & Rigging
legacy module/Core
legacy module/Eevee & Viewport
legacy module/Grease Pencil
legacy module/Modeling
legacy module/Nodes & Physics
legacy module/Pipeline, Assets & IO
legacy module/Platforms, Builds, Tests & Devices
legacy module/Python API
legacy module/Rendering & Cycles
legacy module/Sculpt, Paint & Texture
legacy module/User Interface
legacy module/VFX & Video
legacy project/2.81
legacy project/2.82
legacy project/2.83
legacy project/2.90
legacy project/2.92
legacy project/2.93
legacy project/3.0
legacy project/3.1
legacy project/3.2
legacy project/3.4
legacy project/Add-ons (BF-Blender)
legacy project/Add-ons (Community)
legacy project/Alembic
legacy project/Animation & Rigging
legacy project/Asset Browser
legacy project/Automated Testing
legacy project/BF Blender: 2.8
legacy project/BF Blender: After Release
legacy project/BF Blender: Next
legacy project/BF Blender: Regressions
legacy project/BF Blender: Unconfirmed
legacy project/Blender 2.70
legacy project/Blender Cloud
legacy project/Code Quest
legacy project/Collada
legacy project/Compositing
legacy project/Core
legacy project/Cycles
legacy project/Datablocks and Libraries
legacy project/Dependency Graph
legacy project/Documentation
legacy project/EEVEE & Viewport
legacy project/Freestyle
legacy project/Game Data Conversion
legacy project/Game Engine
legacy project/Game Physics
legacy project/Game Python
legacy project/Game UI
legacy project/Geometry Nodes
legacy project/Good First Issue
legacy project/Grease Pencil
legacy project/Images & Movies
legacy project/Import/Export
legacy project/Infrastructure: Blender Buildbot
legacy project/Infrastructure: Blender Web Assets
legacy project/Infrastructure: Websites
legacy project/Modeling
legacy project/Modifiers
legacy project/Motion Tracking
legacy project/Nodes
legacy project/Nodes & Physics
legacy project/OpenGL Error
legacy project/Overrides
legacy project/Papercut
legacy project/Physics
legacy project/Pillar
legacy project/Pipeline, Assets & I/O
legacy project/Platform: Linux
legacy project/Platform: macOS
legacy project/Platforms, Builds, Tests & Devices
legacy project/Platform: Windows
legacy project/Python API
legacy project/Render & Cycles
legacy project/Render Pipeline
legacy project/Sculpt, Paint & Texture
legacy project/Straightforward Issue
legacy project/Text Editor
legacy project/Tracker Curfew
legacy project/Translations
legacy project/USD
legacy project/User Interface
legacy project/UV Editing
legacy project/VFX & Video
legacy project/Video Sequencer
legacy project/Virtual Reality
papercut
Priority › High
Priority › Low
Priority › Normal
Priority › Unbreak Now!
Status › Archived
Status › Confirmed
Status › Duplicate
Status › Needs Information from Developers
Status › Needs Information from User
Status › Needs Triage
Status › Resolved
straightforward issue
Type › Bug
Type › Design
Type › Known Issue
Type › Patch
Type › Report
Type › To Do
No Milestone
No project
No Assignees
5 Participants
Notifications
Due Date

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender-addons#51729
Loading…
There is no content yet.