first, the SET keyword does not expect the = , so you need to type SET MYVAR MYVALUE
second, when you use , you need to escape them, in your case, \file04 should be \\file04
Well, the only thing that differs when Muster spawns the process is its environment. Unless you have the environmental variables system-wide, it may be possible that your user has a different one. Try to type “set” into a console, then run a job into Muster with a pre-chunk script with “c:windowssystem32cmd.exe /c env”. This will output the environment inside Muster you can use to compare..
Render nodes and pools are available by default, so if you set the rule as “Enabled” that means the nodes will be enabled. You should declare a specific time lapse where the nodes/pool will be “disabled” too.
Best thing is always look at the template file, it has all the list of the UNMAPPED (mapped fields automatically maps to start-frame / end-frame and so on) mandatory fields, if it is a combo box, you have a list of the possible values !
You can simply change the path of the engine into the renderclient preferences. Under Configure->Templates->Maya sw (or whatever engine you need). If you need to support both versions, you need to create a new template so you can have two different templates pointing to two installations directories. You can just migrate the existing template, and change its name and UID according.
Have you configured the paths to VRAY into the client preferences, under templates->Maya Vray ? It sets up the environmental variables properly to avoid this kind of problem.
Python based dependancies check is scheduled for 8.2.0. This means you will be able to run a script to check if a job is suitable to start (And a chunk off-course). With this build-in API, you can simply query the chunk status of another job and act according. Just 3 lines of code…
I think this is something related to the X window system and Maya 2015, by the way, if the DISPLAY env fixes your issue , you can just modify the templates, to include the environment preparation you need:
def onBuildEnvironment(self, job, chunk, clientTemplatePreferences, existingEnvironment):
environment = existingEnvironment
environment.setValue(“DISPLAY”,”The value you need”)
return environment
You basically need the sets of the Muster frameworks available from within the Python installation. You can either copy the .dylib files where your MClientAPI.so file resides, or export the DYLD_LIBRARY_PATH environmental variable to include the Muster frameworks installation path.
Another user reported the same thing, this has something to do with the environment passed to the process spawn, but unfortunately we are not able to reproduce it.
Are you able to print the environment variable ? You just need to add a print(environment) before line 614 !
Actually with mrtool (upcoming M8 has a complete python API), there’s no way to filter for folders , but you can put into the results column, the job type flag (type into the -jf flag), this will output if the job is a folder or not…
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.
