Problem when merging objects with duplicate name materials (max 2016)

[Linkfoto]

Goodmorning. We have a problem (probably a bug) with the objects merging from different scenes.

When we merge an object from a different scene that have materials with a name that is the same as one in the current scene, it asks what to do with it, as usual. The problem is that, if the materials are multiple, it applys the same choice to all the merged materials with duplicate name, even if the "Apply to All duplicate" checkbox is unchecked. So, if I tell to use the first merged material, it uses also all the other merged materials instead of the scene materials. But usually I want to decide for each duplicated material. But with this bug is really easy to mess up the scene materials. The only solution is to rename all the merged materials, but this is not good with important ones.

Can anyone help or tell if this is a known bug? This happens all the times. Is there a solution? thanks.

[jon.bell]

Hello,

I've tested your instructions and created new example scenes for this report, and you're right -- this is unexpected behavior. If you don't check the Apply to All Duplicates button, but manually replace specific same-named objects in your scene, you expect that manually replacing same-named materials would work on an individual basis as well.

This behavior may be connected to an existing defect we have logged in our internal database, and I've updated it for our developers, using your new example (and test scene files I created.)

A possible workaround is to save multiple copies of your scene material libraries, incrementing them as you change the materials. If you merge objects into your scene and find they are using the "unexpected" version of a material, you can load the most recent material library and replace the material with the correct one.

Please let me know if this suggestion works for you.

Best regards,

Jon A. Bell

Autodesk Technical Support

[Linkfoto]

Thankyou for your reply. Is it possible that the fix for this problem will be a patch for max 2016? We wouldn't like to update to 2017 just to fix this bug (when 2017 will be available). Updating all the workstation we have would be a pain, so having the fix in a product update will make us save a lot of time.

Thanks!

[jon.bell · Accepted solution]

Hello,

I can't say for certain that a fix for this will be in an upcoming 3ds max service pack, or full release, but I have attached your defect information and my own custom testing file to a similar Material Merge defect logged in our developer database, and I'll continue to monitor it.

In the meantime, my suggested workaround is to save copies of your material libraries (incrementing their names by date or version number) and/or incrementing your material names as necessary when you make changes to them (e.g., Wood Parquet_Floor_017 becomes Wood_Parquet_Floor_017-B, or whatever naming convention works for you.)

If I hear back from our developers on this issue, I'll let you know.

Best regards,

Jon A. Bell

Autodesk Technical Support