Troubleshooting

PoserPhysics 2012 has been release, and there have been almost no reported issues, which is great.  Some items that you should note though:

1. Do not have more the one instance of the PoserPhysics2012 script running at a time.  I will add a check in SR1 to make sure a second copy is not started.
2. Whilst the PoserPhysics window is displayed, it is using the Poser python callback system to detect when you select different Poser scene elements.  If you run another PoserPython script which sets the Poser callback (which is highly unlikely), PoserPhysics will no longer know when you change your figure or prop selection in the scene.  If you do need to run such a script, simply close the PoserPhysics window first.
3. If you have previously installed the old PoserPhysics plugin into your Poser9 or PoserPro2012 Runtime (which would not have worked), make sure you delete it prior to installing PoserPhysics2012.  So delete the following folders/files:
     - Runtime\Python\Lib\site-packages\P6
     - Runtime\Python\Lib\site-packages\P7
     - Runtime\Python\Lib\physics*.*
     - Runtime\Python\poserscripts\PoserPhysics
4. There is a capsule primitive (pp2) supplied with PoserPhysics which gets installed in the Primitives folder, and loads into your scene as "capsule" (lowercase "C"), and  you may already have the Smith Micro supplied capsule (pz2) in the same folder, which loads into your scene as "Capsule" (uppercase "C").  Either of these props work in PoserPhysics, however the former is simulated as a "Capsule", and the later defaults to a "trimesh box".  If using the Smith Micro supplied capsule, set the Shape to "Trimesh Capsule".  This is will set as the default in SR1.
5. The valid "Bounciness" range is 0 - 1, however the PoserPhysics GUI will let you entered numbers greater than 1 (which will be address in SR1).  Keep Bounciness <= 1.