IMHO, Autodesk SDK versions are usually okay, but the reverse-engineered, open-code versions from eg Blender can be very problematic. Especially when tiny plug-in updates carry format on/off 'sweet-spot'...

In general, I've found that the older the version, the better, as less scope for 'genetic drift'...

eg Maximo's rigged freebies in FBX 2016/v1.60 format are usually well-behaved...

FWIW, I routinely port XPS figures via .MESH.ASCII and Noesis to FBX for Poser.

Some are very good, some okay, some just about usable, and I'd have to set [PROFANITY] flag to describe the rest. YMMV...

Glad resolved..

Sounded unpleasantly like scene corruption due FBX imports 'breaking bad'. You can see entire scene, but only parts will render. Poser has lost track of much, and saving scene as PZ3 is too late. What's lost is lost. You must close Poser, swear eloquently, have a mug of 'caffeinated' and start over...

Upside, if you parent an FBX's many (>>10) 'junior' sub-rigs to the 'master' sub-rig promptly after import, seems to avert such horrors. Hierarchy 'root' does not appreciate congestion by a surfeit of sub-rigs. Analogy is not overloading root folder of eg C: drive with a zillion individual files: organised into sub-folders, they're okay...

Welcome !!

At least your 'Classic' files are still accessible: I keep stumbling across forlorn links to sites that are not only gone, but set 'Do Not Index' flags beyond front page, so their fun freebies are lost from even the 'WayBack Machine'...

Against that, I keep finding 'buried treasures' among the stuff I frantically salvaged from the multiple drive failures that took down both my first CAD-Tower and its complementary Browser PC...

Hi ! Welcome back !!

I find free Irfan View does a lot of stuff that XN View can't, and vice versa. They complement each other. eg, XN View will (slowly) open huge HDRIs that confound IV. But, XN View may try and fail to open a texture file per its suffix, while IV cheerfully announces that eg is a mis-named PNG or JPG, and would I like it renamed ??

;-)

Species & Monsters...

https://www.renderosity.com/forums/threads/2972242/three-eyed-monsters

"Now the 'Burgess Shale' has yielded a Cambrian (~500 MYr) three-eyed apex predator, please, monster-makers, consider a third-eye as a routine option ??"

https://phys.org/news/2022-07-million-year-old-fossilized-brains-stanleycaris-prompt.html

Yeah, that beastie had a big dorsal centre-line eye between the two laterals. (IIRC, we have pineal, which seems to be a re-purposed vestigial third-eye. )

Likewise, 5-fold symmetry per starfish, sea-urchins and Lovecraftian horrors.

Also, 7-fold if possible...

FWW, if an FBX import does not actually crash P_11 I/O, does all its node-building and reaches scene, I've found any flock of sub-rigs may usually be tamed by using Poser hierarchy to parent subsequent sub-rigs to root of first in list. Yes, the one used to pose the figure...

( I used to use a prim place-holder, but dare to try using first sub-rig... )

With a bit of luck, this will off-load Poser hierarchy enough to let you safely move and pose figure.

And, if you use hierarchy tools to rename that first with a nice prefix, it is easy to spot in scene.

With care, you may even use 'Edit, Duplicate' to clone figure. Safer and uses far less resource than importing a second take...

https://www.renderosity.com/gallery/items/3071727/band-of-brothers

Thanks for watching !!

Issue with FBX, as I understand it, is that even P_11  is happy with recent FBX generated by Autodesk's official SDK aka 'Rigged in Maya'. It's the 'third-party' stuff generated by eg Blender plug-ins that are the problem.

I've mentioned else-where that I've seen Blender & plug-ins develop a 'sweet-spot', temporarily generate a bunch of well-behaved rigs. Then, either Blender or its plug-in got a version tweak, and its FBX files stopped 'playing nice' with Poser...

Here's one that only generated a dozen or so sub-rigs on export via Noesis. By using Poser hierarchy to identify, hide then delete surplus options, I got sub-rig count down to five (5)...

https://www.deviantart.com/bringess/art/Darkness-Rises-Assassin-Swimdress-924090002

Ah, some-one else with a 'KiloWatt' Corsair...

Does that have the USB link to mobo for dash-board ??

Y-Phil mentions tweaking 'vols & buckets', and I fully agree. Also, that may take some experimenting to find the 'sweet spot' for each type of job...

This PC has a pair of now-ageing GeForce GTX 750 Ti cards driving four (4) displays. And, yes, a low-flying duty-cat who's just deleted a so-carefully crafted paragraph. For 'modest' scenes, Superfly, progressive, I've found 'vol-bounces & buckets' may both be set to 1024. If cards max-out and scene is blank or missing chunks, I back those off via 512, 256... down to 64, which is what CPU-only renders prefer, be they this PC's weary FX8350 (8 threads) or network-render 'Box' nimble Ryzen-7 1700x (16 threads)...

I have a bunch of 'presets', making it easy to configure render for type of job...

This set-up is no match for a modern GPU card with 'studio' driver complemented by Poser render support, but building 'Box' was a lot cheaper than upgrading to such... 

YMMV, but good graphics cards may tolerate much higher Superfly progressive 'vols & buckets' than running 'CPU-Only'...

Could take some experimentation to find 'sweet spot'... And how complex a scene before you gotta ease those back.

May I suggest...

max out your RAM.

Lots of CPU cores. IMHO, a few more cores are much better than a slightly faster clock-speed. (Do the math !!)

DO NOT keep everything on your C: Drive. Poser thrives on 'external libraries', which limit clutter in your core run-time. So, F:, G:, H: etc. Preferably one removable / slide.

IMHO, does not really matter how fast eg Poser loads from C: as PC will spend much more time wrangling the scene. For other apps, that load & unload modules, YMMV...

You can spend an absolute fortune on high-spec GPU cards. One things is certain, your projects & scenes will out-grow them. Unless GPU & CPU rendering can be combined, you're back to 'CPU-Only', and be very glad of those extra CPU cores...

In fact, IMHO, if you are planning to do 'many' renders', you may do better going for a comparatively modest GPU card for main PC, and spending the savings on a network-render 'Box' . If Poser's 'render queue', it uses CPU-only, so lotsa RAM and Cores, with only a basic 'office' GPU and a small, pre-loved display...

Have you tried setting the library to 'deep search' ?

Also, Windows can be weird when you copy stuff: I've often found folder 'attributes' set to eg 'write protected'. Worse, may take several attempts to 'un-protect'...

In one case, I had to create a new folder, copy stuff from the intransigent whatsit. Finally, with all contents removed, I could clear the protected flag, delete that folder, re-name its replacement...

Thank you, Super-nerd.

As you imply --"~1000 lines"-- skinny-dipping huge text-files spawned by eg OBJ or MC6 is not for the faint-hearted, but at least they are plain-text !!

And, yes, unlike some 'text' formats, tolerate editing... { Have you ever tried to fix bad paths in an 'ascii' FBX ? TSB,NFC !! }

Plus, this hack puts a new perspective on MC6: I've copy/pasted the rudiments of such out to MTL, I'm a tad wiser now...

I may have misunderstood question but, IIRC, GROUND has two materials, one for the floor, other for sky-dome...

Else, some-where down the line, your attempt to buy an up-date, eg from P_12 to Poser'23, will go horribly, expensively wrong: 'No such name, no such number...'

( 'Accounts & Purchasing' are funny like that: I managed to crash the payment system of a 3D site because it said to enter my name exactly as on my debit card. A  'Bobby Tables' failure ensued, as their 'front end' could not parse the multiple dots of my initials. And a big UK cell-phone company did exactly the same, to their profound chagrin... )

Strange...

I do not get any pop-ups on Rendo.

I'm running Win'10, Chrome browser, uber-paranoid Norton's...