Maclean: Here's a quote from the Helpfile from Ajax's EasyPose Underground: Because morph dials respond to mouse control at 1/50 of the rate of valueParms, all of the speed settings will automatically be multiplied by 50 to compensate when you choose to use null morphs as EasyPose master dials. Note that this is not the case when you use null morphs in the ERC control panel, where the control ratio you set is the control ratio you get. This indicates to me that you simply need to go more extreme when upping the sensitivity of those morph dials. Tasquah: Okay, for example, if you had a Poser prop with the following geomCustom directive this is (shortened, obviously):

prop thingy_1
    {
    geomCustom 
        {
        numbVerts     4
        numbTVerts    0
        numbTSets     0
        numbElems     1
        numbSets      4
        v 0.000000 0.000000 0.000000
        v 0.050000 0.000000 0.000000
        v 0.000000 0.050000 0.000000
        v 0.000000 0.000000 0.050000
        f 1 2 3 4
        }
    }

You would cut the stuff inside the and paste it into in a seperate text file, like so: numbVerts 4 numbTVerts 0 numbTSets 0 numbElems 1 numbSets 4 v 0.000000 0.000000 0.000000 v 0.050000 0.000000 0.000000 v 0.000000 0.050000 0.000000 v 0.000000 0.000000 0.050000 f 1 2 3 4

This would leave the Poser doc like this for the moment: prop thingy_1 { geomCustom { } }

Now in the new text file, you remove the leading whitespace, like so: numbVerts 4 numbTVerts 0 numbTSets 0 numbElems 1 numbSets 4 v 0.000000 0.000000 0.000000 v 0.050000 0.000000 0.000000 v 0.000000 0.050000 0.000000 v 0.000000 0.000000 0.050000 f 1 2 3 4

Then comment out the numb- directives (you can just remove 'em but I keep them in for informational purposes if I need such info). You can add other ntoes as comments this way, too. # numbVerts 4 # numbTVerts 0 # numbTSets 0 # numbElems 1 # numbSets 4

# thingy.obj file generated by hand by Dodger. Muahaha.
# Last revision 3 May 2003

v 0.000000 0.000000 0.000000
v 0.050000 0.000000 0.000000
v 0.000000 0.050000 0.000000
v 0.000000 0.000000 0.050000
f 1 2 3 4

Then save this to a file, for example, C:Program FilesPoser 4RuntimeGeometriesMyStuffthingy.obj Now totally remove the geomCustom block in the Poser file; it will look like this: prop thingy_1 { }

(which is a null declaration like you see with cameras) Next you add in an objFileGeom declaration (with a storageOffset declaration, at least traditionally), like so: prop thingy_1 { storageOffset 0 0.3487 0 objFileGeom 0 0 :Runtime:Geometries:MyStuff:thingy.obj }