Hi,
Importing OBJ's with multimat textures seems not to be working in max2017, only the first material is imported.
In max2016 this works fine.
Can this be confirmed as a bug?
thx,
Danny
Solved! Go to Solution.
Solved by ksdd567. Go to Solution.
Thanks for your input, I am actually using Max 2017 SP1.
Maybe it is something about my setup...
May I ask you to test the small attached scene?
scene.max - max2017 testing setup scene with multi materials
OBJ2017.obj - the exported OBJ
> only 1st material gets imported back in 2017, works fine in 2016
Thx!
Danny
Ok, this is what i found so far:
If you export/import obj from 3dsmax it indeed truncates all materials except the first one.(using the example scene you provided)
If i use an external application for exporting obj ( in my case i used Poser/Daz-Studio) it works just fine and all materials are
forming a nice multisub-material in 3dsmax2017.
However if i import into DAZ/Poser from 3dsmax2017 i get all sub-materials but the cube is not visible in the viewports of these applications.
So i guess obj. export is broken in 2017.
Do you agree? Or anyone else?
I also tested with DAZ obj exports and same problem > just 1 material in max2017 (works fine in max2016)
Also with obj's from marvelous designer.
When I export OBJ from max2017 they do seem to work fine in other applications. (tested with max2016 and element3D)
But importing OBJ into max2017 always gives me problems.
Cheers,
Danny
Ok, i`m starting to realize that material handling of .obj import in 2017 works different from 2016.
If you uncheck 'import as single mesh', it no longer creates a multi-sub material for all scene objects.
Instead it creates a material/submaterial of the materials assigned to the specific object only.
Only if you 'import as single mesh' it creates a multi-sub of all objects in the scene (which is the default behavior in 2016)
This rather looks like a well-meant optimization in 2017 than a bug.
Hmm, i still can`t import an object exported from 2017 with multiple mat-id's. Strange.
I am having the same issue importing. Submitted a bug report back in 4/16. Applied sp1 and still have the issue.
Right now my work around is
Import into 2016
Save as .max file
Merge into 2017
Yes, that is also how I manage my workflow for the moment.
Thanks for confirming, hopefully this gets solved in the next SP.
Cheers,
Danny
Has this even been solved? I can not export IDs with OBJ and using Max 2016 certainly makes no sense.
Yes, I know I can export IDs with FBX but in some specific cases I need OBJ