- #Remove autodesk backburner 2014 install
- #Remove autodesk backburner 2014 software
- #Remove autodesk backburner 2014 license
MSI files for network deployment packages are available here.Ĭonfiguring RPC PLug-in Dashboard locations without Opening 3D Application All content used in the scene must be accessible to all render nodes.Īs mentioned earlier in this document plug-ins should be installed either via the ArchVision Dashboard or a stand-alone installer obtained here. To configure a content path click on Preferences -> Configure Path then browse to the directory where content is stored. If Dashboard can access the content then it should be available at render time.
#Remove autodesk backburner 2014 software
Also read permission is required for the user that the Dashboard software is running as. Mapped or UNC paths can be used, however UNC paths are preferred as these greatly reduce issues associated with accessibility caused by permissions or user specific mappings. Render nodes do not require licenses.Ĥ) Content must be in a location that is accessible to each of the render nodes.Įach Dashboard can have a path configured to content located anywhere on the network. The computer submitting the render job is the machine that requires the license.
#Remove autodesk backburner 2014 license
If no license is present then watermarks will be displayed. If a license is found then content will render without watermarks. When a user submits a render job, the application connects to a Dashboard per the configuration made under Configure Content.
When using the Dashboard Service, simply configure rpcapi.ini files to point to the Ip address of the machine running the ArchVision Dashboard Service.ģ) The computer submitting the job needs a license to remove watermarks.
#Remove autodesk backburner 2014 install
For users who do not wish to login to have a Dashboard service content for network rendering they can instead install the Dashboard Service tool here. The Dashboard does not have to be licensed, simply running and have a path configured to the content. If a Dashboard is installed on the same computer as the render node's plug-in then the plug-in is automatically configured to connect to the Dashboard using IP address 127.0.0.1 (the loopback IP address, which tells the RPC Plug-in to look for a Dashboard on the local computer). Each render node must be configured to connect to a Dashboard. MSI files for network deployment are available here.Ģ. Stand-alone plug-in installers are available for download here. However in larger environments users often want to push out just the plug-in installer. The preferred installation is to first install Dashboard and then use it to install the RPC Plug-in for the desired application. The RPC Plug-in must be installed onto each of the render nodes
There is a document for configuring Autodesk Backburner available here: Backburner Rendering Overview The following explores each of these guidelines in greater detail.ġ. If all (4) of these criteria are met then network rendering via backburner or distributed rendering (V-ray or mental Ray) should be very straight forward. 4) Content must be in a location that is accessible to each of the render nodes.3) The computer submitting the job needs a license present at render time to remove watermarks.2) Each render node must be configured to connect to a Dashboard.1) The RPC Plug-in must be installed onto each of the render nodes.