Tangential problem is crafting a transparency, reflectivity or emission map for a 'well wrapped' prop, typically a complex OBJ with equally complex textures.

As some UV mappers allow parts to be moved around to minimise 'wasted space' on a texture, finding eg interior mirror or small bulk-head lamp can be fraught.

Unless you're fortunate enough to spot the shape, may come down to a 'binary chop': So, apply a 'half+half' painted image crafted in eg free Irfan view.  Half-paint the portion that hit target, repeat until located...

My worst-case was seventeen (17) iterations to locate a few dozen pixels in unexpected part of a very busy 2k texture. A smear rather than a shape, it could not be found 'by inspection'...

Given those generous discounts to go from P_11 to P_12, I fear any P_11 to P_13 offer would be minimal...

Best guess, it was exported to FBX using one of the 'third party', reverse-engineered plug-ins. Comes close to Autodesk's proprietary format, but Poser is fussy...

( Honourable exceptions for Mixamo's v2016, Truebones' new 'PMX to FBX' utility and anything 'by/from Maya', which usually behave...)

What you could try is 'zero rotations, zero figure'. Sometimes this re-aligns the strays. 

I'd expect the over-all figure may then be scaled, XYZ translated using the first sub-rig listed.

Applying any supplied textures to your zoo of parts in material room is another matter entirely...

'Crash' crash, or renders black ??

Latter may be due to scene and/or texture complexity. IMHO, Poser_11's 'garbage collection' can get 'maxed-out' if you do a lot of texture changing, especially 2k, 4k, 8k super-detailed textures. Save PZ3, close and re-start Poser usually helps. If necessary, down-size mega-textures using eg free Irfan View.

Don't know about Firefly, but I also tackle persistent 'renders-black' failures in Superfly by reducing my 'vols & buckets' from 1024 by binary stages to 64. At that point, probably faster to switch from my overloaded GPU cards to CPU-only, or send job to networked 'Box'...

Yay !! Neat !!!

I often find some juggling of camera position plus camera's 'hither' setting allows sufficient suppression of 'photo-bomb' pillars, walls etc...

It's when entire scene renders black that the real head-scratching begins...

If the FBX source uses generic 'open source' code, then Poser seems to have problems.

Worse, sub-version changes to that code may 'sub-vert' functionality. I've several similar figures re-rigged in succession by same artist using same work-flow, but only one group of them 'play nice' with Poser. Blender and/or its plug-in had up-dated after about six weeks, and their temporary 'sweet spot' was lost... 

I've found Mixamo figures with earliest / oldest FBX version, anything 'Rigged/Exported from Maya', and Truebones' new ($$) 'PMX to FBX' utility usually work in Poser.

Note: As yet, T-bones' utility only sets hues, cannot call textures. Hand-loading is not a problem for a few materials, but gets silly beyond a dozen or so, especially if Diff complemented by bump, transparency, emission etc maps. And, d'uh, mind-blowing if dozens. I've sent the guy a link with better documentation of PMX texture-call storage, hope a #2.0 will arrive...

I did not realise there was a 'literature' gallery, thought it was just about the 'art' of writing...

Just to clarify, IIRC, render box --prior to #13 ?-- uses CPU only. I've a basic VGA card & display in mine.

From what I've heard, on-board GPU chips are not very good at non-game rendering. Also, GPU cores take up die-space that, IMHO, is better used for CPU cores. As I mentioned above, 'Box' uses 15½ of its 16 cores to render. Usage swings from 100~~90 % of CPU resource, between 'pulses' of data to disk...

Okay, so not as fast as a 'state of art' mega-GPU card with a zillion cores and an astonishment of fast RAM, but I'm a hobbyist not a commercial artist, so hits my 'sweet spot' of cost vs performance. YMMV. If necessary, I could build a second 'Box' --plus KVM switch-- for a fraction the cost of a twice-as-fast GPU card, render two views in parallel...

IIRC, UV Mapper Classic is still available, still free...

http://www.uvmapper.com/

I'm no Mapper guru, I can't yet shuffle out-lying map portions into neat, neighbourly positions. But, especially for older OBJs that say 'template available on forum', but that's long gone, trying different un-wraps often gives a match to the texture maps. Because, yes, 'Classic' was so the 'GoTo' app...

Trying to find the teeny-tiny portion of a complex 2k or 4k texture that 'works' eg a vehicle's mirror, side-window or lamp, so you can mask emission and transparency, can still end up as a 'binary chop'. IIRC, my 'worst case' hunt took 19 tries...

Tangential, I'm narrowing down the problems with imported FBX figures. More and more, is not the figures, but exporters' 3rd-party plug-ins.

Example: Truebones now do a ($$) 'PMX to FBX' conversion utility. It does not seem to use generic open-source FBX I/O code, makes nice, posable figures. Yes, even though the FBX 'version' is 'very recent', Poser_11 likes it.

Well, d'uh...

Okay, there are usually 2~~3 rigs, use the first for posing. And, yes, PMX 'TDA' figures / accessories have 'NO-PORT' T&Cs due to SL piracy, so must be shunned...

I realised it would be much cheaper and future-resistant to build a 'render box' than significantly upgrade either of my CAD_Tower's now-ageing twin GPU cards...

As Box' graphics need only support VGA , this means you can fit a 'Basic Office' GPU card, an old display. But, the more CPU cores, the better. Mine renders with ~15½ of its 16. One 'gotcha' is my twin GPU cards like Superfly with 1024 vols & buckets. For 'CPU-only' renders, eg on 'Box', these must be dropped to 64 else stalls out...

Yes, all of the above points by Richard60, especially the 'same version' thing.

What beat me for weeks was Window 10's exasperating network security stuff. The error messages do not give a clue to what's wrong. In the end, I realised that the error messages were looking at sorta-flipside of problem, dug deeper, found yet-another poorly documented networking menu. One last check-box and we were in business...

Uh, please may we have a forum for queue rendering and its quirks ??

That's a useful trick, especially when you're trying to set a scene with 'luminous' stuff, as super-ambient and/or Cycles' emission.

Have you a UV map for the object ?? Also solves issues around unsightly edges that do not 'tile'...

IIRC, there was an official comment on the shop-front that they usually post those USB sticks out as a batch, once a month. 

Add the scary flux of seasonal post...

Hope it arrives soon !!

( UK's postal dispute grumbles on, with service cut by several days a week, a dire back-log of seasonal, a vast back-log for anything needing 'Customs' assessment... )

You must juggle illumination & shadows, plus perspective and 'vanishing point'...

There's too many pretty 'scenes' over on DA where a character has been put onto rather than into a background pic, and just about everything looks wrong.
Still, gotta start some-where...

Perhaps you could take a trick from theatre, dissect that background into elements at different distances, apply those to 'flats' for 2 ½ D ?