Copy link to clipboard
Copied
I uploaded a character to mixamo https://www.mixamo.com/#/ that has 6 textures embedded into the FBX. The output looks good as seen in the screenshot below but when I click download Collada, it's only downloaded with 1 texture in textures file.
Since the texture is that of the tongue, the output in Blender looks like this:
Is this a Mixamo website bug or is there anything I can do to fix this? What is the reasoning for this result? It randomly picked out the tongue texture.
baking the textures will be the fix but the problem was caused by your converting to Collada
Mixamo is a rigging software not a file converter... but as you figgured out baking the textures together works around it
Copy link to clipboard
Copied
So I'm assuming multiple texturres is not supported on this site so I ended up baking the textures into one using this method
Copy link to clipboard
Copied
baking the textures will be the fix but the problem was caused by your converting to Collada
Mixamo is a rigging software not a file converter... but as you figgured out baking the textures together works around it
Copy link to clipboard
Copied
Thank you so much for your answer and shedding light on this issue. So I assume it's the same problem with this flickering issue? When I download the mixamo file as collada and import the asset into BeamNG I get this flickering result. Do you know what could cause this?
Copy link to clipboard
Copied
ah it's a mixamo bug. when you download as FBX all is fine but when downloaded as Collada, it's putting messed up Custom Split normals on the model. I just cleared the custom split normals.
Copy link to clipboard
Copied
if you uploaded the file in say Fbx then downloaded it in Collada yes that will mess up because Fbx isn't true standard and strange stuff happens when you try to convert it
if you upload the model in [wavefront] Obj then download it as Collada i supect the artifacts go away... if so then no its not a Mixamo bug
you did well to work out a fix
Copy link to clipboard
Copied
Yes you are correct. The problem was actually with my mesh, I did some cleanup and then it all went well.
Find more inspiration, events, and resources on the new Adobe Community
Explore Now