Does anyone have a fix for this issue? When I import this FBX, it is composed of around 100 or so separate components but in Poser the scale and rotation of the individual components don't maintain their relative positions. Here are 3 screenshots of different imports to different software. Autodesk FBX Review opens it correctly but that software is just for viewing, no editing or even saving. Blender imports most of the model correctly but a number of parts are translated out of position. Poser is worst of all, all parts exploded and different scales.

Best guess, it was exported to FBX using one of the 'third party', reverse-engineered plug-ins. Comes close to Autodesk's proprietary format, but Poser is fussy...

( Honourable exceptions for Mixamo's v2016, Truebones' new 'PMX to FBX' utility and anything 'by/from Maya', which usually behave...)

What you could try is 'zero rotations, zero figure'. Sometimes this re-aligns the strays. 

I'd expect the over-all figure may then be scaled, XYZ translated using the first sub-rig listed.

Applying any supplied textures to your zoo of parts in material room is another matter entirely...

Load your FBX into blender, convert it to Xps, load the created xps into blender. Assign your textures if necessary, adjust z axis of model into right position, scale it onto the floor size. Save it again as xps. Now your new xps should load in blender with the right proportions. bones+rigging if you have any, and the textures. now if your model is in the correct position in blender rotate it -90 on x axis and export it as collada. make sure to have a blender save point. Now import your newly created collada version into poser. This procedure will normally fix all the issues you encounter wit Fbx models. This method is used if you have a rigged model if it is not rigged you will need to export it as Obj and assign all the groups before doing so this way you can spawn all the groups in poser in a easy way to make a new rig. 

Forgot to mention:

before exporting to collada you need to merge all the components into one, this is important if the mesh groups are separated in blender this will prevent having loads of parented figure parts when loading the collada into poser , you will have just one figure with all the groups. In Blender select a part of the mesh hit A got to Object and hit Join. Then export as Collada. 

Your blender import already seems to be out of range. Try loading it with the setting " Apply Transform " it might fix the issue. alternative try using a previous Blender version like 2.76 if you still have it , this might load your fbx file correctly. Sometimes these FBX files are just to old and not compatible with newer blender releases. Via Versa

Should work alight .....

Thanks for the responses and procedures! What does that do to the file size? I have this model already in .obj format, even though the geometry is identical the FBX is half the size of the .obj.  At over 500MB, the .obj just won't import and if it did it would be too big to use. The falcon you show pictured is not the same model, this one has a full geometry modeled cockpit and 250 4K textures.. I basically just spent 12 hours in Poser and re-rotated, translated, scaled, and re-parented everything. I still have a few parts left to reposition but this is it so far!

Side Note:

Sometimes the issue with importing 3rd party Fbx is quiet simple, like in your case it might already fix the issue in poser by just 0 the figure. Sometimes Fbx loads with changed scaling un individual parts also rotations might be loading wrong. Check the individual parts it they have changed scaling and rotations, make sure to load the fbx original size in poser not scaling it up or down while loading. if it is just that the position and scaling changed while loading then it is quiet simple to get it fixed right in poser.

Side Note:

Judging by OP's render history thumbnails, hopefully the 250 mb millennium Falcon fbx comes equipped with a janitor droid to clean up after the shenanigans of the crew members lol...

Opps! That should have been edited! I cannot edit that post now, or remove those pics..

Chewbacca expresses keen interest

primorge posted at 1:48 PM Mon, 13 February 2023 - #4455792

Side Note:

Judging by OP's render history thumbnails, hopefully the 250 mb millennium Falcon fbx comes equipped with a janitor droid to clean up after the shenanigans of the crew members lol...

put a "spatial concept" and the word "janitor" and instantly pops up in my mind some good memories with this

𝒫𝒽𝓎𝓁

---

(っ◔◡◔)っ

👿 Win11 on i9-13900K@5GHz, 64GB, RoG Strix B760F Gamng, Asus Tuf Gaming RTX 4070 OC Edition, 1 TB SSD, 6+4+8TB HD
👿 Mac Mini M2, Sonoma 14.6.1, 16GB, 500GB SSD
👿 Nas 10TB
👿 Poser 13 and soon 14 ❤️

primorge posted at 2:34 PM Mon, 13 February 2023 - #4455796

Chewbacca expresses keen interest

𝒫𝒽𝓎𝓁

---

(っ◔◡◔)っ

👿 Win11 on i9-13900K@5GHz, 64GB, RoG Strix B760F Gamng, Asus Tuf Gaming RTX 4070 OC Edition, 1 TB SSD, 6+4+8TB HD
👿 Mac Mini M2, Sonoma 14.6.1, 16GB, 500GB SSD
👿 Nas 10TB
👿 Poser 13 and soon 14 ❤️

Not quite in same league, but I've just been wrangling a couple of budget multi-format 'golf carts' from another site.

Poser, of course, took a serious dislike to the rigged FBX: Not only did the many materials not call the supplied mapped textures, but the cart roofs were skew to carts. My usual trick of zeroing rotations aligned one roof parallel, but that was all.

Time for 'Plan_B': I re-exported the FBX from free Noesis. Now, loading this FBX at default 100% scale prompted Poser to ask me to locate those meaningfully named textures. I also had to manually hide the set's vast sky/backdrop, tint windscreen glass and dial to ~85% transparency...

FWIW, scene complexity crashed my twin GPU cards' superfly render, I had to switch to CPU-only. Networked 'Box' not available as doing a belated Windows' update...

The carts look like they're scaled small.