Thank you for that info about Notepad++.

Why that should work but neither Notepad nor Wordpad is interesting...

Also, have you tried any of the Truebones' animated FBX freebies ??

I do not know if he's 'just lucky' or uses Autodesk's official SDK, but his FBX models and conversions all seem to 'Play Nice' with my P_11.3...

--

Disclosure: I bought Truebone's 'PMX to FBX' Converter ($$) to get rigged MMD figures into Poser. IIRC, it also ports animation.

Two 'gotchas'...

This first version cannot port texture calls. Hand-loading those within Poser may be tedious, but totally beats trying to rig figure..

Do NOT port PMX models flagged 'TDA' or 'TDA-derived', as their 'T&Cs' prohibit use outside MMD environment.
IIRC, TDA's author was badly affected by SL piracy, slammed the door...

"It seems like the '5 points per $1 spent' is gone."

Unless has simply fallen off page during update --Not unknown !!-- would seem so...

Hmm...

I banked a lot of store points against P_12's arrival. Did not reckon its 'new facilities' cost-effective, kept banking towards _13.
No, I'll wait for next 13.x, look again...

FWIW, DS recently added a 'frequent buyer' program, whose tokens expire at end of week !!
ROFL !!!!

Does not influence my collecting their 'budget' Classic outfits (VAGSM4), props etc, plus 'interesting' freebies.
The 'non-Poser' models make their way to Poser as either 'static' OBJ+MTL or rigged FBX...

Thank you.

I have FBX Converter 2013.3. It cannot handle some recent versions, but the Explorer tool clearly show when texture calls are missing or 'non-relative'.

I've never tried Notepad++, will investigate.

Why that should work, but neither Notepad nor Wordpad is interesting...

Again, thank you.

Plan_B is to position light at a known XYZ.

This helps when eg a 'broad' spot-light cannot bring up facial features without 'washing out' scene, so needs an additional narrow beam as supplement...

( I fell into Poser 3 via a CAD background, as my FloorPlan + TurboCAD combo could not handle more than very-low-poly static figures... )

Well, when I imported a Noesis-generated FBX and found it had ~70++ sub-rigs, each with its own material calling one of ~25+ texture sets (DSB+T), I was a tad disheartened...

--

As I understand it, GPU rendering must load all textures along with the models.

By analogy with meshes where, IIRC, 'Duplicate' command thriftily references original OBJ, PP2 or CR2, while a new library load or import piles up over-heads, how does eg Superfly handle texture calls ??

I've just thought, with a shudder, that auto-loading or dragging in a texture might add significant over-heads, while selecting from drop-down list --The one starting with 'None'-- may not...

A minor issue for 'simple' scenes but, when you're invoking a bunch of 2k, 4k, even 8k texture sets per material, with HDRI back-grounds...

Any chance of the Coder Gurus laying out the resource costs ??

Also, a plea for an 'engineering' dashboard' so we know what's stretching Poser, and so how close to failure we're flying... 

My P_11.3 claims it can import LWO format, but only seems to like older models. Hence my thought that there are file version issues...

If you open a simple LWO file in eg Notepad, is there a version number quoted in 'plain text' before the data ?

FWIW, will your Lightwave export FBX ? Directly or via a budget plug-in ??

Do these 'Library' items head only for Poser's core run-time or, optionally, external libraries ?? 
--
I actually have very little beyond the 'install' pack and a few 'saves' in Poser on C:, but ~4TB of folders with a zoo of items, each with own run-times or 'importable' files spread across several data drives...

I link in what I need for a project, un-couple when done...

Tangential, what USB ports do you have ? There are many budget external USB_3 and/or USB_c DVD drives available on eg Amazon, somewhat fewer with USB 2.0 ...

Thank you, Thank you Nerd, for this 'inside' info.

Could some thought be given to an 'engineering' console for Poser  ?

Even as a $$ stand-alone app that monitors what parts of Poser are using what resource ??

Windows' 'Task Manager' can be frustratingly generic...

I get a blank but usually no crash if scene is just too complex for my ageing twin GPU cards. Dialling back their preferred 1024 vols+buckets progressively, I get to 64, which is also the CPU-only setting for both this CAD_Tower and the network-render 'Box'...

For example, this scene was still unstable at 64 v+b with the GPU cards, so I ran CPU-only, 96 pixel-samples, in ~ 1¼ hours on 'Box'. Currently running a 256 p-s, which I've just stopped by to check on queue's progress ~80%...

Lamps are budget DS set ported to OBJ+MTL. Frame is Poser primitive cylinder, multplicated, scaled etc.

Hooks from https://www.renderosity.com/freestuff/items/84438/simple-hook-primitive

My P_11 #1 light is well behaved. Yet, with what seem the same settings, #2~~4 are often too-bright or too-dim depending on spot/infinite/area/point etc. I've reached the 'shrug' stage.

But, yes, even with Superfly, I can dial down spots to a narrow beam with 'cast no shadows' to illuminate eg face under big helmet...

Takes much 'trial & error', much swearing, a lot of test-renders, always wondering if my dozen-plus deleted test-renders will all re-appear next time I open Poser...

You may find you must combine two lights from same direction.

I'm several generations behind such uber-tech but, IMHO, 'superfly, progressive' seems to thrive on pixel-sample count: The more, the faster.

Lots of light helps, too...

I do test-renders with 14 pixel-samples, WIPs with 32, 'nice' with 64, 'good' with 96 and 'over-kill' with eg 256, run overnight.

Until my ageing twin GPU cards max-out on scene complexity, they like 1024 vols+buckets. I can push them a lot further by reducing via 256, 128 to  64. My CAD-Tower's CPU cores and network-render 'Box' also take that 64...

Are there different versions of LWO ??

Also, OBJ (+MTL) is un-rigged. Upside, as both are text files, paths etc may be hand-edited.
FBX may be rigged. It may even have 'relative' texture calls, rather than hard-coded into depths of author's G: drive's folder tree...
But, due to differences between 3rd Party / Open Source FBX plug-ins, eg for Blender, and the proprietary Adobe SDK, import results vary.
I half-joke about three types of outcome:
'Okay', either due Adobe SDK --'Rigged by Maya' ?-- or a temporary 'happy alignment' of eg Blender and plug-in sub-versions' quirks.
'So-So', anywhere between a few and many sub-rigs. Position / pose using first, parent others to this ASAP to off-load Poser hierarchy base...
'Splat', think Star-Trek Transporter Accident. Call janitor to mop mess, close and re-start Poser...

But it does not have to, unlike hex+pent, or Penrose's kites etc...

The 'Grauniad' has a reputation for oopsies...

;-)

vopehov506, please spare a thought for those with epilepsy. That striking animation is in 'Photic Driver' country...

I'm safe, it just gives me a headache and a strong urge to 'punch out the perp', but my wife (RIP) would now be in a twitching heap on floor, or 'yogic flying' off the sofa...

Remember that infamous 1997 Japanese Pokemon animation that hospitalised many hundreds of kids ??

Yeah, right...