Render On Your Network
KeyShot Network Rendering allows you to take advantage of your network’s computer resources for rendering images, animations, and KeyShotVR’s. After the simple installation process, any user with KeyShot can send a “job” to be rendered on the network. The jobs are organized into a queue that all users can view. Jobs can also be sent from the internal KeyShot queue to network rendering.
How It Works
KeyShot Network Rendering consists of three elements: Master, Slaves, and Queues. The Master manages all of the connected network resources. The Slave does the actual rendering. The Queue shows the jobs that have been submitted to the Network Rendering system by each Slave. After the job is submitted, the Queue can be closed or disconnected from the network without affecting the jobs.
The more cores you have, the faster your images and animations render.
Manage all of the users in your organization with the ability to assign specific privileges based on role or usage. Easily add, remove or change passwords and privileges for each user all from a single screen within the user management system.
Manage your slave computers, scheduling them for use at specific times or days. Set the number of cores allowed for each slave and see immediately what computers are allocated for use, with the ability to utilize computer power without KeyShot being installed.
How Many Cores Do You Need?
Whether you need 32 cores to increase the speed of your smaller rendering processes, 256 cores, or more to bring in the ultimate rendering power, KeyShot Network Rendering has the set-up and scalable options to cut down the time it takes to create renderings and animations.
Note: A virtual core/thread will count as a physical core and is subject to the Network Rendering license’s core limit. For example, an 18 core (36 thread) machine will be calculated as 36 cores by the Network Rendering application. Should you require more than 256 cores, simply purchase additional units until they add up to your final core count.
KeyShot Network Rendering Features
- Master/Slave-System – independent of KeyShot, i.e. KeyShot doesn’t have to be installed on the slave system
- Easy to install and administer – simply install, and follow the instructions.
- New updates will be downloaded from within the network queue
- Network Render queue – everyone can send jobs to the network for rendering.
- User system – allows for user accounts to have manageability over current jobs in queue
- Slaves will be connected automatically by sending packets across the network for detection by the master for connection
- Queue shows current frame being rendered and remaining time of job
- Jobs can be prioritized within the queue
- Supports an “unlimited” number of slaves with any number of cores (physical / virtual)
- Slave tray application, allows the user to update the number of cores being utilized on the network
- Partial image download – if the image is not done rendering, you can download the rendered results.
- Slave scheduling allows slaves to become active or inactive at scheduled times(user system must be enabled, with appropriate privilages)
- Slaves can be added or subtracted anytime, i.e. before, or after rendering.
- Works with all versions of KeyShot 3/4(KeyShot, KeyShot Pro, KeyShot Pro Floating)
- Since KeyShot’s performance increases linearly, the render performance doubles when the number of cores doubles
- Support mixed networks(PC & Mac)
KeyShot Network Rendering is currently available for purchase in the Luxion webstore. To find out more or have a special configuration you would like to discuss, simply contact us below.