More of a 'jogging rant' this time.

I've been importing a budget basket of cute FBX anime characters from CGT. (IIRC, flash-sale has now ended.) Typically, Poser cannot locate and auto-load the supplied textures, which means I must open the bundled OBJ's MTL file as a guide. Given many anime model materials and textures have glyphs in their names, this can prove 'interesting'. Doubly so when zip/un-zip process renders such glyphs unto a mess of dipthongs such as ɻĬÉüÉß.png. Often, though, there's a numerical and/or _SPH suffix, which simplifies identification...

Still, when there's 50+ materials, I usually leave the Material room with a raging headache. Last night, I untangled a model with 94, which is a tribute to all the strong, sweet 'Yorkshire Gold' super-tea I was quaffing...

Question arises: How should FBX material / texture paths be arranged to 'play nice' with Poser ? They can be inspected but NOT edited or copied with AutoDesk's free FBX Toolkit's File Explorer. Using that, if you open a file's Object list, and scroll waaaay down past geometry, materials etc, you may come to the Texture list eg 'Texture 0 ~~ Texture 37'

A texture's FileName and RelativeFilename fields may both hold something like C:UsersUsuarioDocumentsmmdPRO TURBONova pastaCrimson Death Tetoeye.png

Which path, of course, does not exist on your PC... D'uh...

A previous tranche of FBX models included a 'total snarl' as described above. After much discussion with artist, seems his modelling program's FBX-export plug-in was to blame. After he updated it and re-exported FBX, Poser import was okay. I'm told Blender is notorious for even minor version updates breaking 3rd-party plug-ins, be they for PMX or FBX. And, yes, FBX version differences compound the problems...

A 'partial' snarl may sometimes be fixed by telling Poser to zero the model. Which may also back-flip etc, but, hey...

Finding your import is a flock of parts which must be parented to a place-holder is unfortunate. I've a growing list of such that require rigging.

There's another flavour of import snarl, when you open the hierarchy window and discover a zillion 'invisible' components, plus an armature tree or trees. The latter may be collapsed, the former not so. And, that zillion may stick around when you delete the model, so must be killed en-masse via the Hierarchy window...

Upside, if you save model to your Poser library, internal or external, that invisible stuff usually does not re-appear. Downside, the now-tidy tree's internals may be entirely labelled with glyphs but, hey, anime. And, figuring how much you dare pose simple FBX rigging can be fun...