Rigacar for Blender - part 1: generate car rig 

my bad, i thought i have to unzip to install .py, works on 2.9 perfectly now

@@exitsalidaexit You just saved my life

You goofy lmao

@@martinmorillo7396 duuuude ahahaha i was hopeless, but i realized this when i installed this other add-on ahahahaha

@@exitsalidaexit why are you doing that pls i’ m blocked this add-on doesn’t work in blender 2.9.3 pls help-me

Found the problem, needed to set the origin to the centre of each wheel before creating the armatures.

Exactly, rigacar uses the center of the object as the position for the head of bones. This is particularly useful to indicate position for the body and the front wheels.

@@digicreatures1945 cool thanks. I'm currently trying to use this to rig a railway RRV. Besides the normal 4 wheels, the RRV has wheels which raise up when not in use. I notice the rig only has one set of brakes for all front and all back wheels. Is there a way to independently brake the extra wheels so they don't spin when raised?

You're right. The generated rig has only one brake for front wheels and one for back wheels. At the time, I didn't expect to have model which would need more. Obviously I were wrong. I will think about having independent pairs of wheels for future release (especially the 2.8 version). Meanwhile, I can figure out two different solutions : - Create two armatures. One for the extra wheels and one for the main model. You can parent root widget of one rig to the root widget of the other rig - More advanced solution : activate layer 15 of the armature to display mechanical bones (MCH). For each wheel bone, add a "limit rotation" constraint on the X for local space. You can then control the influence of this constraint from 0 to 1 and have additional brakes. You can even add driver to control the influence of the 4 wheels at the same time. I suspect this solution will not be 100 % accurate but it prevents you from creating two armatures.

@@digicreatures1945 Brilliant, thanks for your help.

Check the position of the 3D Cursor when you add the deformation rig. Not sure it is related to your problem...

hard to learn, easy to master, tedious to implement

not_ herobrine definitely agree with you.

Same here, in 2023 ! Thank you a lot for making and sharing this !

@@skaze93 you are definitely right. 👍

Could you share a file please. It's impossible to find out any solution without any information. You can open an issue if you have time : github.com/digicreatures/rigacar/issues

Take a look at part 3 of this series... ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-MN6CXG83Wdw.html

For the spinning, Rigacar can bake the animation for you (no need for adding driver). Please take a look at part 3 of this series and you will learn how to do it with Rigacar : ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-MN6CXG83Wdw.html

same

welp just found a fix for it you have to parent the 1 wheel to its corensponding bone

make sure that the object origin is set to geometry for the wheels

@@HarmfulBacon True. Thanks.

Yes you're right, it's the brake caliper. I use wheel brake as a generic term for all pieces attached to the wheel but which do not spin. I agree, this can be confusing.

of course it is possible, that's the main purpose. No need to parent the wheels to the body (actually body and wheels will be parented to the armature by the addon). Just create separate objects and follow the naming convention to be sure rigacar will be able to identify each part of your model.

I do de mon mieux :)

@cervidae submitted this solution for camber angle If anyone has camber on their car you have to make the following change: 1. Make sure your wheel is set to not have any camber and that its Y rotation is at 0 2. Go to layer 32 of the armature 3. Select the biggest green bone on a wheel and select "bone" from the context menu 4. Change Y rotation to whatever you want your camber to be (for me that was 7.5 degrees)

Not sure to get the situation. It seems you have activated "wheels on y axis". If you want to correctly animate the wheels, take a look at part 3 of this tutorial and use "Bake wheels rotation"

Check the origin point of the wheels. it should probably not located at the center of the wheel. You should move them at the right place and create the rig again.

Figured out my solution: it actually did generate ground sensors for the right side but they were located in the middle of the model and they were too large. When I tabbed into edit mode and adjusted these bones, the rig works great.

As you have already noticed the origin point of the armature is between the back axle. Why? Because when you want to animate a bone along a curve, Blender uses the origin point of the armature to position the rig (and not the bone attached to the curve). Having the origin point between the back axle is the best position to have realistic animation along a curve. If you take a look at part 3 of this tutorial, you will see I recommend to check and fix the offset position when using a follow curve constraint. At that time, Rigacar didn't change the position of the armature during the generation but now the position is always correct by default. The little jump forward comes from the origin point of the generated armature is positioned at (0, 0, 0). For any armature this is highly recommended (especially if you link your rig as an external asset in your scene). Otherwise, the position of the armature is used as an offset in your animation, which is almost never a good idea in animation. To summarize, Rigacar tries to create the armature in the ideal state to be ready to animate. By the way, you have an option when you generate the final rig to not change the position of your model (so you won't have the jump forward effect). This can be useful but only in very very limited cases. I recommend not to use this option if you don't really need to.

@@digicreatures1945 Oh, i didn't see the "Move origin" option when i generated the rig and was confused, because here in Part 1 your car didn't jump forward, when you generated the rig. Thank you very much for the detailed reply!

Probably there should have some errors in the name. Can you copy/paste exactly some of the names to let me double check.

@@digicreatures1945 Hi, thank you. I fixed the problem I didn’t use the car name in front of naming cause I had a downloaded project already rigged with the add-on and there wasn’t also the car name in naming so I thought it is not necessary to have it, but after I renamed my parts as your documentation suggests it works for me. Thank you!

Check the origin point of your objects. Also unparent the body and the wheels if there is a relationship between them. Rigacar remove the relationship automatically to parent them to the armature. In some cases, this operation could cause objects to be moved in the scene.

@@digicreatures1945 aha! thanks for answer! i solved it too by manually dragging the body back to original point works too :D

@@digicreatures1945 oh, btw.. "check the origin point" , my car all object parts origin point is at the ground center. is it right or i should apply "origin to gemoetry" for all parts?

yes it works, I have usually created this kind of model to test features. You should just pay attention to the name of each object and their origin point.

Can you make quick tutorial on car rigging with latest blender 2.8 x version . Please !! Can I mail my car blender file to you?? If you don't mind.

There are in the toolshelf panel. Press N to make the side bar appear.

Ground sensors are just bones with shrinkwrap constraints. So you can add as many constraints as you want and animate the influence. But you could also create a fake ground object (this object is not rendered). This way you have only one object (no need to add extra shrinkwrap constraint) which follow the overall shape of the ground.

Thanks a lot for your reply ... Be patient to me , I'm a beginner I apply what i understand from you i add a new bone constrains on every ground sensor bone . which target to the second ground ( new plan mesh ) But it doesn't work ?? .:: Another Question ::. what if i have my ground is not a plane if it is a cube mesh for example ?? i have a problem with any think not a plane for ground ??!! again thanks a lot for your works

thanks i apply solution and change the Shrinkwrap type to project and it is works and works with cube mesh

Good news! The good solution is probably what works for you! For complex scene, consider also using fake ground object. This way, you can have more control over the sensors.

Sorry for that. Try to read the online documentation digicreatures.net/articles/rigacar.html Or look for other tutorials on RU-vid. Maybe you will find one more useful and also more recent. ru-vid.com?search_query=blender+rigacar+tutorial

only CPU, RAM and GPU are the limit.

Nope

Take your time to learn modeling in blender. All the things you described can be handle quickly once you know how to do them. You can use group instances ou object instances to avoid duplicate wheels. You can separate part of your mesh by using the separate operator (shortcut P when you are in edit mode).

Check the origin point for each wheel. It should be at the center of the wheel.

Other people start to publish updated tutorials. Take a look here ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-JMTAZ3eadgU.html

Thanks. Glad to be useful. If it's possible, don't hesitate to share your videos...

It's not a bug, it's a feature. For most cars, it as a good idea to have the origin point of the armature in the middle of the front axle. But for animation, it is recommanded to have the origin point of the armature at location (0,0,0). Take a look at part 3, I used an old version of rigacar and I have to manually adjust the origin. Now the addon put the origin point at the right place by default and move the armature to place it at the center of the scene. It is the optimal position before starting any animation.

You need to do this 10:25

Check the reference objects (wheels, body and brakes) are not parented before adding the rig.

To avoid this effect, you have to be sure the center point of each wheel is at the center of the wheel. Ideally it should be at the same position as the head of the deformation bone of the wheel. I don't know why but you have this issue only when you activate the motion blur.

@@digicreatures1945 thanks for replying (and creating this thing). I did exactly that yesterday and, yes, it did solve the error. I use your add-on all of the time. It's perfect!