IIRC, though DS no longer support DSON, their 'T+C' barred redistribution, reverse engineering etc etc...

Although a tad long-winded, you can export clad figures from DS as rigged FBX which Poser may read.

I managed to get Kalea7 Rogue, a former DS freebie, into Poser thus...

https://www.renderosity.com/gallery/items/3103742/ds-kalea-7-rogue-ported-to-poser-as-fbx-yay

FWIW, I routinely port DS props to OBJ+MTL for use in Poser. DSF Tools ($$) is now un-supported, and seems to hang on DSF files above ~1 MB. YMMV.
DS' UI gives me a prompt migraine, but its Poser-scaled 'OBJ+MTL' export path has no problems with even '>> 10 MB' files.

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

Thank you, Nerd. Good to know, as saved me making an expensive mistake...

FWIW, there's an extensive GeForce_20 Wiki at...

https://en.wikipedia.org/wiki/GeForce_20_series#:~:text=The%20RTX%2020%20series%20is,nm%20FinFET%20NVIDIA%20(FFN).

Y-Phil, thank you for that clarification.

Whatever the reason for the 1.000 / -1.000 delay, knowing there may be a delay yet it will 'come good' makes it 'usable'...

Thank you.

Good call, Thalek.

Though SmithM were somewhat reticent about Poser internals, perhaps Bondware's gurus may be aware of potential processing pinch-point, and if still exists in #12 / #13...

What's rule on 'previously posted else-where' ??

May I suggest you keep your core Poser run-time 'sparse', use the external library facility to link in whatever unique stuff you need for a specific project ??

Link to folders *holding* those external runtime, lest Poser be utterly confuddled. To sanitise really classic stuff, I load empty runtime folder tree into new 'holding' folder, move whatever where...

Also simplifies porting / organising 'other' mesh / model formats, as easy to keep Zip/Rar, thumbnails / comments / scaling info / renders etc together...

I've 3~~5 TB of 'stuff', spread across three data-drives. Ranges from low-poly, static, clad-mannequin 3DS figures, mostly 'Medieval-ish', from my 'Classic FloorPlan' days via a zoo of rDNA etc freebies for P3+P4, many XPS etc figures ported via FBX, sundry XPS and PMX props / stages / scenes exported to OBJ+MTL, to the latest 'Salt Lake' freebies...

May your back-ups be current...

My network-render PC deploys ~15½ of its 16 Ryzen_7 cores but, hey, complete 'Box' was cheaper than upgrading either of this now-ageing CAD_Tower's twin GPU cards...

Could a nice tribute be added to the 'In Memoriam' section ??

Parallels my call, too, Meshbox.

;-(

I built a heap of store-points towards my #11 to #12 upgrade, but realised #12.0 lost eg the 'simple' Material Room stuff I used. Waited for subsequent #12.x to put such back, but #13 came along first...

Seems #13, after a few teething troubles, runs cleaner, faster etc etc than #12 did: Kudos, Team_Poser !!

But, sadly, a lot of that uses PC hardware I lack...

Also, I'm not yet sufficiently impressed by the community's opinions of #13's benefits to put my 10+k points towards it...

Could be said that, beyond using 'External Libraries',  'dipping a toe' into Cycles' Emission and Reflection, and using Superfly plus network-render 'Box', I'm essentially running Poser_11 as a 'super-P_4'...

Um, 'Guilty as Charged', I'm afraid...

I fell into Poser (#3 cover-disk) because my 'home design' package could not handle more than un-rigged, minimal-poly, Medieval-ish 3DS 'figures'. 

But, I could export a room and its Medieval-ish props to Poser_4, put those Medieval-ish figures in the background, supplement with posed P3/P4 people 'doing stuff'...

For 'reasons', that home-design package was not re-compiled to 32/64 bit, but replaced by a less 'friendly' package that was not back-compatible...
( IIRC, company 'fell out' with the coding team they'd licensed original '3D Core' from, bought in all-new...)
Ouch...

But, my habit of porting 'fun stuff' from other formats was set. Routes currently available are...
XPS via free XNA Posing Studio => OBJ+MTL props, or rigged .MESH.ASCII, then latter via free Noesis to Poser-compatible FBX.
PMX props via free PMX Editor => OBJ+MTL
PMX rigged via TrueBones ($$) utility to Poser-compatible FBX. Note this v1 (Beta ?) only ports hues, not texture calls, which must be hand-loaded...
SFM VTF textures via free Noesis to eg PNG or JPG
SFM MDL models via free Noesis to un-textured OBJ or FBX. Textures must be hand-loaded.

DS props via DSF Tools for low-ish poly or DS' migraine-inducing UI for 'big stuff' to OBJ+MTL.
DS figures to rigged FBX... Um, one, once: Kalea7 as proof of concept, but migraine lasted all next day...
Ouch...

Just a reminder, thanks to several Poser gurus, that morphs are linear: Small bend angles don't look too bad but, above ~30º, forget it...

So, sliding doors / windows on a panel van are okay, cab doors may open 'ajar', but back doors will not 'swing back' as intended.

If I could work grouping etc, I'd arrange pivot axis, dial etc to twirl each back door by ~270º with limits.

I got around my lack of skill by using a $$ utility to convert that free MMD/PMX vehicle with such morphs to FBX...

Has your ISP temporarily blocked great chunks of addresses ??

Mine's done that several times recently, pulling up drawbridge against incursions by Nork / Rus hackers. Also, throttled broadband to 'dial-up' speeds against DOS storms...

Settled down after a day or two, though...

Thank you.

Does this still apply using external libraries ?

I've remarkably little in P_11.3 'base' library on C:, but ~ 4 TB of assorted 'import' formats and external library runtimes on E: and G:

I link them in / out as needed. ( F: is mostly my non-CGI material.)

Saving a nice scene and render(s) with their makings makes it hard to re-arrange folders...