Force Front X Axis is missing in Unreal Engine 5.5

Hey guys, i’m wondering why and where did Force Front X Axis option has gone in new import settings in Unreal engine 5.5? That was a lifesaver for meshes import, especially if you want to use meshes not made for unreal
This is how it looks now

For anyone struggling with the same issue - that option is now hidden in the three dots menu next to the source file path (see screenshot)

2 Likes

Why?

Why are these cherry picked 4 checkboxes separated from the entire rest of the Interchange settings? This is so frustrating.

The current processus is splitted in : translating the fbx file to an internal format, then processing the data based on content structure, metadata and settings, then generate assets and actors.

The … settings are settings that UE needs when reading the FBX file, while the rest are general import settings. And while you can modify general settings and see results immediately by hitting preview, modifying the translation settings will require UE to reimport the FBX from scratch.

So for now, there is a clear UI separation between translation/parser settings and the general import settings.

But I understand that, as is, translation settings are practically hidden.

Wouldn’t it be possible to simply detect the format of the file being imported, and if it’s FBX, show these settings along with the other settings but in a separate panel clearly labeled something like “FBX settings” so that it’s clear to the user that these settings are unique to FBX file format?

How are for example GLTF specific settings handled?

It is more a UI UX discussion that might need to be revisited on the best way to separate between Pipeline settings vs Translation settings. They both fall under “import settings” umbrella but conceptually those two settings are handled in a different way, hence the UI separation.

The translation settings are already different depending on the file format you are importing. If you open the … after importing a gltf or CAD or FBX file you will not have same translation settings.

Which to me seems like even less of a reason to have those FBX settings in such a hidden place :slight_smile: