Features inside Royal Render

	Client averaging	If you have multiple projects at the same time in your company, the server is able to average the clients between your projects. You don't have the problem that if Project "A" sends a lot of jobs, it will block the farm for other projects. With all other render farm managers you have the problem with setting X priorities, reordering the render queue or always re-defining render pools if a new project is rendering on the farm.
	Dynamic and flexible	It does not matter if you shutdown a client, if you disable a client. You can assign or deassign clients for a running job. You can even restart the rrServer, the clients continue to render their current task.
	Intelligent Clients	Configure your client to recognize your working hours (disables itself. With login detection). A client recognizes if the CPU usage is high and it should not start to render. While rendering the client checks the render process and all sub-processes. Automatic enable after x minutes idle time Automatic shutdown after x minutes idle time Renderer freeze detection Render in the background with less CPUs
	Render licenses	Set the number of render licenses you have.
	Service/deamon	The rrClient and rrServer are running as a service. You do not need to be logged in on a workstation to render.
	Local Textures	RRender is able to copy all textures of a scene to the local harddrive. For XSI and Maya you have a new "send scene" command, which changes all texture paths, then saves the scene under a new name. The client checks if the texture already exists on the local harddrive. If not, it copies the texture and starts rendering. It keeps track of changed textures (size, date, directory) and a free space limit for the harddrive.