in Registry by
Like without the users having to each run a licensing tool the first time they run it?

1 Answer

0 votes
selected by
Best answer

Unfortunately, at the moment when the user is using MG-Picker Studio with a floating license, it is required that on each user's machine, he/she needs to run the license connector.

This requirement might be removed in future versions, but for now, it is needed.


However, you can make the whole process automatic.

First, you just put the connector program and relevant libraries in a central, read-only place. 

To set up the connector path so when the user clicks `Misc Menu /  floating license: login`, there are three ways, each will work, just choose the one that best suits your situation:

  1. Tell the user the path to the connector executable, so the user can manually pick them up for the 1st time they log in to the floating license. 
  2. Somehow set the environment variable "MGPICKER_FLOAT_LIC_CONNECTOR_DIR".
  3. Setting the value in the server config file. The text-based setting file is in MGPicker_ServerConfig/ServerConfig.txt. Edit the `currentPickerProject = ` value and save it in that central location. Use  `!currentPickerProject = ` to force it to override the user manual preference if you need to.

When the connector launches, how to avoid asking the users to input the credentials

The process above is a one-off process. The next time the user launches the tool, the connector will be launched automatically and their tool will be licensed.


What if in the future new MG-Picker Studio version is released?

  • Back up the MGPicker_ServerConfig/ServerConfig.txt file, override the program files, and restore MGPicker_ServerConfig/ServerConfig.txt. If you choose to put a new version in a different folder, you can choose to manually edit the ServerConfig.txt or copy it over.
  • That shall be all you need to do.
  • Tips: In Windows, the .mll plugin might refuse to be updated if it is loaded in Maya. You will have to ask all users to quit Maya or choose a time when nobody is using it. In Linux or MacOSX there seems to be no such problem.