(Copied from original User Voice forum)   "Although the archive option has been there for awhile it retains the absolute file structure a file has when copying the items into a zip file. A more practical and helpful option for handing off project directories would be something that: 01 - detects all paths pointing outside the root of the workspace. 02 - makes a copy of the files into the relative path starting in the same root. 03 - Relinks the nodes in order for the scene to be fully self contained. This allows for various modular workflows and detachable shot work without the need for extended scripting or tool building, as well as minimizing the support need when uploading projects to a cloud environment." Show More

(Copied from original User Voice forum)   "Separating geo from animation using alembic will allow a lighter or FX artist to more easily separate their workflow (dependency) on the geometry received from off a rig or other department. That way a lighting setup/ fur setup with different UV assignments, history, nodes connected etc, can be maintained as a separate process, while only needing to update vertex animation, versus trying to reconnect stuff to new geometry.. Cortex can do this.. Alembic should definitely do this!" Show More

(Copied from original User Voice forum)   "Large image files can quickly bring Maya to it's knees by filling up main system Ram and GPU resources. But more often than not, we have no immediate need to see the full resolution of these image files inside Maya itself. Instead they are merely there to be fed to our final Render engine of choice. Be it Mental Ray, V-Ray, Arnold, etc.  In the meantime, a much lower resolution placeholder would do just as well. In Nuke this is handled by their read nodes having a separate file path entry for a low-res Proxy version of the image(s) you are loading in. Then there are global switches which enable you to tell Nuke to either use the full-resolution files for high quality results or the low-resolution versions for speed and interactivity. Best of both worlds at the flick of a switch." Show More

Offer a limit for the amount of nodes allowed in an object's construction history (to auto-collapse up to the last [X] number of recent history nodes).  This should improve performance, and remove the need to delete history every few minutes. Show More