Forum Replies Created
-
-
11th May 2018 at 9:14 am #17032Could you send me a screenshot of your settings as well as the output from the error ?
Thanks
8th May 2018 at 1:56 pm #17027Try to define a system wide MUSTER9 environmental variable that points to your installation directory, and relaunch after effects and the .jsx connector and let me know if this solves your issue. The different network port may be due by the installation of the previous version, did you ever attempt to install muster 8 on your After effects installation ?
By the way, be sure that the port matches the “management port” of the Dispatcher, it should match the port used when you connect using “console” that in turn should be 9881
Regards.
3rd May 2018 at 9:11 am #17025First of all, you should never change a template on a render client. I do not see any reason to tweak a template to solve your issue. By the way, templates are stored on the Dispatcher and changed on it (or using Console), and then after the change, are automatically updated and streamed on the renderclient.
Now about your recent problem, it’s possible that you’ve deactivated the Maya arnold support on the Renderclient and that’s why the job is not starting.
You can try the following:1 – Right click on a node and select supported templates, check that Maya Arnold is effectively enabled.
2 – Configure the renderclient, and under templates->Maya arnold, be sure the check box at the top is selected, otherwise the render engine is disabled for that particular node.
3 – Send us the rc.conf of that client that’s not rendering.I’ve not understood well if now you can store the changes after you configure a client
2nd May 2018 at 9:21 am #17021The current way to configure the Renderclient is through Console as you’re already doing.
If changes are not saved, this is due to the configuration of the renderclient service itself. Did you configure it using a specific user account during the installation (or after the installation using the services system control panel) ? If so, there’s a change the user is not able to write the rc.conf, and this is the reason of the changes not saved when you restart the service.
You can either double check the user permission against the machine (for a full working environment, we suggest to make the user an administrator of the machine, so you won’t hit those kind of problems), or if security is not a concern for you, give Everyone full read/write access to the rc.conf, but this off-course expose a security risk.
1st May 2018 at 8:33 pm #17019The connectors are available on our download page. Just select a version and scroll to the bottom and you’ll find the links to the various connectors.
20th April 2018 at 9:02 am #17011Hi Eric,
Thank you for posting, let us know if you need further help, but I see you’re making the good progresses by yourself.
Have a nice day !
16th April 2018 at 11:46 am #17001Hi Hue03,
The getting started walk-trough should give you enough information about starting using Muster. By the way, if you’re running into specific issue or you’re stuck in a specific installation step, please fell free to ask for it.
On the Mac platform, a usual initial setup is very easy:
1 – Install Muster on the machines by simply dragging it into the /Application folder from the release .DMG
2 – Start the Services control applet. Here you can choose if to install just the Renderclient or the Renderclient and the Dispatcher service. If you’re installing the Renderclient, be sure to configure the IP to your Dispatcher service. Then you can simply start the services in console checking that there’ effective connection, and/or install them as permanent services.
3 – After the installation is successfully, open Console, and connect to your Dispatcher service. Check that your hosts are online, and start configuring the path to the render engine you’re going to use. Just right click on a node, and select “Configure” then navigate to the engine you’re interested it, and double check the path to it.After this initial setup, you can start submitting your first job using the submission view on the right of the Console application.
Let me know if this helps you or you need further guidance,
Regards.
19th February 2018 at 1:36 pm #16657The Java API is directly mapped to the C++ classes available in the wiki classes documentation.
You just need to check that section. Contact the support if you’re stuck with implementing the Java API
19th February 2018 at 1:35 pm #16656chunkGet had a bug where the database ID was expected instead of the chunk progressive ID. It has been fixed in 8.6.19
19th February 2018 at 1:35 pm #16655This is a bug and has been fixed in the latest releases
19th February 2018 at 1:35 pm #16654Sorry for delaying the response but the forum are unmoderated until now, we’ll start to moderate the forums with the release of Muster 9
I think you already have contacted the support for this topic by the way, it seems like your environment is not finding the Python extension for Muster, also you said that you’re using Python 2.6, the standard plugins we distribute are for version 2.7 so that’s why they are not loaded by your Python interpreter. I suggest you to switch to 2.7 or 3.3
19th February 2018 at 1:33 pm #16653We just completed Muster 9 and taking into serious consideration what’s listed here for a future features release.
Thanks!
19th February 2018 at 1:31 pm #16652what versions were you using when you experienced those problems ? the onBuildEnvironment is confirm to work as expected in the latest versions.
19th February 2018 at 1:29 pm #16651some defined attributes like BLENDERFILE are directly mapped to Muster internals, you can check this into the template by looking for the addMappings() functions.
That means, some parameters like the main scene file must be passed with the standard mrtool flags, that in this case is -f
19th February 2018 at 1:27 pm #16650Hi there,
Unfortunately at the moment no, but in Muster 9 close to release, we have a completely redesigned error system where you should be able to have a finer control over the errors reporting
-
