Walk.O.matic 0.49.9 maintenance release


(Jamesk) #1

Here’s an unofficial maintenance release. I didn’t update the docs yet, that’s why it’s not official… umm…

*** CHANGES in this release:

  • Decent names for the target empties. That was a total no-brainer really, but I have to thank eeshlo for telling me how to do it anyways

  • Empties will be reused if they are already in the scene upon script execution. So, no need to delete them in between reruns. Thx to theeth for bitching about it.

  • Very nifty recalculation of heel separation, foot look-at and toe look-at forward offset amount: Once you’ve run the script, and rerun it, it will look at how the targets are placed and change the global parameters for them by measuring the new heel separation etc. This makes it much easier to use when you’re trying to match these values to your armature. Just move the empties to the correct location and run the script. One important notice tho: for the foot and toe look-at empties, only the adjustments made to the right foot will be taken into account.

That’s about it, unless I forgot some minor fix. Get the new version here:
http://home.bip.net/millfield/walkomatic0.49.9.py


(theeth) #2

cool beans :slight_smile:

and who said bitching never pays :stuck_out_tongue:

Martin
PS: Did you ever tried writing Rotation IPOs with the 2.25 API? I’m trying to do that for my tracking script but it doesn’t work somehow.


(eeshlo) #3

You probably know, but just in case, the rotation values are supposed to be one tenth of the actual value in degrees. So if the rotation is 45 degrees the ipo value should be 4.5
This is what caused confusion for me when creating the ICARUS script.


(theeth) #4

[quote=“eeshlo”]

You probably know, but just in case, the rotation values are supposed to be one tenth of the actual value in degrees. So if the rotation is 45 degrees the ipo value should be 4.5
This is what caused confusion for me when creating the ICARUS script.[/quote]
Actually, I got that part pretty quick having worked with IPOs for a long time, but the problem is that it seems to work in radians in 2.25 (actually, it works when using radians but only if I add 1 point to the curve. With more than one it doesn’t work anymore). I tried working in one tenth of the degree value but the curve is still screwed up, that is, I get values in the 10000 range.

I’ll try posting a copy of the script I was using later today.

Martin


(Jamesk) #5

Not yet, but I will. I’ll let you know what happens =)


(bmax) #6

kewl idea! :smiley: