Jump to content

BretBays

Regular Member
  • Content Count

    54
  • Joined

  • Last visited

  • Days Won

    3

BretBays last won the day on January 16 2019

BretBays had the most liked content!

Community Reputation

41 Noble Beginner

4 Followers

About BretBays

  • Rank
    Cafe Ronin

Profile Information

  • First Name
    Bret
  • Last Name
    Bays
  • Location
    California
  • Website URL
    www.bretbbays.com

Cinema 4D Information

  • C4D Version
    R21

Hardware Information

  • CPU/GPU
    i dunno

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Are you using Parent Constraints in R16? They were refactored in either R19 or R20, and they don't import properly. You'd want to convert them to be a PSR constraint(ie make a null, at the location/orientation of the object with the constraint tag and put that null under the target object from the constraint, then switch it to PSR).r
  2. Yeah it was a newer feature for R21 I think. After I sent it to MAXON I think it got mucked with a bit(Or it could be entirely my fault I don't remember) and it introduced this priority problem.
  3. Well, the thing is, if you're using mocap(which is the intended use for that template) it was needed to work that way. If you're not using Mocap, then use the Advanced Biped rig. If you are using Mocap you could still do it by either parent constraining or psr constraining the IK controller to another object that you can treat as the IK control. Just make some object, and put the tag on the mixamo ik arm controller.
  4. It does not say when you get access to it. So as long as you are given access to the features of the upgrade within the upgrade cycle of your MSA there are fullfilling their side of the deal. I believe they had mentioned that it is available now for Subscribers, and will eventually be met for perpetual folks. The idea is that MAXON could probably do multiple releases in a year. During that time subscribers would get them as they arrive as a perk of being a subscriber and not 'owning' the software', and perpetual licenses would get the compiled upgrade at the end of the cycle. So it's not that you won't get it, it's that you won't get it right when it's available.
  5. There's no real easy way to do this, as different parts of the rigs would require different needs. So for Mixamo joints, it could depend on how the skeleton is handled. Usually only the root/hips has translate data on it. So that should be as simple as negating all the X value keys to go from left to right. Then it's a matter of mirroring the rotation values of the spine, and it would just take a little trial and error to figure out which keys to negate. Let's say rX is the bend forward and backward, rY is left/right and rZ is twist, you'd probably need to negate the rY and rZ channels on the spine. With the limbs, you'd want to basically swap the keys from one limb to the other, and then you'd have to do a similar trial and error of figuring out which keys to negate. When I say negate, you would select the keys of that track, and in the value field set it to be x*-1.
  6. If you are wanting to use XRefs, they can be problematic at times. What I would suggest is that when you create your Xrefs. There's a section on the XRef that dictates what you should be able to modify when something is referenced. Make sure Hierarchy is turned OFF. You shouldn't be able to change the hierarchy of a reference. You really only want to be able to adjust Coordinates, Parameters, and User Data. Doing it this way should give you some of the more stable qualities of Xrefs.
  7. What Everfresh said. I think you can just do it to 24. They're both set to 25, but their insertion is the problem. technically, it just needs to be above the bendy arm controller, but since that's not as easy to fix, just set it to 24
  8. To fix the issue in your scene just do the following: Switch to full hierarchy display mode. Locate the object called: L_Forearm_Bendy_algn. Also the right side so R_etc... The constraint tag that is on that object, set it's priority to 30 instead of 0. If you wish to fix this going forward, crack open the adv_biped.c4d template and make the change in there. Choose Character>Character Builder>Save Character Template. Then it shouldn't be there going forward, but this could get blown away on any new update, just as an fyi
  9. I think it got introduced in R20. It was either directly my fault(as some changes were made in R20), or it was someone at MAXON's who did some minor re-org of it after the changes were made, which introduced a priority issue. But I believe it's a relatively new issue. If you find the object that is lagging, it's probably the controller, which is driving the joints etc). If you were to adjust the constraint tag of the null that is driving the controller, make it like 1 number bigger, it might solve it. Otherwise ill need to crack open the file and check.
  10. Implementing a fix is hard, but I can tell you how to fix it. It's just changing one of the priorities of the constraint tags I believe. I don't have it in front of me though.
  11. Fwiw, you dont have to do the disabling step. Just click set bind pose and youll see it jump and be good to go. you can check for the issue by toggling the checkmark though. If it moves then theres an offset from the bind pose typically if youve bound them go back and readjust this will happen. Any adjustments made after binding would require you to reset the bind pose of the weight tag.
  12. Most people just don't understand them. They are pretty straight forward for the most part. The only time you run into sort of unsolveable issues is when you are trying to combine expressions with deformers. And that's really only an issue because you cannot set the priority of deformers. A lot of folks struggle because they start changing things willy nilly. Stick to Expressions, Use increments of 5 to give you extra wiggle room, and you can go quite far with very little hangups.
  13. Howdy, So I peaked at the file. A couple of things: I'd reccommend never putting stuff at generators priority level. There's really like...no point. Unless you're doing crazy junk, with sds' and like deformers then maaaaybe, but generally speaking, for a standard rig, you never need to leave Expressions mode. In general if everything is in Expressions mode, then it's just an order of operations thing. So it first looks at the priority number. If everything were at the same number, then it solves top of OM down. And then on an object, the tags would solve(i think) left to right. So assuming all the same priority number, you can fix lags by adjusting the OM order. But having said that, it's generally just not going to be as simple as that. Really, the simpler thing is to just adjust the numbers. That way Expressions 0 solve before Expressions 1, which solves before Expressions 2, etc. So, when I open your file here's what I did to remove the lag: 1. I moved the mesh and deformer below the rig itself. I think it's generally better to have the rig and everything above what you are deforming. 2. Switched the SplineIK tags from Generators to Expression When you do those two things, there's still a lag. The reason is because those tags reside under BD_Head_jnt. BD_Head_jnt has a constraint tag on it set to Expressions 60. Ok So 0 solves before 60. However, the positioning of the joints are a child of BD_Head_jnt. So right at this point the Behavior is Solving the SplineIK, Solving the head....which would put the splineIK not in the right spot. Hence the lag. So to solve it: 3. You can either Set the SplineIK tag's to Expression 60 or higher. So if it's set to 60, because it's below the head, when c4d solves everything in Expression level 60, it solves them top down. So even though they're both 60, Since it's under BD_Head_jnt, it will solve after it. Or you set it higher than 60 it'll solve after. Hope this helps and makes some sense.
  14. So, I made some of the stuff for what Brandon showed in that video. I was planning on making and releasing a new updated mixamo template in the character object that would give you IK or Mocap etc. Sadly, it's a complicate thing. I have fully FK rig controls you can use, but IK is harder to keep things matching. I have something that kind of works, but the elbows and knees are hard to keep in line with the mocap, and that's what's been preventing me from releasing anything. You can do it manually each time, but that's a pain in the ass. Just use local rotation constraints on the parents that drive the controllers and you have mocap driving your ik and such, but setting it up each time is the pain and that's what I have been hoping to alleviate but have not finished yet.
  15. You can bypass all of that by doing the IK tag on a chain of controllers instead of bones. The bind bones are constrained to the controllers. Then you can handle visibility between IK and FK by hiding or unhiding controls. Here's what I'm doing: https://www.dropbox.com/s/mv2jwd3lpvn20s9/IKFKTest.c4d?dl=0
×
×
  • Create New...