KitBash3D changed their FBX encoding version from the 2014 to the 2019 version. Now Poser Pro 11 import no longer recognises KB3D's FBX files. Can we get a fix in the next update please?

FBX was updated in the last version I downloaded (beta) - 11.3.791 (see screen below). I think the latest public release is now 11.3.b813, so maybe check your version number on the about screen and download the installer files again if you're running an older version?

@caisson Thanks so much for letting me know.

On another note, I have a question about the importation of the FBX files into Poser. Why does it dump the pieces into one big clump? What must I do to avoid this mess?

Wait, Poser's FBX amalgamates the meshes?! That's no better than OBJ. I was using Carrara for FBX before, but it's left behind forever. Hmmm...

It imports the file all right but then it just drop them in one big mess, not like OBJ where it is imported as it is set up originally . You will have to move them and it's a big hassle!

Maybe the pieces (what pieces?) were saved as one big clump? More info required - some details and maybe a screenshot of what you're trying to import?

Thank you, ThunderStone, for letting me know, but it's less of a hassle to move things than it is to cut them apart.

This is what it looks like after importing. It was on its side on the ground. The ground plane was made invisible.

Thanks for the screenshot, though I have more questions! What is the model of and what is it's origin - did you make it, is it a freebie, or commercial product? Has it been put together in Poser then exported from Poser as FBX, or has it been exported from a different application, and if so which one, and do you know what the export settings were? Though I can't read the screenshot there is a hierarchy there, so is it a rigged model?

The problem is that FBX has a lot more options and variations than OBJ, which is a very simple format by comparison.

This model is from Kitbash3D and is called Utopia. See this article here for more info about the model.

Excellent, thank you - I have downloaded it, will play around later today and post back with findings!

The FBX opens up like this in Lightwave:

In Poser though I've had to create a simple hierarchy for each group of props and rotate -90° on the xRotate dial, then adjust the yTrans to get that group placed on the ground. Then of course the materials need to be sorted out - this set would require some work whatever application it's used with, as the website for KitBash3D makes clear. Once each group of props has been 'poserised' it would need to be saved to the library as a multi-part prop.

I have found some shading issues with one of the towers in Superfly and I am going to look into it further, but I suspect that Superfly wants more geometry, which is definitely not built for subD unfortunately.

The Lightwave layout shown is similar to the OBJ import within Poser. But it's still a hassle when you do the FBX import. I don't have LW but I do have Hexagon. Maybe I should add Blender to the pipeline. Should have thought of that in the first place.

@4385975 https://www.renderosity.com/mod/forumpro/?thread_id=2935477&page_number=11

I've a 'running rant' about FBX imports on the 'wish list' thread. Here's the short version... First, find an appropriate import scale, which may vary from ~0.5 ~~3500 %. A very, very few FBX models are **correctly **rigged, load like it says on the tin. Posing them is non-trivial, but can be done without re-rigging. Some are 'welded solid' like an OBJ prop. Some arrive as a jumbled heap, per your example above. Some arrive as a flock of free-flying parts, must be parented to a 'place-holder'...

Oh, and if textures etc do not auto-load, there's no obvious way to aim Poser at FBX's associated texture directory per eg 3D Paint and say, 'There you go'. Hand-loading 50+ materials' texture maps etc is a total pain. I've resorted to exporting FBX files as ASCII from AutoDesk's free FBX toolkit, just to get a plain-text listing...

https://www.deviantart.com/nik-2213/art/FBX-and-a-D-uh-moment-837842799

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...