This is a genuinely sensitive topic, Primorge.

I port a lot of free props and scenes / stages from eg MMD PMX format, but must always check that they're not 'TDA Origin'. This is because that prolific artist, who'd produced a wide range of freebies, was justifiably outraged to find his freebies being sold on 'Second Life' without credit or attribution. As SL seemed unwilling to take action, he changed his freebies etc 'T&Cs' to 'No Port'. No exceptions, no waivers, no ports...

As rigged PMX figures remain beyond my skill to re-rig, I just had to check the origin of props and clothes before porting.

Clothes ?? Yes, as a PMX set ported to OBJ+MTL may not fit any Poser figure, but looks good on a wardrobe or shop hanger. And usually low-poly...

And, now, a twist: I've found a commercial, stand-alone utility which claims to convert rigged PMX figures to rigged FBX. The Windows app is not $_budget, but discussion with supplier allows for 'uninstall+refund' if FBX format incompatible with Poser.

Seasonal expenses / contingencies have put this on hold until mid-January, when I'll have the money and time to try it...

If it works, I'll suggest to supplier that they consider advertising it on Rendo-- With reminder to respect source 'T&Cs'...

So, is this quirk a BUG or a FEATURE of Poser's gizzards ??

"This is a notification that there has been a new reply posted to the thread titled "Creating and Saving texture and material files" in the Poser 11 / Poser Pro 11 OFFICIAL Technical forum. "

Huh ?? It's my own post from almost a year ago !!!

Weird, or what ???

IIRC, .DSA files are a 'script' in plain-text, supplying eg location information.

They're often in a 'Support' folder, hunt nearby for 'Textures' folder.

You may find you must scale the textures for use in Poser. Happily, the Material Room 'Advanced' properties will provide optional U & V scaling...

IIRC, the only 'may not work' between P_12 and prior is anything that invokes Python due version change.

I seem to remember a sorta tutorial on how to edit 'old' python files to 'play nice' with new version...

Um, materials ? I recently loaded a 'classic' model, discovered each of the many materials invoked at least a dozen Superfly Cycles nodes. I made window wider and wider, more kept appearing. In the end, I just deleted all but their very basics. My 'post-middle-aged' eyes could not discern any quality loss...

I don't know about P_12, but I've noticed that leaving a complex scene up on P_11.3 for several days often seems to slow it down. If I was more confident, I'd suspect a memory leak...

Have you re-booted recently ? ( Full restart, so you get your mobo's splash-screen ?? )

Thank you, Primorge.

FWIW, I used one of the bundled 'wigs' for LaF that looks okay but did not significantly slow editing.

Also, just do lighting 'with wig' test renders of head+shoulders to mitigate weary wait...

Another 'gotcha' is complex foliage such as a common-or-garden lawn: 35 MB OBJ ??? I wrangled that monster by using Poser's ground plane and OBJ's bump-map set to 'displacement'. Just mind you set appropriate displacement scaling there, and  'displacement bounds' in figure properties. With care you can get 'Elephant Grass'...

Note: If eg CR2 file exceeds ~100 Kb, 'Notepad' may become unstable or 'hang'. If so, open file with eg Wordpad, which lacks such constraints...

I ran into this 'hacking' mis-exported OBJ files which had 'many' material regions, but only one (1) material name...

( And, d'uh, make a 'safety' copy of original file, to be sure, to be sure... )

There are also 'Classic' utilities such as Phil_C's wondrous CR2 editor...

Depending on your GPU card, you'll have to find the 'sweet spot' for 'vols & buckets' size to give fastest Superfly rendering. If scene complexity gives a blank (*) or 'render fail' message, reduce your many  'v+b' setting by binary stages towards the (typically) 64 preferred by CPU-only...

Um, you may have to enable SCUDA / CUDA, too, but I cannot remember where that lives...

*) I've been caught a few times by camera being outside Poser ground's solid sky-dome, but all the lit lights were inside. So, just an unlit wall: Oops...

This problem of incompatible / obsolete drivers is one reason I spent my GPU-cards' upgrade fund on a stand-alone network-render 'Box'. Its nimble Ryzen-7's 16 CPU threads are no-where near as fast as a GPU super-card, but doesn't have 'black-out' issues when scenes / scenery become too complex, common for this PC's now-ageing twin GTX 750 Ti cards...

I only use DS for exporting props that choke / confuse 'DSF Tools', will not allow 'install manager' near it.

So, manual down-loads are the way to go. Also means you can steer files to a directory of your choice, un-pack / un-tangle / thumb-nail / trawl / convert them at your leisure. Beside a zoo of 'SORTED' folders from P4 days, from before Poser and DS diverged, I've 25+ folders, each with 10~~20 sub-folders of DAZ etc DS 'stuff'. Mostly 'budget' or freebies, but you're never quite sure what there'll be. Sometimes OBJs / PP2s are bundled, save me porting DSF...

Sadly, another DAZ 'gotcha' is when they fetch a 'classic' from their archive and the product page says, 'templates available from forum' or similar. They'll have long since purged that forum and, typically, the artist has long since lost their file...

Since I got several such in succession, and put in a grim ticket, DAZ have done better. Happily, though DAZ could not provide templates, I've usually managed to match the mapped textures to their OBJ's default UV-unwrap by one of several 'classic' utilities.

FWIW, though DS' UI gives me a prompt migraine, here's my 'strip map' for exporting DUF/DSF props from DS format as OBJ+MTL. Although describes single props, readily adapted to groups / scenes...

https://www.deviantart.com/nik-2213/art/Porting-DAZ-Studio-props-to-Poser-friendly-OBJ-MTL-911478576

Try not to clutter your Poser installation. Keep whatever you can on a non-system drive, just link/un-link those product folders through 'external library' when needed.

A lot of the old models did not have 'correct' runtime folder trees. May be worth crafting an un-populated one of your own, ready for copy/pasting stuff.

This also helps if you collect and convert models from other formats, such as DS/DUF, SFM, XPS and PMX. As yet, I can only import 'rigged' as FBX, albeit warily...

You got RSR thumbnails ? You need the totally classic Dizzi converter...

https://www.renderosity.com/freestuff/items/57197/rsr-to-png-converter

I'm still finding and untangling some of the early DS figures / outfits that came as self-installing EXE files. Some may be opened as 'archives', most must be wrangled to have sight of Poser, then shunted onto data drive. Many only have RSR thumbnails, so I knew what you needed...

Twin GTX 750 Ti , so you have about thrice my combined GPU RAM...

But, hey, they're also driving three wide-screen displays plus a 'portrait' salvaged from old desk-top, all on four double-jointed arms, spanning almost six feet...

( There's also a small VGA hung off desk's LHS riser to keep an eye on 'Box'... )

Sounds like my wide-screen scenes proving too much for my now-ageing twin GPU cards' 'vols & buckets' settings. For 'not-too-complex' scenes, 1024 suits. When complexity grows, must progressively binary-chop down through 256 to 64, which is what suits a 'CPU-only' render, either on this PC or my networked 'Box'...

I cannot reproduce it, but I sometimes feel that leaving P_11 'open' for a day or two with a complex scene may lead to instability.

IMHO, Poser could do with an 'Engineering' display, showing gas gauge, oil-pressure etc...

IMHO, it is easy enough to port DS props to OBJ+MTL for use in eg Poser.

https://www.deviantart.com/nik-2213/art/Porting-DAZ-Studio-props-to-Poser-friendly-OBJ-MTL-911478576

Snag is that they are entirely un-rigged.

Given discussion of that gold chain, could it be imported as OBJ then 'auto-conformed' to wearer using Poser's 'dynamic' tools ??