Help | ArchVision | Support
Network Rendering Using the ACM
One of the many features of the ArchVision Content Manager is that it eliminates several of the difficulties associated with network rendering. The ACM can manage paths to your RPC content for all of your rendering nodes from a single point of administration on your network server. If you follow the simple guidelines here, you will be able to quickly configure your RPC Plug-ins for network rendering.
Guidelines for Network Rendering RPCs
- 1.) The ACM should be installed onto a file Server (preferably where the RPC content resides).
- 2.) An RPC Plug-in should be installed onto each of the rendering nodes.
- 3.) RPC content should be located in a directory (folder) that is accessible to all of the rendering nodes.
- 4.) A UNC path should be configured to the location of the RPCs from the ACM.
- 5.) The RPC Plug-in must be configured to connect to the ACM.
1. The ACM Should be installed onto a file Server.
This is recommended because Server Operating Systems are necessary to accommodate large numbers of connections. If fewer than 10 rendering nodes will be present on the network, then it is acceptable to use an ACM installed onto a non Server Operating System.
It is ok if the ACM is installed onto other Servers or rendering nodes, but the RPC Plug-ins should be configured to point to one ACM when network rendering. This will insure that the same content is available to all of the rendering nodes.
2. RPC Plug-ins should be installed onto each of the rendering nodes.
All rendering nodes must have the exact same version of the RPC Plug-in installed to render a scene with RPCs in it. A rendering node without the RPC Plug-in cannot render RPCs and will generate rendering errors.
The RPC Plug-in files can be added to each of the rendering nodes by running the RPC Plug-in installer. Alternatively, the files can be copied to the directories where the RPC Plug-in installer would place them from a node that has already been configured. This eliminates the time necessary to perform the install and configure the RPC Plug-in to connect to the ACM. Files should be copied from their current directories to respective directories on the other rendering nodes. The necessary files for ACM enabled applications are listed below.
RPC Plug-in files
Autodesk ADT/Max/Viz
LightWave
pluginsRPC.dlo
RPC.p
pluginsRPCapi.dll
RPCapi.dll
pluginsRPCcls.dll
RPCcls.dll
pluginsRPCFilterhost.dll
RPCFilterhost.dll
pluginsRPCJpeg.dll
RPCJpeg.dll
pluginsRPCPopulate.dll
msvci70.dll
plugcfgrpcapi.ini
msvcp70.dll
mentalrayshaders_autoloadincludeRPCavMR.mi
msvcr70.dll
mentalrayshaders_autoloadshadersRPCavMR.dll
RPC.cfg
mentalrayshaders_autoloadshadersRPCapi.dll
RPCapi.ini
mentalrayshaders_autoloadshadersRPCcls.dl
mentalrayshaders_autoloadshadersRPCjpeg.dll
Note: RPC Plug-in for Max 6-8 users should run the installer on each of the rendering nodes so that the necessary modifications are made to the registry automatically. Manually copying the files to the correct directories will not work because the registry edits will still be needed.
3. RPC content should be located in a directory (folder) that is accessible to all of the rendering nodes.
This is the most problematic issue that users have. Their content will be configured correctly and the RPC Plug-ins will be configured to connect to the ACM, but the rendering nodes will not be able to access the RPC Content. This is often because the path has been configured locally and the rendering nodes do not have access to non-shared folders. Another issue is user rights. If a particular rendering node cannot access the content due to a rights issue, then it will not render.
4. A UNC path should be configured to the location of the RPCs from the ACM.
A UNC Paths looks something like this:
\servernamesharedrpcfolder
Paths like the following are not recommended:
X:MyRPCfolder (this may or may not work)
C:Program FilesArchVisionRPC Content (this almost certainly will not work)
It is important to remember that just because one of the rendering nodes can access the RPC content does not mean that they all can. Mapped paths, will sometimes work, but they are unpredictable and will vary from rendering node to rendering node. Even if your network rendering appears to work with this configuration, it is not recommended.
Local paths will not work, because the rendering node will look to the local machine for RPC Content. This can only be configured if the RPC content is located in the exact same folder on every machine and mapped correctly. This is troublesome because it costs users a considerable amount of disk space and is cumbersome to manage.
5. The RPC Plug-ins must be configured to connect to the ACM.
The intended use of the RPC Plug-in is for it to access the ACM for all path and license information. It may be possible for a user to configure paths via other methods in their choice rendering products, however the ACM should be used instead to eliminate extraneous paths and simplify the configuration process and management of the paths.
Other Common ACM Network Rendering Questions
Q: Is it necessary to install the RPC Plug-in onto each of the network rendering nodes?
A: Yes, the RPC Plug-in must be installed onto each of the rendering nodes.
Q: Should the ACM be installed onto each of the rendering nodes?
A: No, only one is recommended so that there is only one ACM to connect to.
Q: I only have one license for my application (this only pertains to applications that require the purchase of a license for the RPC Plug-in). How can I network render?
A: It is not necessary to have a license for every network rendering node. As long as there is one license to open the scene, the job can be sent to the other rendering nodes. Please note that Maya users will need to have a Mental Ray License and Mental Ray Shader License for each of the rendering nodes to use the RPC Plug-in (licensed or unlicensed).
Need help? Visit support.archvision.com
