JediSpectre117 opened this issue on Dec 24, 2018 · 40 posts
NikKelly posted Sat, 12 September 2020 at 11:22 AM
{Cough} Having a Procrustean 'One Install Type For All' system would NOT suit me.
A Poser user since P_3, albeit with a time-out from 7~9, I've a near-terabyte of 'fun stuff' on E:, safely off-line.
Any too-rigid system hoards trouble for the future. Remember self-installing EXE models ? Some could be un-zipped, others would only un-pack where-ever they pleased. I've even had to craft fake 'prior-brand' Poser run-times to extract a few...
Besides my zoo of 'legacy' Poser freebies, many still needing re-work, eg from flat heap to 'proper' run-time trees, I've a zillion 3DS and OBJ±MTL meshes, many, many FBX models and figures, plus a big cast of PMD/PMX, XPS and X pending conversion. And, yes, even some modern DS models-- I'm happy to buy 'interesting' items then 'rip' their mesh with eg $$ DSF Toolkit...
I have a 'sparse' core run-time. For whatever project I'm doing, I routinely load and un-load external run-times via the library. Even 11.3's bundled 'Dawn & Dusk', recently located and un-packed, live in 'external library'. Takes 'Special Pleading' to be allowed onto my C: drive...
Basically, I DO NOT want my imports tied to Poser. May seem an odd way of going about things, but I fell into Poser as a way to put 'better' figures in Medieval-ish architectural sets. Originally, I used 'Classic' FloorPlan 3D plus TurboCAD, exchanged sets and props via 3DS. Perforce, figures were super-low-poly 3DS 'statues'. Re-creating rooms in Poser_4 (with 'Big Memory' fix), I could use chunks of my sprawling caravanserai set, the same props and textures plus, now, period-clad & plausibly posed, Posette & Co. Yeah !!
FWIW, 'Classic' FP died when it could not be economically re-compiled to x64, and TC still cannot grok OBJ+MTL. Happily, PoserPro x64 plus my 32 GB RAM can hold much bigger sets than any P_x32, and I think I've found an OBJ+MTL-friendly CAD to replace TC...
Hmm: what will P_12's promised FBX I/O update bring ? PPro_11 seems happy with FBX versions up to v6.1. The now-common v7.4 / v7.5 cause problems ranging from broken 'trees' to 'SPLAT'. IIRC, v7.6 is now 'In The Wild', and sufficiently different for many FBX utilities / plug-ins to report such files as 'corrupted'...
[ Sorry for waffle: I woke to e-mail advising that Azn was delivering between 09:15 and 11:15. Now 17:15+, and 'Still Arriving Today'. {Sulk...} ]