Create a ticket

Q100079: Best practices for sharing Mari archives


In many cases artists are required to share their projects. This article explains the recommended way of sharing Mari archives and also elaborates why some practices might not be ideal.


The recommended workflow in a networked environment is to work locally.

For sharing an archive you have two main options:

1) Synchronizing (or versioning) the assets by exporting & importing the textures & shaders

While in pre-3.0 versions this used to be a manual process, the 'Session Scripts' - introduced in Mari 3.0 - allow you to easily export and import content of an archive as sessions. This method is a convenient way to version and exchange files.

Please be aware however that there are still some limitations which should be looked up in the Mari Online Help before making use of this feature.

2) Exchanging archives in the form of Mari's .mra files.

Mari .mra files contain the entire project and is a secure and efficient to store all the data within the project. Due to the larger file sizes, this can be sometimes inconvenient. In those cases it might be worth considering option 1.

We recommend not to have your cache/project directory on a network location as network issues or overloads (e.g. during crunch times) can cause irreversible project corruptions which in turn can lead to the loss of days of work.

Keywords: Sharing, archives, textures, network, Session Scripts

Was this article helpful?

We're sorry to hear that

Please tell us why
2 out of 5 found this helpful