AETemplate error when loading a file and losing connection with material (green

[Anonymous]

I've got a recurrent issue with some files, that is really impacting our current production pipeline.

I'm using Maya 2018 version.

Each time that I'm loading a file, I've got an error message and most of our textures aren't displayed in the viewport, where the character appears all Green.
The error message is this one:

"C:/Program Files/Autodesk/Maya2018/scripts/AETemplates/AEfileTemplate.mel line 638: Object 'textureUvTilingGeneratePreviewButton' not found."

Our current pipeline is the following one:

- Create a character a texture it, then save the file as "Name_Mesh"

- Reference this file, then create the skeleton and Skin it.  Save this file as "Name_Skeleton" version.  everything looks fine here.

- Open the Name_Skeleton file and create the rig for it (I'm using home made Python script for this). Everything still looks fine here.

- Close this last file, then immediatlt reopen it.  This is where I end up with this AETEmplate error, and the character looks all green in every viewport windows.  This is strange and the material still exist when looking in the material editor, and the texture is still displayed correctly in it.  

I've search this forum, and found the answer to nuke my Prefs, but this didn't solved the issue.

Has anyone encountered this, and have a working solution to avoid this ? I've got no idea of why this AETemplate script is called, and what is this TextureUvTilling preview button.

Any idea is welcomed 🙂

Thanks

[Anonymous]

Hello @Anonymous 

Your text is two years old now, and I am currently facing the same situation as you.

With all due respect, have you found the solution?

Thanks,

Laetitia

[Anonymous]

Hi,
Sorry to ear that. Sadly, I never get any working solution for it, and as
it was really hurting our production process, we had to find
other solutions.
We completely abandon the idea of Referencing file that already contains
referenced objects, as it seems to be the source of conflicts.
This works fine like this, but is of course very restrictive. We are
countering this by using some scripts to then recreate our complete
skeleton each time. Not the most convenient way, but at least, we could
move forward.

Cheers