Actually that was the original idea. I was saving out the mesh information i need in a separate file, but it was not enough for our pipeline. The referenced mesh was changing continuously, so that's why I tried to go this way. The purpose of referencing in this case, is to create a 'live' connection with that object, so that whatever stage the referenced mesh is at, the artists can easily have the most updated version, and at the same time I can know exactly which file they are working on. I can still save out this data for each single file which is published and used the reference name to read the relative file, but although it works I think it is a bit messy, and I'd like to find a cleaner solution.
So thanks for the suggestion, but the hunt is still on! :) -- You received this message because you are subscribed to the Google Groups "Python Programming for Autodesk Maya" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/python_inside_maya/32adee0e-b424-438c-a3c7-30c4154d150e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
