Here is one of my own scripts, which might help. Before running it:

1. set the 'proplocation' to point to the Prop to load.
2. Set the 'numberofprops' for the number of instances of the prop to load.

http://tima.uk.com/poser/load_props_randomly.py

IMHO, if a Prop is given 'Bullet Figure' values, then it retains when the Prop is saved into the Library. One could them spend a few minites manually adding many instances of the Prop.

I find this is one area where 'scripting' can be very useful. A script would load all the props and randomly position and rotate them. I have done this a few times whilst playing with PPro2014; and it can be fun to watch several hundred objects falling down.

I created a crowd scene in this animation (from 05:03 to 05:30) http://www.youtube.com/watch?v=ZKIDR7njbXQ
For that, I animated a group of people into poses randomly selected from the Poser Library, with their keyframes randomly set. Then, using the process Greymalkn mentioned, in my video editing software, I added (overlayed) multiple copies. But, to prevent them appearing the same, I used the software to create a mixture of forward and backward motion, and a standard and mirrored image.

However, if Figures are expected to move around each other in a 3d world, simple overlaying is not possible (or not practical). The Computer running Poser must do all the work (and thus affect the speed of using the app).

And things get harder if the Figures are to move around. The image below is from my next amateur animation. It shows some of the 100 Figures who, after walking down their own Walk Paths are lifted upwards (as in 'the Matrix') using PoserPhysics2012.

My thanks again for the advice and suggestions.
This process now appears to work satisfactorily (for me).

1. Import the original graphics file into Inkscape.
2. Use the Menu 'Path/Trace Bitmap' and choose the tracing system required.
3. Export as SVG.
4. Import the SVG into Blender, and apply an Extrusion.
5. Export the object as OBJ (or whatever is required).
6. Import the OBJ into Poser, and use the Material room to replace the default (black) colour.

Inkscape's options for tracing are described in the Helpfile. Depending how it is set, the trace may either either generate only the outline or treat the whole coloured area as a solid.
The Inkscape tracing options are described here:
http://tavmjong.free.fr/INKSCAPE/MANUAL/html/Trace.html

It depends whether you require the manual settings which are disabled when using progressive mode. The Helpfile helpfully states "Uncheck this option if you need more flexibility with manual render settings."

Thank you. I have now looked briefly at Blender's option to extrude SVG. That may eventually be my option.

My other option is to write my own image to OBJ (or whatever) converter. Input a black and white graphic at one end; and out pops a 3d object with all the necessary quads. I wonder why there are lots of similar freeware apps available?

My thanks again to jestmark. I am not actually adverse to 'learning basic modeling', but I understand the theory alot better than I know what each program does, or how well each one performs.

I am sorry. I was not clear. I was asking for a semi-automated procedure; as I am wishing to create a large number of such simple objects. The images are very detailed and may contain over 20,000 accurately placed vertices. Whilst it can be done, I assume, using most modelling software; it would likely be a huge manual task.

I had understood the Blender option requires the user to manually trace the outline. Some applications, for example Adobe's Illustrator are able to create the required vector outlines; but cannot generate 3d models.

Perhaps jestmarc can explain how Blender might automate the task for me?

Ah! Many thanks. I had not discovered "SelectFigure" before. That is perfect. Thank you again!

I appreciate it is generally easier to use the Keyframe editor; however my Scene has over 50 Figures and I want to try various combinations and permutations; so need to repeat the process many times. In addition, with so many Figures, Poser tend to slow down and the Keyframe Editor window can sometimes feel a little unresponsive.

I watched several parts of the Intro, but gave up because it progessed so slowly. Before making files downloadable, I earnestly hope that you edit them (to remove the unneccessary sections) and adjust the audio levels so the different voices have the same volume. I suspect it will make the downloadable videos smaller, shorter and more informative.

My clip here uses many animated scenes using Poser. Those scenes were rendered as PNG files and imported into a video editor (where additional effects and scenes were added). The Poser sections should be pretty obvious (as I am not a Poser expert!), and some may enjoy the 'crowds' which start around 04:30 , or the 'clocks' around 06:05

http://www.youtube.com/watch?v=ZKIDR7njbXQ

A number of my other clips at http://www.youtube.com/timand2222 also use Poser for the animation.

May I politely ask whether all the above wisdom in this thread is equally application to animations as well as 'single' frame images?

That was very helpful. Thank you very much for taking the time to assist me.

My thanks to all replies regarding UVMapping. I was hoping there would be existing templates for the default Poser primitives props; to save converting the props to OBJ. However, thanks to your responses; I now know where to start learning.

(I am sorry my 'dice' got confused with 'ice'. This has led to yet another difficult to follow  thread in this Forum.)

Many thanks for the reply and the link.

Perhaps I don't understand this either. But:

After pressing 'OK'; and then clicking on 'Apply' again (to re-open the 'Apply Walk'); the the 'End Frame' value is automatically recalculated, based on the existing value for 'Cycle repetitions'.

I agree, the interface is confusing. But, I think the designer expects the User to either:
a) Set how many repetitions they want,
OR
b) Select the End Frame.

As far as I understand, the uncontrollable jerkiness only occurs if the User sets the 'End frame' to be higher that its original calculated value.

If the 'End frame' value is set lower than the original value; then the animation stops at that place. Sensibly, I think.

I recommend reporting the missing helpfile text to SM.