You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Table of Contents

This page provides information on how to use Anima on a network.


Centralized Asset Management

Starting with anima® 4.0, it is possible to download and update the models of the library directly from the anima® application. Therefore, if you are going to use anima® on multiple machines connected to the same network, we recommend setting up your “Purchases” folder in a shared location to make sure that all the machines are using the same updated resources.

If you own a subscription account (anima® ALL) it is also a good idea to follow this same principle and share the downloaded models in the same shared network location to use it as a sort of download cache to avoid downloading multiple times the same models. You are not forced to do it because anima® will automatically download any of the assets you may need, but sharing the same Purchases folder with your colleagues will save you time and bandwidth (keep in mind that the new 4D models have a considerable size).

To share your resources with all the anima® installations in your local network (ALL, PRO and Render Node), make sure that all the computers have access to the path where the anima® project is stored (it should be in a network path), just the same as you do when you render any other 3dsMax®, Maya®, or Cinema4D® file in a network machine with Backburner, Batch Render, Team Render or Deadline.


The Purchases Folder

Then you can configure your anima® preferences to set the “Purchases” folder on another network path, in order to share your purchased assets with all the other machines.

To set up the Purchases folder in the anima® Designer application, go to anima® Menu > Preferences:



Then, change the “Purchases” path to set a shared folder on your network. You can either edit the path field manually or browse to a path location using the […] button on the right side.



After that, all the content present in the folder will be moved to a new location automatically.

When you change your “Purchases” folder to another location and the current one already has some models, the dialog from the 2nd image below will appear. As you can read there, if you click the “OK” button, all the assets you have in your current “Purchases” folder will be moved to the new location. However, if you click “Change path” the new path will be set and saved in your preferences, but no assets will be moved nor overwritten. This way you can freely choose to let anima® handle the transference of the assets or manage it yourself.



Whenever you set “Purchases” to any location, a few .xml files and 3 subfolders (“models“, “clips” and “streams“) will be automatically created there. For example, if your “Purchases” path is set to “Z:/_AXYZ_/purchases“, then the anima® actors (all the *.y files) will be placed inside the subfolder “Z:/_AXYZ_/purchases/models“.


Blocked Purchase Folder

Notice that when the alive™ connection is active, the “Purchases” path is blocked on the preferences dialog. We added this limitation when we introduced alive™ to avoid library inconsistencies between the plugins and the core anima® application during the synchronization updates.



You only need to stop the alive™ connection to unlock it that field again by simply closing your 3D application or changing the currently opened scenes in either anima® or the plugin app.


Purchases Folder on the Render Nodes (DEPRECATED)

On the anima® Render Nodes you can also define a Purchases folder, but notice that this is a setting that is only kept to ensure backward compatibility with anima® 4.1.x or older. Since version 4.5.x it is not necessary anymore to set up the Purchases folder in the Render Nodes because they now use the new “resource_cache” subfolder from the same anima® project to get all the assets used in the project, so setting the Purchase folder on the nodes will have no effect at all on the newer versions.

Learn more about this in the following article: Understanding the Resource Cache.


Invisible Mapped Drives

If you have problems to have access to your mapped drives from anima®, it means that the main anima® process “anima.exe” is running in a user environment that does not have those mapped drives mounted yet or in which the access to those drives has been marked as unavailable by Windows (this could happen if the NAS or Server that hosts the network drives was not reachable for a while).

Sometimes you can even open a Windows File Manager and an anima® File Browser in the same user session, but see the mapped drives on one of the windows only. This counter-intuitive behavior is a known issue in Windows systems and is described in full detail in these articles:

This usually happens when anima® is launched from the installer because the installer is always executed with “admin” privileges and the processes that are launched from there are inheriting the same windows environment. If this happens, the problem can be easily solved by closing anima® and starting it again from the Windows Start menu.

If that does not solve the problem, there are two alternative solutions that can also be used to solve this situation:

  • Make sure that the user that is running the anima® process has actually access to those drives and that the drive mapping is also set up on that account. You can see the users related to each process in the Windows Task Manager, at the Details Tab.
  • Use the extended UNC paths instead of the mapped drives. For example, let’s say that the path “Z:\ANIMA_Assets” has a “Z:” mapped drive that corresponds to the UNC path “\\You_server\your_shared_folder“. Then you can replace that part to get the full path: “\\You_server\your_shared_folder\ANIMA_Assets”


Related Topics