Hallo
I have an issue, stuff moves around (actually my "aim") in double speed. I do know that you (Wayne) mentioned in an earlier video that if we add something twice its behaviour acts weird.
I added the file to dropbox. I could not find out what it is. In my opinion everything seems fine.
do you mind take a look at this and give me a hint?
Hope you can help
kind regards
Martin
PS: I try to figure it out in meantime of course
https://www.dropbox.com/s/bvvhbttbw7t8dep/Turret_rig_START.blend?dl=0
Hi Wayne
(time11:41) you have a constraint on the base, so I think there should be one, yes.
My "recoil" is parented to the "body" and he is parented to the "base". the "base" is parented to the "root" and the "aim" to the "base". the "torret base" is parented to the root.... (short: all bones are parented to the base and the base is connected with the root)
At the beginning of you video, the turrets body was parented with the "turret base"... (object)
I followed all this but I have a mess when I move it...
I removed the constraint from the base but that made it worse... actually loosing it :)
when adding the locked track to the body the turret does not move at all any more... only the bones.
but I find it hard to explain everything ...
hope you know what I mean, thank you Wayne
Hi Martin, don't know if this is helpful to you ( I don't understand most of it), but your Console gives some information that might help with troubleshooting (on Windows, go to Window > Toggle System Console...on Linux just start Blender from the Terminal... don't know about Mac, but Wayne will):
Hi Spikey
This helps indeed. Thank you very much. In one of his Videos Wayne explains it but couldn't find it any more.
Trying to find out how to get rid of this DC, the answer doesn't really help yet. Glad, impatience isn't related with pain... :-)
Here is another thing I don't quite get. At the beginning of the Video you parent the Turret_body_GEO to the base_GEO then around 8.35 you parent it to the bone body.... which kicks out (in my case) the parenting between the two _GEOs
I know, a lot of questions but I am having a hard time understanding this.... hope you have the patience to go through this with me.
thank you
Alright... here I am again... why not :-)
The video was a bit confusing because around 10.15 you say "Everything should be parented to the "Root""A mark at 10.20 says This should be parented to the base bone I will fix this.... so I kept parenting my bones to the base... which causes the issues....
bloody hell, those two days made me struggle and almost made me give up but at the end I learned so much about dependency cycles... pretty cool the feeling when you figure out something... such a release :-)))
thank you Spikey and Wanye...
Martin
Hey Martin.
Sorry you're having troubles, but I can see you have actually figured out something very important. That is - when you struggle and learn something the hard way, the lesson you learn is more valuable.
Now you know much more about dependency cycles (and hopefully how to avoid them)
Let me clarify what I meant when I said "everything should be parented to the Root". I don't actually mean 'directly' parented to the Root, it can be indirectly parented. Meaning - if you follow the parenting of any bone up, it will flow to the Root (which should be the top of the hierarchy). There are a few exceptions to this when you are using certain constraints - but then the 'parenting' is happening through constraints rather than a parent-child relationship.
I really hope that didn't make things more confusing
I think I may have sent you down the garden path from my last comment (about the constraint on the base)
I watched the video again and saw how I put this together (there's many ways to do it)
To solve your problem - you just need to parent the aim bone to the root control (not the base like your file).
That is what I do in the video.
Hope this helps.
