Yes ipad only.

Yeah the object seems normal in blender, it's a bit strange.

what if you exported the obj from 2.9 and 3.2 and compare the files, would that narrow things down?

Thanks

Hi, I exported in .obj format from 2.93 & 3.2 then imported back to respective versions and I don't see any difference after comparing them.

Without access to procreate it would be difficult to test I guess.

I exported the obj from both versions of blender and opened them up in sublime text and saw something interesting.

Could it be the formatting and or the order of lines that's causing the issue?

in the old version (highlighted) the text is:

'usemtl Material.001
s off'

in the new version (highlighted) the text is:

's 0
usemtl Material.001'

Maybe it's the change from text to binary (line 's off' to 's0') that is the problem or the fact that in the new version, 's0' is above "usemtl Material.001" ?

It could explain why there is no issue importing it back into blender, maybe, I'm just guessing :)

@Kuzey (Kuzey) I can't reproduce the issue here in Procreate. Export monkey models with multiple materials with blender 3.0 & 3.1, and yes the .obj content is slightly different like you mention above, but importing both into Procreate on iPad, everything seems to work fine.

Could you attach your "works fine" and "is broken" .obj files to the bug report?

I redid them, I'll include 3 files:

worksfine.obj is from 2.93.0

broken.obj is from 3.2

broken2.obj is the same as the previous one, but I selected a random square patch on the left side of the head and assigned that to one of the existing materials. This one is the most broken, it has many more layers in procreate.

Hope they help

The old exporter groups all faces with one material under a single usemtl line. The new exporter doesn't and switches back and forth between materials many times.

Perhaps Procreate treats each usemtl line as the start of a different "material slot", while Blender treats all usemtl M lines (with the same M) as reusing the same material slot.

I'll attach a ZIP with two .obj files of a three-material Cube that differ only in this aspect. If BrokenCube.obj is broken and WorkingCube.obj works, then you'll know this is the reason.

So the question is, which is the current industry standard?

The old way or has it changed and is Blender just using the newest convention?

I think I might report this as a bug with Procreate as well, just to be on the safe side.

If this is indeed the industry standard, would it be wise to bring back the old exporter and call it legacy for a few months or so?

Update: I Just sent a bug report to Procreate

I can see an issue with the monkey repro files in Procreate, but I can't quite validate that theory with the simpler "TestCubes" case. It's as if, yes, the fact that 3.1+ obj exporter does not "group" faces by material is creating some issue for Procreate, but it's not as simple as "each usemtl group ends up creating it's own subset". Looks like the Procreate logic in obj importing is "something else".

That said, I think the best course of action would be to fix 3.1+ OBJ exporter to group faces by material again. Who knows how much other random software is out there that implicitly assumes that faces are grouped. I'll try to make that fix.

I gave the link to this thread in my Procreate bug report, hopefully it'll be useful for them going forward.

Thanks everyone and cheers :)