I am preparing a model to export for Cinema4d and have decided that the obj format would probably be the best to respect geometry and textures.
I made a simple test object to check the importer/exporter and wrapper for texture nodes.
The new «wrapper» seems to work well when exporting from blender.
It writes an .mtl file and seems to point the image textures to right places, (although places Normal maps as Bump)
The exported .mtl file describes the material like this:
Blender MTL File: ‘test.blend’
Material Count: 1
Ka 1.000000 1.000000 1.000000
Kd 0.800000 0.800000 0.800000
Ks 0.500000 0.500000 0.500000
Ke 0.000000 0.000000 0.000000
To check the file I tried importing it back into blender, unfortunately when I try to import the obj file (exported with blender) the «wrapper» mixes the maps up.
It maps the metallic image to the diffuse colour input with reflection coordinates as vector input, and drops the diffuse colour map and the roughness map
The original node setup is this:
The node setup that is produced after import is this:
It is strange that blender mixes up .mtl files that it has made itself.
Does anybody know if I am doing something wrong?
I read the documentation in the manual about OBJ and the wrapper and think I have followed the convention.
I have had success if I only use colour and Normal map, but I would like to include metallic and roughness maps as well. Simple values for metallic and roughness also work properly. The problem arrives when I plug in the image maps.
A second question would be that I also I have no idea how Cinema4d will interpret the texture, I have prepared the test .obj with texture maps in a zip file.
Here is the zip file:
TestObject.tar.gz (110.6 KB)
If anyone reading has Cinema4d, could you kindly import it and see how Cinema4d handles it?
It should look like this:
Many thanks in advance!