Hi @3dnator,

 

Please try writing the output of the Python to an FME Feature Store (FFS) writer, then post the resulting .ffs (and sidecar .frs) files here, so we can have a look at the resulting feature. The FFS format is an exact dump of the feature within FME, so it should let us see how it is constructed.

 

---

Hi @3dnator,

 

Please try writing the output of the Python to an FME Feature Store (FFS) writer, then post the resulting .ffs (and sidecar .frs) files here, so we can have a look at the resulting feature. The FFS format is an exact dump of the feature within FME, so it should let us see how it is constructed.

 

test.zip

 

Hi Dave,

 

Here is one .ffs file containing original file and edited mesh imported through binary serialisation and recreated through python caller. Orientation and UV coordinates are different and it is ok. Loosing UV-s is the problem :)

 

 

---

test.zip

 

Hi Dave,

 

Here is one .ffs file containing original file and edited mesh imported through binary serialisation and recreated through python caller. Orientation and UV coordinates are different and it is ok. Loosing UV-s is the problem :)

 

 

Hi @3dnator,

 

The UV texture coordinates apply to an image texture, but you don't seem to have any applied on your meshes. Without an image texture to write, the texture coordinates will be discarded when writing to most 3D formats.

 

---

Hi @3dnator,

 

The UV texture coordinates apply to an image texture, but you don't seem to have any applied on your meshes. Without an image texture to write, the texture coordinates will be discarded when writing to most 3D formats.

 

I understand that. Strange is if you are writing that original file it will keep uv-s but created one will not. After python caller I am using appearance setter but it will create new uvs and not use thoce from python caller. Have tryed allso to apply image to mesh and then to add uvs but becouse it is append it will just add more uvs. What to use in phyton api for applying texture?

---

Hi @3dnator,

In the AppearanceSetter settings, in the section 'Texture Coordinate Generation Parameters', there is an option to use the existing texture coordinates. Please try setting this to Yes.

---

Hi @3dnator,

In the AppearanceSetter settings, in the section 'Texture Coordinate Generation Parameters', there is an option to use the existing texture coordinates. Please try setting this to Yes.

Already tried that, all possible combinations :) it is working with original mesh but not generated one.

 

---

Hi @3dnator,

You will also need to get the AppearanceSetter to set the appearance at the appropriate geometry level for your mesh. By default, it will place the texture on the mesh root, on both sides. You want it to place the texture on the mesh parts, on the front side only, so that it matches your existing texture coordinates.

Please set the geometry Xquery to This part Geometry Type = Mesh Part and Set Appearance On to Front Side.

---

Hi @3dnator,

You will also need to get the AppearanceSetter to set the appearance at the appropriate geometry level for your mesh. By default, it will place the texture on the mesh root, on both sides. You want it to place the texture on the mesh parts, on the front side only, so that it matches your existing texture coordinates.

Please set the geometry Xquery to This part Geometry Type = Mesh Part and Set Appearance On to Front Side.

Unfortunately there is no difference by doing that.

 

 

---

Unfortunately there is no difference by doing that.

 

 

Hi @3dnator,

 

That's strange - it worked for me on the test FFS. Would you mind sending me your complete workspace and a sample of your source data? If you don't want to make it public, you can send it to dave.campanas@safe.com

 

---