Switch to HOST VIEW mode. The configuration is host-wide, some functions like the copy/paste and the services commands must be invoked right-clicking on the host rather than the instance!
the -v 5 flag is passed from Muster to the engine batch render. The command line construction syntax is available inside the Muster template (maya_mr.. in your case). Just modify the verbose level on the template (in the Dispatcher installation folder) and restart the Dispatcher.
To have realtime feedback of the log, open the REALTIME log on each client right clicking on them and selecting Realtime log!
To create a new engine, just duplicate the template inside the dispatcher, and change the TEMPLATE_UID value inside the template itself.
Change off-course the descriptions to help you found the new one. After this, restart the Dispatcher and the clients so you’ll get the new template migrated across each host. Then launch the management console, and configure the paths of the templates for each host.
Try to change the starting path of mental ray. Depending on the configuration, images may be stored on a subfolder of the launching folder. Under windows , you may need to use a mapped drive to have it wokring.
When you render using a renderfarm system, your jobs must be on a network drive, so each node is able to store and read the contents from the same path.
First of all, you should try to render your job through the command line using the Render.exe command.
This is the way Muster uses to launch renders. If you get the same errors, the problem is elsewhere in Maya.
Regarding render times, remember that, when you launch it trough Muster, you’ve the additional scene loading time to take into account, while when you render from Maya, you already have the job in memory. On very fast jobs, you’ll off-course get longer rendering times.
You can put the Maya.env file in the Muster user account home folder, or, you can configure the Maya template to directly change specific environmental variable in the “environment” block of the template.
Check the dispatcher/client logs. This may be a “keep alive” issue. Network is full so there’s no signal sent between the two processes. you can solve the issue increasing the keep alive check on both side. (remember that the client one should be half size of the dispatcher one ).
We use cookies to ensure that we give you the best experience on our website Cookies are also used to send anonymous browsing data to Google Analytics. We give you the option to Refuse our cookies.
