Q100587: Licensing Power Translators and Power SubdNurbs from Modo 15.0 and above with Login licensing

SUMMARY

Modo's Power Translators and Power SubD-NURBS plugins function via Login licensing. Any foundry.com account that has previously purchased the plugins will have a Login entitlement in their account. This article will explain how to use this license on Modo 15 and above.

Due to the retirement of our old Login server on April 30th 2025, Modo 14.2 and earlier will no longer be available on Login licensing. This also means that the Power Translators and Power SubD-NURBS plugins will no longer function on Modo 14.2 and earlier, as the licenses for these plugins cannot communicate with the deprecated Login server. More information on this can be found here:

Q100718: Important update for older versions of Mari and Modo with Login licensing starting April 30th, 2025

 

In the meantime, the following steps can be used to license the Power Translators and Power SubD-Nurbs plugins with Modo 15 and above.

 

HOW TO LICENSE POWER TRANSLATORS and POWER SUBD-NURBS FROM MODO 15.0

On April 30th 2025, support for our old Login server was deprecated. Launching Modo 14.2 and below with the plugins installed will show an "Invalid Plug-in License" error message. The Power Translators and Power SubD-NURBS plugins will function on Modo 15.0 and upwards.

PT_missing_license.png
ST_MissingLicense.png

To activate the Login licenses for Power Translators and Power SubD-NURBS licenses for Modo 15.0, you will need to use your foundry.com login details. However, this process changes depending on whether your Modo license is Nodelocked or Floating, or Login. More information on our various license types can be found here:

Q100266: What is the difference between Nodelocked, Floating and Login licenses?

 

NODELOCKED/FLOATING MODO LICENSES

If your Modo license is Nodelocked or Floating, and you want to use your Power Translators plugin, you may encounter the following error:

PT_missing_license.png

To resolve this, you need to manually activate your Power Translators login license via Modo's licensing dialog. Instructions on how to do this are as follows:

1. Navigate to Help > Modo Licensing...

 

2. You will see a Missing Licenses page, where you should see that you are missing a Power Translators license. You may see a description of the error saying "Failed to find a License". Select Show Status.

 

3. You will now see all the licenses in use. Select Add License.

 

4. Select Login License, which will automatically launch an activation page in your default browser. Check to see if the activation codes match on the licensing dialog and the activation page in your browser, and then select Activate on the activation page. You will then be able to proceed with the activation process.

 

5. You will now be prompted to choose which type of license you want to use. Select Individual.

At this point you will now be able to select your Power Translators plugin to install. Select the plugin and then select Install. Now your Power Translator plugin will be installed and ready to use.

 

LOGIN MODO LICENSES

If you are using a Login Modo license, on Modo 15.0 and upwards, and you have a Power Translators Login on your account, then when you launch Modo, your Power Translators license should be automatically found and activated. However, if this process does not occur, you will need to manually activate your Power Translators license following the instructions detailed above.

 

FURTHER READING

More information on login based licenses and troubleshooting guide can be found here:

Q100282: What is Individual Login licensing and which products is it available for?

Q100285: Initial steps to help solve issues with Individual Login Licensing

 

FURTHER HELP

If you are still experiencing difficulties please create a support ticket to let us know the exact issue encountered and the troubleshooting steps that have been taken.
For more information on how to open a support request, please refer to this article: Q100064: How to raise a support ticket

    We're sorry to hear that

    Please tell us why