No definitely don’t reference models This is turning into an interesting thread. :)
On this topic, I’d like to share that I used to think so too, until I found these advantages. 1. It protects the names (like with rigs) 2. It saves space on disk (models can be large, and are otherwise duplicated in every version of a rig) 3. It reduces the time taken to save (related to 2, but important enough to highlight) Although this assumes that: 1. References are imported on export/publish (nested references are sometimes confusing) 2. The referenced file doesn’t change (like a fixed version. changes may break previously functional rigs) In my everyday workday, the assumptions are safe to make and benefits are fantastic, especially (3). It means I save more often and as an end result end up with less lost work on crashes and other hazards. For example, if a rig has a dense mesh of 50-100mb, saving on a network can take 3-5 seconds. With a referenced model, saving takes <1 second. Additionally, space savings it enables greater archiving. 100 versions of 100 mb is 1 additional gb for a single asset. In other cases, a mesh can weigh in at 100-500 mb, that’s when you really feel the savings. Food for thought! -- 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/CAFRtmODW3AMWt4vJ0upQEDFdGGiUSnJL3gnPmzuVMGdPNSf54w%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
