Sounds like you have texture plus transparency mapped onto place-holder rectangles. Much, much lower-poly than drawing each leaf's near-fractal detail...

Please check for transparency map(s). If not stand-alone, may be texture's Alpha-channel in PNG, or equivalent in eg DDS.

Free 'Irfan View' is your graphics-format friend...

I've tried to port some of the 'classic' stuff up to LaF/LeH, but outcome follows the old saw that borrowed armour comes in 'too' sizes, too big and too small...

Which reminds me of this, by 'silkalivedoll'...

Sorta 'Plan_B' is to send OBJ+MTL to the free Mixamo machine, export as FBX in one of their optional formats.

I've yet to try this, I've only acquired a few pre-rigged freebies but, IMHO, the oldest FBX format (2016) they offer seems to 'play nice' with Poser.

YMMV...

Calm down, every-one !! Please !!

Rendo' & Co have a dire legacy of neglect to untangle, no thanks to the 'Old Owners' who saw it as a commodity rather than an eco-system.

Upside, 'Unimesh support' touches so many aspects of core-code that it must come via a massive 'Spring Clean'.

Which also offers an opportunity to 'Do the Needful' and add 'hooks' to provide future facilities such as, well, browse the 'P_12 Wishlist' for inspiration.

FWIW, V4 may be a couple of LODs down on the current 'Genesis' crew, but both have their place in CGI...

Legacy models ? Yeah, I've several terabytes of them --figures, props, accessories etc etc-- some from before P3 and 'RuntimeDNA'. Funnily enough, a lot of them have similar LOD to recent ports you see from XNA/Lara, SFM, MMD, Mixamo etc etc.

I began with 3DS --static, hues-- to accessorise my 'Classic' FP3D 'Home Design / Architecture' suite for a Medieval-ish look. P3 had figures that could be 'posed', however clunkily, and could use my collection of props. I still collect such, though current challenge is the oft-exasperating rigging differences between Autodesk and 'Open' FBX formats...

Um, is there a convenient workflow between an MMD 'rigged' PMX and something Poser will load ? Without total re-build / re-rig ??

I've sorta-solved for XPS...

FWIW, if you have a lot of 'legacy' materiel, use via 'external library' function rather than loading more than a very few directly into Poser.

Link via 'library' to an item's own folder anywhere on an attached or networked drive. Poser will peek within and access the item's mini-run-time. Un-link that folder, another potential piece of clutter goes safely back into your archive...

'Gotcha' is that this only works so easily if 'external content' has its own mini-run-time. Easy enough to keep an empty 'run-time' folder tree, copy to where-ever needed, populate neatly.

If you only have eg OBJ+MTL and textures in folder, just import via file menu. Don't forget to add a tiny .txt to folder with scaling and other notes...

"If rendering in Superfly, you need to apply a holdout node to the construct."

Thank you, seachnasaigh, for providing a 'finder' map: Much appreciated.

Yes, DS is 'free', but DAZ are 'content sellers', their figures are expensive. Think free shaving handles but pricey disposable blades. Yes, you can find lots of freebies there if you watch like a cat, but most are add-ons to add-ons to $$ purchases. And, too many of their budget items come with 'gotchas', like their discounted legacy products that say 'templates available', but don't due age of model and/or forum culls. Oops...

There are many DS freebies etc here at Rendo', over at eg SCG, EE and the like, but...

I began with Poser_3 'free' off a mag's cover-disk, bought #4, was moving to #7 when a multi-HDD disaster and family priorities took me out for almost a decade. Got discounted #10, soon moved to #11. The legacy of previous owners' neglect was glaringly obvious: There's still UI bugs & quirks I remember un-fondly from #4...

IMHO, Rendo' are doing the best they can to untangle the many, deep legacy issues, drag Poser " kickin' & screamin'  " into contention with Unity, XNA/Lara etc etc. I reckon DAZ is determined to move away from Poser-compatibility, and each generation of 'Genesis' makes it worse.

Two things:
When Poser gets 'Unimesh' working, which will be no small feat (*), that opens a window to 'modern' rigging. Then, eg FBX figures may become truly inter-operable.

I've found an easy route from rigged XPS to FBX via free Noesis. It usually 'plays well-ish' with Poser_11. Is there such from MMD's rigged PMX without a total re-build ??

--

*) Long ago and far away, I used to code '6502' for fun, wrote robust 'utility' software for my lab in several BASICs. A wary amateur, I knew my limits, crafted 'clean code'...

Well done !!

( Would like a 'LIKE' Button...)

FWIW, I've now had some success getting XPS to Poser.

Free XNA/Lara can load XPS, export as generic.mesh.ascii, which free Noesis can export as rigged FBX that Poser may read. Downside, will probably import to Poser as multiple sub-rigs. At least textures usually auto-load, PNG quirks permitting. Trick is to find which sub-rig works the skeleton's bones. Usually first in list, but...

If lucky, figure may be posed with care, while the fabrics, props etc politely follow along...

https://www.deviantart.com/higuys920/art/Wonder-Egg-Priority-Rika-Kawai-3D-Model-905990312

The freebie's supplied FBX showed 'all black' in Poser, I could not match all its materials to textures, so I ported the XPS via route above...

IMHO, better use for 'integrated graphics' mini-system is a network-render box, a 'side-kick' for your existing system. Get as much RAM and CPU cores/threads as practicable. The queue-render is not displayed on networked system, so you can wind resolution & refresh down to VGA to make best use of CPU resource...

Okay, it is no substitute for a braw GPU card, but the work-flow is rapidly test-render locally using main PC's GPU, then send full job to 'box' as CPU-only. Now you can continue working at full speed on main PC...

The other side of coin is that GPU cards max-out as scene complexity rises. I found I must progressively 'dial back' vol-bounces and buckets from my twin cards' optimal 1024 settings. Eventually, the GPU cards just 'fall over' with any settings. But, there's no such limits on CPU-only renders, locally or remote, which just take longer.

The Pro has more / better morphs ??

FWIW, I'd like a 'lite' version of 'base' LF......

I've accumulated ample store points for P12, but I've held off upgrading my P/p11 for several reasons.

First, I would have to use Cycles from the start. As yet, I cannot 'grok' more than the very basics, and the recent Cycles version change is as potent as the Python switch. I need a 'Cycles 3.0 for Dummies' book, something that is cross-platform, not just a Blender text.

Second, I want robust rigged-FBX import, as 'take it for granted' as OBJ+MTL, but boned. With a few, honourable exceptions that manage to 'play nice' --Kudos, guys !!--  my understanding is that the rest will stay 'pot luck' until Unimesh arrives to simplify rigging. Meanwhile, there's Mixamo, exporting as FBX version 6.1 (~2016)...

Third, rather than up-grade either of  my twin, now-ageing graphics cards, I realised it was cheaper and more future-resistant to build a network-render 'Box', send jobs to that. Sadly, a lot of P12's super features need super GPUs...

I do sigh when I see the latest 'photo-real' DS figures but, truth be told, I lack both the skill and artistry to make use of them. In fact, I reckon I 'topped out' at VAGM4. Later props and clothing are a different matter, as I'll happily 'rip' such to OBJ+MTL, port to Poser. FWIW, DS' procrustean UI gives me a prompt migraine... 

IMHO, reliable import of  XNA/Lara's rigged XPS, X & ASCII and MMD's rigged PMX would trump Daz' Series 5~6~7~8 figures for most Poser users...

Wow. That's in a different league from my dabblings...

I've learned a bunch of work-arounds for getting different formats / figure conformers into Poser.

I've EE's 'Crossdresser', but not yet got the knack of making results look non-silly. YMMV. 

FBX items are supposed to import freely. Props are usually much more tolerant than rigged figures, but results range from 'Perfect' to crashing Poser. IMHO, the older the FBX version, the better, so eg v6.1 (~2016) is usually better than recent v7.4. There are honourable exceptions. YMMV.

DS' DUF / DSF props may be exported to OBJ+MTL, either using one of several ($$) utilities, or via free DS' own export tools. I found the latter are much faster when model size rises beyond a few MB, although the UI gives me a prompt migraine. YMMV...

MikoMikoDance (MMD) PMD, PMX and X props may be exported to OBJ+MTL from the free PMX Editor (DA), albeit mirrored L/R by default.
Care: MMD 'TDA' models' T&Cs often prohibit such porting. Please respect such.

SFM items and their VTE textures may be ported to OBJ and eg JPG using free Noesis, but that does not generate an MTL or match them up.

XNA/Lara and related "Gary's Mod" items come as .XPS and several types of .ASCII. Free 'Open3Mod', free 'Noesis' and ($$) 3DOC can convert some of these, often dependent on file version. As yet, Noesis cannot grok XPS as-is, but I've had some success exporting rigged .ASCII (Or .MESH.ASCII) to FBX.

Mariokart64's free utility (DA) will usually convert any XPS, X or .ASCII type to MMD's PMX, rigging included, from where props may be exported as above....

So, I reckon the big gaps are rigged XPS and rigged PMX to Poser-compatible FBX.

Note I've made no mention of tweaking in Blender. Unfortunately, the oft-changing sub-versions of both Blender and its I/O plug-ins mean that export to Poser via FBX has horribly unpredictable results. There seems to be an ever-shifting 'sweet spot', such the same work-flow may export well-behaved models one week, chaos the next...

Point taken, Hborre, though I feel 'Institutional Budget' decor suits the scene... "The Therapist Is IN..."

This is quickie Poser CPU test-render, halted when I felt it would work, scaled 50%x50% to spare forum band-width. Box' 100 min run  is 96 pixel-sample, 1089x572.

Yes, I'm going to continue playing with the illumination and render size. Former to much higher emission than this '55', latter to eg 4400*2200, see how it goes.

Really, pic was to illustrate one of the woes & pitfalls of remote rendering. And, may I make another plea for a dedicated sub-forum ??