Combine meshes flag not respected on reimport

anonymous_user_b9532c9a · February 17, 2015, 6:11pm

Hi ,

Can you list what steps you are taking when reimporting your meshes?

aviel08 · February 17, 2015, 10:36pm

Absolutely, the model is created on 3DS Max. Exported as FBX 2014.
I import it in UE 4.6 with the “combine mesh” tick off. That brings several meshes to my content window. If I click “re import” on any of those objects it will be replaced with a copy of the entire FBX mesh combined.
I hope that’s clear enough.
.

anonymous_user_b9532c9a · February 19, 2015, 6:09pm

Hi ,

I attempted this on my end but have been unsuccessful. Can you send me a test .fbx that is showing this on your end so I can attempt to reproduce it? Thank you!

aviel08 · February 22, 2015, 5:01am

Hi ,

Please find attached my fbx file.

http://www.filedropper.com/mauhouse

anonymous_user_b9532c9a · February 23, 2015, 5:24pm

Hi,

This bug has been reported as UE-1434. I have added additional information to assist in discovering the root cause of the error.

aviel08 · May 20, 2015, 1:35pm

Is it gone? I’m still facing it on 4.7.6

anonymous_user_b9532c9a · May 20, 2015, 3:29pm

Hi ,

UE-1434 is still under assessment. We have not been able to reproduce this internally in quite some time, however resources have been dedicated elsewhere as those who were experiencing this bug seem to no longer have it occurring. Do you have a particular asset that is exhibiting this behavior you’d be willing to share? I’ll be happy to take a look and update the bug report with additional information.

SilverDragon · July 18, 2015, 3:29am

I have the exact same problem. It is a real pain to reimport something, the only option is to delete every mesh and import again, losing all your work inside UE4. It is now 07/17/2015 and the same problem persists…

aviel08 · July 20, 2015, 12:51am

It is very frustrating indeed. Let’s share our information to try to give more clues to Epic staff.
I’m using:
-UE4 4.8.1
-Model created in Blender
-Windows 8 64bits

aviel08 · July 20, 2015, 12:59am

Hi , for the follow up. It took me a while since I’ve been waiting to try to replicate the error in different builds. So far I’ve tested it on 4.7.6 and 4.8.1.
No matter what mesh I export the problem seems to persist. I’ll try on 4.8.2 and I might even record it so you guys can watch it.

anonymous_user_5eb35db0 · January 2, 2017, 1:58pm

Has this been fixed? I have just encountered this issue on 4.14.0.

I export my entire model (multiple meshes) and import into UE with combine meshes unticked.

I then make changes in Max, re-save the fbx, and do re-import, but the entire fbx is imported into the one mesh which I wanted to update.

anonymous_user_5eb35db0 · January 2, 2017, 4:15pm

OK I now understand what’s going on, and why myself and others are getting this issue.

My problem was that I was re-saving the whole 3Ds file as an fbx, then doing the re-import, but what I needed to do was only export the single mesh that I wanted to update in UE. Now when I export say box1, and re-import box1 in UE, it’s all great.

This is more about understanding the workflow, rather than a bug. I thought I’d post this for future reference anyway in case anyone else gets stuck!

AnadinX · January 3, 2017, 11:30am

I would disagree with this, as the original set of uassets were created from 1 original FBX file, reimporting uasset should get that one item from the now updated single FBX file.

Deathrey · January 8, 2017, 6:57pm

I’ve just ran into this issue on 4.14.
Re-import imports whole FBX instead of specific mesh.
I’m fairly sure that I was able to re-import individual meshes from one master file before.

anonymous_user_0c62419a · January 11, 2017, 10:29pm

Hi all,

This issue has popped up in 4.14 as a regression and has been addressed. We have the target fix set for 4.15. You can view the issue here: Unreal Engine Issues and Bug Tracker (UE-39798)

Cheers!

-Ed

SwiftLeigh · March 10, 2017, 6:20am

I seem to have this same issue in 4.15 as well. Re-import combines the meshes into each existing static mesh asset selected in UE for import. This kills what should be a very simple workflow to sync models. No combination of different sources or FBX export settings on external 3D tools makes a difference. Has anyone found this to work reliably?

anonymous_user_0c62419a · March 10, 2017, 7:35pm

Hey SwiftLeigh,

This issue was confirmed fixed in 4.15 with the steps provided in UE-39798. Here is the test asset used.

Mesh

Would you mind providing a test asset and a specific list of steps that reproduces the issue (if the steps in the ticket above aren’t valid for your workflow).

,

SwiftLeigh · March 11, 2017, 5:41am

The MultiMesh asset works which got me looking into this further. I reduced a project down to two objects and still have the re-import issue. I then renamed the individual meshes in shorter before exporting and it fixed the case. Please look at the name differences to see what the specific cause in the name is:

Not Working Mesh Name : NotWorking_M_Concrete-Rectangular-Column_750x600mm__1137538_
Working Mesh Name : Working_Column1

Working and Not Working FBX Files

,
Leigh

SwiftLeigh · March 11, 2017, 6:10am

I may have found the error : If you have either of the open or close square brackets in your name then it breaks. Swapping these in and out routinely broke and fixed the test import.

SwiftLeigh · March 13, 2017, 9:34pm

workaround seems not limited to square brackets. Recommend replacing any non-alphanumeric mesh name in your 3D tool before starting a workflow requiring re-import of the individual mesh function in the editor.