- User Since
- Jun 24 2016, 1:06 PM (56 w, 6 d)
I can't conform that.
It could be related to some script running in background, or just a graphic driver issue.
@Lucio Rossi (luciorossi) @Brendon Murphy (meta-androcto) Can anyone else please confirm this is happening?
@adam earle (adamearle),
first, take in consideration that all the first part of your post is not a bug report. I could take it as a sort of design proposal. I'll take the time to answer anyway but please next time consider that a bug is considered something the program is explicitly meant to do and doesn't.
Sat, Jul 22
A Vertex Group doesn't appear until you click in the view port and the bone seems to have no weighting.
Mon, Jul 3
@Bastien Montagne (mont29) since 2.79 is going to be last stable build till the official 2.8 release, i thought it could be worth a look at this patch since, even if doomed, BI will stay as long as needed to make 2.8 stable. What benefit could come from not having a workaround for that issue in 2.79 as long as it doesn't break anything else?
@Paolo Acampora (pkrime), i remember you wrote for us a patch to fix that while we were rendering our animated feature GL previews. I think it's here https://developer.blender.org/T48983. @Bastien Montagne (mont29) We are stil using it in studio, even if rejected (and still unclear to me why) i think it could be at least a good starting point to address the issue, can you please consider it?
Fri, Jun 30
After a first look it seems something has changed in the way blender handles the snapping functions.
Thu, Jun 29
I can confirm the issue. Causes are still unclear. We are investigating right now.
automatic works as designed.
The option is on the limb. Just switch from automatic to the axis you want. default is X.
Jun 23 2017
hey @Brendon Murphy (meta-androcto) can you please have a look at this?
Jun 10 2017
closing the tasks as resolved since rigify 0.5 addresses all 3 issues.
i am closing this task as invalid since it was already reported, fixed and, after a double check on commits there's no trace of other issues introduced by recent commits.
I remember the issue. We never fixed that in legacy mode. Legacy mode is intended to maintain the legacy feature unchanged during the migration to new 0.5 code.
The reported issue is related to rigify's original design, we took care of it redesigning the rigs in 0.5.
there's more than a issue here.
May 29 2017
@Julien DUROURE (julien) with the next 2.79 release all your requests should be addressed. Have a look at the release notes and follow the upcoming wiki page to know how to use it.
May 15 2017
About the rig-id part:
Seems you are writing the rig-id on the meta-rig and then the meta-rig passes it to the rig. Even if the idea seems cool at a first glance, again, the consequence of this change are breaking other rigify features.
It seems you never generate again the rig-id on the meta-rig once is created. This is bad. Rigify metarigs are created to be shareable through blender files. For example, you have rigged your character with rigify, the next one is similar to the first, so you append your meta-rig form the first to the second file, then edit it as needed and generate. Standing to your patch in this case the metarig will bring in the second file the same rig id and - even not finding the rig itself - will always generate rigs with same rig-id. Since there is no rule to know when to re-create the rig id, you will force the user to manually delete it.
The idea behind the patch is good though.
I'll try to think a workaround for this second part, but for now -as this patch is submitted - I consider this part rejected too.
from a first look i have some big concerns about rigify WGT patch proposal:
looking into the patch right now.
This is fixed in 2.79. Now the property is moved to a visible bone laying at the base of the limb.
- New rigs created starting from 2.79 code will work automatically.
- Old rigs should be upgraded re-assigning the rigify-types property in pose mode.
Feb 8 2017
This is the metarig i re-created from the ORG-bones in your file. That's how the arm bone should be oriented to make it correctly work. You can restart from there.
on the the sample file i see more problems than you reported. Most of the controls are turned in the rest pose and there is a dependency cycle on the right leg. I suspect the metarig is misaligned or some modifications were made after the rig-generation.
I can see from the ORG-bones (that are the exact metarig copy) that your arms have bone rolls not correctly aligned. the Z-axis should point downward, in your rig instead is flipped.
You can go in the front view (numpad 1) select the arm bone-chain on the metarig and hit CTRL+N > Recalculate Roll > View Axis. Then regenerate the rig.
Jan 28 2017
@Luciano Muñoz Sessarego (looch)
please provide the blend file with the metarig that's generating the error. And a detailed description.
About the finger, have you tried to replace basic fingers with the pitchypoi super finger?
That should do exactly what you asked for.
Jan 27 2017
Not sure it's a complete solution tough.
Then if hand_fk is not visible the problem remains. I guess exposing a separate bone at the limb's first bone to handle all the properties is a better idea. This bone can be on both FK and IK rig-layer meaning it's always visibile if at least one of them is.
Will look further into that.
You can use the method you prefer. Rigify can make mixed rigs.
- Add Human-Metarig
- in edit mode add a sample face
- parent the face bone to the head
I can confirm the bug. Looking if @Joshua Leung (aligorith) 's fix is breaking something else.
Following those steps i can't reproduce this error on 2.78a. All DEF and ORG bones are on the respective layers and correctly displayed.
Jan 24 2017
We could have a fix that adds the feature you requested on the pitchypoi leg.
Jan 23 2017
@Julien DUROURE (julien)
I looked into the FK toe snap problem.
@Julien DUROURE (julien)
i will have a look at the standard rigify bug. But that part if the code is untouched since nathan coded it.
@Julien DUROURE (julien)
The firts 3 reports should be all grouped into a single thread since are all related.
Jan 22 2017
@Luciano Muñoz Sessarego (looch):
Yes all our work relies on the pitchipoy code.
@Luciano Muñoz Sessarego (looch),
All the major changes presented at the conference are already in master since 2.78.
Sep 22 2016
This is the commit of an urgent fix that will make the snapping functions work with new additions to the super_limbs:
Sep 12 2016
The feature suggested by @johan tri handoyo (johantri) is now committed.
Aug 20 2016
i tested your rig.
As i wrote in the previous post, this cant't work "out of the box" with rigify rigs.
Aug 19 2016
i maybe didn't understand well what was done on the rigging side on the garfield series, but i suppose it wasn't done in blender. About your method:
Jul 19 2016
adding the missing super_palm.py file.
@Campbell Barton (campbellbarton) @Nathan Vegdahl (cessen) the inherit scale modification is necessary to prevent undesired results after non uniform scaling on the hand control. If you want to check it just generate the rig leaving inherit scale values active, then rotate the hand and scale it non uniformly (ex: S Y Y) and you will see the fingers controls and deform bones exploding in all directions. Anyway our modification is applied to a new rig type with a different name. The old one is still there and will not be affected by the modification.