Thank you all very much. That is most useful. The solution now looks so obvious!

I have spend a while looking at the maths functions, and I am attempting to reconcile them with my limited knowledge of programming. I wish the manual included a collection of examples of these kinds of logical collections.

Why is the camera to be outside the vehilce? In real life, one might expect to locate a real camera inside; and to use a short lens (e.g. 20mm 'Focal' length, in terms of Poser's main Camera) to view a wide angle.

For techies, here is more information about PathMatch:

http://gfx.cs.princeton.edu/pubs/Barnes_2009_PAR/index.php

Thank you very much for the assistance.  I suspect Easypose may be best for my purposes. Sadly, even the 20ft rope only has around 100 segments. I shall contact the author ask if he has one with more.

I appreciate TrekkieGrrrl's reminder that rope is "very easy to model and rig". Sadly, I lack the skill and knowledge. Even the 'setup room' fills me with horror and confusion.

Phil's 'AllTiedUp' looks alot of fun to use, but rather more powerful than I currently need.

randym77's referred to the general difficulty of posing rope. I agree; and made harder if the rope is to be tightened and tied - in an animation.

Thank you all, again.

I am unsure what resolution such printers can offer. In the cases of, for example, a "30cm x 40cm" or a "50cm x 70cm" print, what would be the max size (number of pixels) of the graphic file in order to make full use of the Printer's capabilities and that of the paper it is to be printed onto?

Or perhaps, if it is an easier question; what DPI can these printers print at?

One could load the Object multiple times.

import poser
scene = poser.Scene()
for n in range(1,10):
    m = scene.LoadLibraryProp("D:Poser Pro 2014 ContentRuntimelibrariesPropsPrimitivesball.ppz")

Very many thanks! I am clearly suffering from PoserPython Manual reading blindness. (I do wish the Poser manuals used the same terms as appear in the GUI).

Adobe offer trials of "Dreamweaver CS6". Whilst still allowing the user to get their hands dirty with 'code', it probably includes a number of functions to do neat HTML5/Canvas tricks.  I might also guess it loves using files from other Abobe products.

(I would be interested in what Ockham might find. Whilst not being obviously related to Poser; it would be pleasing to see what tools might help allow a Poser user to generate simple HTML5 versions of their Poser animations.)

FWIT, here is a short demo (20 secs) where I used 45 Figures in the same scene (and 45 separate Walk Paths).

Whilst Scripting simplified the task of loading all the Figures (and in creating all the Walk Paths), the Poser app still ran, although noticely slowly!

I7 CPU, 64bit PoserPro2012, 16Gb RAM.

www.youtube.com/watch?v=VUBy5YIlE9A

I believe 'light emitter' may be set in Python by using the "SetVisibleInIDL" command (Poser Python manual page 202), which may integrate well with Markschum's script.

And. If you change a state while the Properties palette is open in Poser, the state in the palette maybe not updated immediately, but only if you switch to the Parameters palette and back.

Thanks, but I believe those 'poser' format files (circa year 2008) were adjusted for the Poser "skeleton".  They don't work so well for other Figures.

The scaling would only be done at the 1st frame. Then, Poser's Figure would have the same proportions as the incoming BVH. If that is true, then perhaps the Poser Figure will move correctly (i.e. as intended by the original BVH). Thus,  no jerking or foot sliding.

I am not intending on changing the world here, I was just keen to watch some of these Carnegie data files within a Poser environment.

Otherwise, I agree with rokket, importing BHV data is generally not the best way to animate.

On a related matter.
Although not using Bullet; my test animation here (best watched at 720p) uses up to 3000 Props in scenes. The 'movement' of cards is controlled by the movement of a single object to which all the other 3000 objects 'pointat'.

http://www.youtube.com/watch?v=EpaOKzLhy-o

Many thanks. That was extremely helpful. I have also had a chance to learn something (ATAN2) about maths that I was was not taught 50 years ago. Sadly, whilst attempting to solve it myself, I ran into "quaternion" maths; of which I understand 0% and don't have a clue to use; but I presume may be even more satisfactory to use.

However, markschum's solution is good enough for my purposes. I am also grateful to Englishbob; who reminded me that I really should learn a bit about from the manual about joint editing.

Thanks again.

You guys are amazing! Sadly, I can't get it to work. markschum's suggestion seems to fit generally with what I was doing. I am wondering if someone might examine my code and see what I am doing wrong.

My aim is to have an animation which includes a number of these objects; which is why I would prefer to script the Rotation calculations.

I realise that checking other people's code is not much fun, so I am grateful for any assistance:

ball = scene.Actor("BallCone_1")
cam = scene.Actor("box_1")
ballx = (ball.ParameterByCode(poser.kParmCodeXTRAN).Value())
bally = (ball.ParameterByCode(poser.kParmCodeYTRAN).Value())
ballz = (ball.ParameterByCode(poser.kParmCodeZTRAN).Value())

for v in range (0,scene.NumFrames()):
    scene.SetFrame(v)
    camx = (cam.ParameterByCode(poser.kParmCodeXTRAN).Value())
    camy = (cam.ParameterByCode(poser.kParmCodeYTRAN).Value())
    camz = (cam.ParameterByCode(poser.kParmCodeZTRAN).Value())
    
    xstep=camx-ballx    
    ystep=camy-bally    
    zstep=camz-ballz    

    if xstep<>0:
        tany=(zstep+0.0)/(xstep+0.0)
        roty= math.degrees(math.atan(tany))

    if ystep<>0:
        tanx=(zstep+0.0)/(ystep+0.0)
        rotx= math.degrees(math.atan(tanx))

    if ystep<>0:
        tanz=(xstep+0.0)/(ystep+0.0)
        rotz= math.degrees(math.atan(tanz))

    ball.ParameterByCode(poser.kParmCodeXROT).SetValue(rotx)
    ball.ParameterByCode(poser.kParmCodeYROT).SetValue(roty)
    ball.ParameterByCode(poser.kParmCodeZROT).SetValue(rotz)

scene.SetFrame(0)