Setting up procedural bones for model

I’ve been working on a model with pistons in the legs, and to get them to work properly, I’m trying to use procedural bones on them. I followed a tutorial for it here: http://forum.facepunch.com/showthread.php?t=1295558 , but when I try to compile the model with Crowbar, this error comes up:


Compiling...

qdir:    "c:\users\matthew\desktop\misc\fear 2\powered armor\"
gamedir: "C:\Program Files (x86)\Steam\steamapps\common\GarrysMod\garrysmod\"
g_path:  "PoweredCopy.qc"
Building binary model files...
Working on "PoweredCopy.qc"
SMD MODEL PoweredArmor.smd
SMD MODEL PAphys.smd
ERROR: procedural bone "R_piston_down", parent remapping error, control parent was "bip01_r_foot", is now "Bip01_R_Thigh"
ERROR: Aborted Processing on 'FEAR2/PoweredArmor.mdl'


...Compile ended. Check above for any errors.


I went back to 3DS Max and checked the rigging, and the piston is definitely attached to the foot bone, like it should be. I’m not sure what’s making it try to attach to the thigh bone.

If it helps, here’s the .vrd file:


<helper> R_piston_up bip01_r_calf bip01_r_calf bip01_r_foot
<basepos> -0.581219 -7.92598 0.561728
<trigger>       90                      -3.02075  -2.55969 112.348           83.7045 -2.03274 -22.6543                       0 0 0
<trigger>       90                      -3.02075  -2.55969 112.348           83.7045 -2.03274 -22.6543                       0 0 0
<trigger>       90                      -3.02075  -2.55969 112.348           83.4464 -0.896012 -12.5821                      0 0 0

<helper> R_piston_down bip01_r_foot bip01_r_foot bip01_r_calf
<basepos> 16.6221 -3.29101 0.0481654
<trigger>       90                      -1.07252  -3.67618 -86.9767            92.5098 1.39485 -115.816                      0 0 0
<trigger>       90                      0.749559 -3.75991 -114.363             92.8527 0.221773 -91.1021                     0 0 0
<trigger>       90                      -2.94304 -2.458 -52.9147               91.8021 2.22282 -137.611                      0 0 0

<helper> L_piston_up bip01_l_calf bip01_l_calf bip01_l_foot
<basepos> -0.510279 -8.04273 0.0781002
<trigger>       90                      1.80178  1.66708 112.411            94.0077 1.81627 -22.8298                         0 0 0
<trigger>       90                      1.80178  1.66708 112.411            94.0077 1.81627 -22.8298                         0 0 0
<trigger>       90                      1.80178  1.66708 112.411            94.2748 1.04042 -12.1422                         0 0 0

<helper> l_piston_down bip01_l_foot bip01_l_foot bip01_l_calf
<basepos> 16.6501 -3.27907 0.0188646
<trigger>       90                      0.744753  3.06534 -86.7972            89.0762 -1.1478 -116.067                       0 0 0
<trigger>       90                      -0.733552 3.06803 -113.914            88.693 -0.680035 -92.3818                      0 0 0
<trigger>       90                      2.27218 2.18864 -54.3653              89.5801 -1.41221 -138.336                      0 0 0


Anyone have any insights?

Are the parents you listed in the VRD file the same as the ones you set up in your modeling program?

I double checked, and they’re the same. I’ve tried matching the case and switching the order of the helpers around, but it always lists R_piston_down as causing the error.

Edit: I just tried commenting out both piston bases, which were parented to the foot joints. The model compiled that time around. Is it doing something where it disagrees with having a procedural bone looking “up” to the calf bone, perhaps?