In most cases the easiest way to get Zookeeper running is through the automated online or offline installer. In some cases, though, installing files manually might be required. For example, people managing custom deployment of files for their studio might need to get all the needed files ahead of time and put them into correct directories later. This document describes how to install Zookeeper manually (without the use of an installer provided by us).
Zookeeper runs on top of a framework called Max.NET (also developed by us). This is what loads Zookeeper and, therefore, needs to be installed alongside of it. Zookeeper is compiled against specific versions of Max.NET, but just getting the latest version should generally work fine.
You can follow the Max.NET setup instructions in a document similar to this one.
Zookeeper supports multiple 3ds Max versions. Make sure that you download the correct build for your version of 3ds Max. Zookeeper assembly is 32/64 bit neutral so it doesn't matter how many bits your system has, just the version of 3ds Max. Please note: you must be logged in to this website before clicking on any of the links below.
Once you have finished downloading the .zip archive from previous step extract it into a temporary directory. There should be one file called Ephere.Plugins.Autodesk.Max.Zookeeper.dll
Copy this file into your 3ds Max plugins directory so that you have something like:
C:\Program Files\3dsmax\plugins\Ephere.Plugins.Autodesk.Max.Zookeeper.dll
You can alternatively place this dll into any directory listed inside your plugin.ini file.
The final step involves setting up a license server for your workstation or for your network license machine. This step cannot be performed manually and our installer must be used. However, this only needs to be done once and on one machine so this step does not apply to updating Zookeeper.
You can get full instructions about setting up the license server in its documentation.
You may need to update your 3dsmax.exe.config in the root directory of 3ds max with the information below. This will give windows permission to remotely load .NET assemblies. This is most commonly required on Windows Vista or Windows 7. (remember to save a backup of this file as needed)
<?xml version="1.0"?>
<configuration>
<system.diagnostics>
<assert assertuienabled="false"/>
<sources>
<!-- This removes Binding error messages coming from AdWindows components -->
<source name="System.Windows.Data" switchName="SourceSwitch">
<listeners>
<remove name="Default" />
</listeners>
</source>
</sources>
<switches>
<add name="SourceSwitch" value="All" />
</switches>
<trace autoflush="true" indentsize="4"></trace>
</system.diagnostics>
<runtime>
<loadFromRemoteSources enabled="true" />
</runtime>
</configuration>
