# Import FBX: Material IDs incorrect?

**URL:** <https://forums.unrealengine.com/t/import-fbx-material-ids-incorrect/384170>\
**Category:** Asset Creation\
**Tags:** fbx-import, unreal-engine, 3DS-Max, question\
**Created:** [February 7, 2017, 12:53pm UTC](https://forums.unrealengine.com/t/import-fbx-material-ids-incorrect/384170 "2017-02-07T12:53:27Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![anonymous\_user\_0350c162](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@anonymous\_user\_0350c162](https://forums.unrealengine.com/u/anonymous_user_0350c162)\
**Post date:** [February 7, 2017, 12:53pm UTC](https://forums.unrealengine.com/t/import-fbx-material-ids-incorrect/384170/1 "2017-02-07T12:53:27Z")

</div>

Im made screenshots that show the problem better than me trying to explain it. Basically I’m trying to import a static mesh with two materials on it. I assigned the material IDs in 3DS Max but they seem to make it over to UE4 only partially correct. I am using the workflow as described in the [UE4 docs][1], creating a MultiSub-Object.

What am I missing?

 ![125256-export_problem.jpg](https://d3kjluh73b9h9o.cloudfront.net/original/4X/4/a/7/4a78d7778aca3129ff0ab89036168c924641f172.jpeg)

EDIT: After remodeling the mesh, the problem fixed itself. Still not sure what caused it in the first place though.

EDIT 2: It seems that manually triangulating the poly before exporting the fbx, fixes the problem. So maybe the automatic triangulation messes things up somehow.

---

<div class="post-metadata">

**Author:** ![Mauron](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@Mauron](https://forums.unrealengine.com/u/Mauron)\
**Post date:** [July 12, 2017, 3:20pm UTC](https://forums.unrealengine.com/t/import-fbx-material-ids-incorrect/384170/2 "2017-07-12T15:20:00Z")

</div>

Hi, I have found a workaround:

1. Create a new object, anything, a box or a sphere.
2. Convert the new object to Editable Poly.
3. In the new object, click Attach and select the mesh with ID problems.
4. Select by Element and delete the new object.
5. You will need to fix your pivot and probably Reset the Xform of your mesh.
6. Export!

I hope it works for you too.

---

<div class="post-metadata">

**Author:** ![JTubb](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@JTubb](https://forums.unrealengine.com/u/JTubb)\
**Post date:** [February 8, 2019, 2:41pm UTC](https://forums.unrealengine.com/t/import-fbx-material-ids-incorrect/384170/3 "2019-02-08T14:41:56Z")

</div>

Yes! your workaround did the trick. haha, I was banging my head on the desk trying to figure out what was wrong. Thanks, Cheers!

---

<div class="post-metadata">

**Author:** ![Gooseman1977](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@Gooseman1977](https://forums.unrealengine.com/u/Gooseman1977)\
**Post date:** [November 16, 2020, 4:09am UTC](https://forums.unrealengine.com/t/import-fbx-material-ids-incorrect/384170/4 "2020-11-16T04:09:15Z")

</div>

oh god! what a life saver… This fixed the same problem for me as well.

---

<div class="post-metadata">

**Author:** ![Mistelko](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@Mistelko](https://forums.unrealengine.com/u/Mistelko)\
**Post date:** [March 23, 2023, 1:44pm UTC](https://forums.unrealengine.com/t/import-fbx-material-ids-incorrect/384170/5 "2023-03-23T13:44:37Z")

</div>

Thank you so much! I was going crazy here! It worked.

---

<div class="post-metadata">

**Author:** ![james\_rout](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@james\_rout](https://forums.unrealengine.com/u/james_rout)\
**Post date:** [October 5, 2024, 1:34pm UTC](https://forums.unrealengine.com/t/import-fbx-material-ids-incorrect/384170/6 "2024-10-05T13:34:22Z")

</div>

This saved me after 30 mins of troubleshooting, thanks bro.
