Exit
  • Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
  • 한국 커뮤니티
0

Substance Plugin for Maya 2018 fails to load

Explorer ,
May 01, 2024 May 01, 2024

Hi!
After installing the Substance plugin in Maya 2018.7/Arnold v4021 in my OSX 10136, I am having this error:

// Error: file: /Applications/Autodesk/maya2018/Maya.app/Contents/scripts/others/pluginWin.mel line 290: initializePlugin function failed (substancemaya) // 

Despite this, once in Hypershade/Create(2D textures/Substance Node
Maya just crashes...!
 
Thanks for ANY help!



LAO

TOPICS
Autodesk Maya , Bugs & Crashes , Discussion
3.1K
Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
May 01, 2024 May 01, 2024

Some extras screenshots!

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Adobe Employee ,
May 01, 2024 May 01, 2024

Hi @LAOMUSIC ARTS , thanks for reaching out and providing the additional screenshots. I would recommend trying an uninstall of the plugin files first then downloading the latest version of the plugin for Maya 2018 that can be found at the bottom of our plugin page here.

  1. First navigate to Applications > Substance 3D for Maya. Move the 2018 folder to another location in case you need to restore to this.
  2. Download the updated plugin version.
  3. Run the installer.
  4. Once it is done, open maya and enable all plugin modules.

    Let me know if using the updated version resolved the issue, and if not we can investigate further.

    -Aldo
Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Adobe Employee ,
May 01, 2024 May 01, 2024

Quick follow up in case the above does not work. We are actively supporting the following versions of Maya with our plugin: 2022, 2023, 2024, and 2025. If possible, I would recommend trying with one of the newer Maya versions as well.

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
May 11, 2024 May 11, 2024

Hi Aldo,

still not working. I just did the 2019 installation, but no love:

// Error: file: /Applications/Autodesk/maya2018/Maya.app/Contents/scripts/others/pluginWin.mel line 290: initializePlugin function failed (substancemaya) // 
Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Adobe Employee ,
May 23, 2024 May 23, 2024

Hi @LAOMUSIC ARTS , if possible could you share a more complete output log from the script editor to see the messages that precede the error? That might give us a bit more information. At the moment it's hard to pinpoint down an exact issue, but I have some guesses:

  • Possible special characters in a related directory name are causing an error.
  • Possible that Opengl engine failed to load for some reason (could be described further in other console lines).
  • Possible environment path issues (might also show up in other console lines).


Other than that, I would suggest trying on Maya 2020 or 2023 if that is available to you.

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
May 24, 2024 May 24, 2024

Good morning Aldo,

Here it is what I have:
Error message:

/ Error: file: /Applications/Autodesk/maya2018/Maya.app/Contents/scripts/others/pluginWin.mel line 290: initializePlugin function failed (substancemaya) //

Faulty code bit:

 

global proc loadPluginCmd( string $path )
{
    if(!`pluginInfo -q -loaded $path`)
    {
        catch(`loadPlugin $path`);
    }
}

 

Faulty code line:

 

        catch(`loadPlugin $path`);

 

But this  MEL Script code for loading a plugin looks almost correct, but there are a couple of issues one might want to address:

  1. Semicolon after the catch statement: In MEL, the catch statement doesn't require a semicolon if it directly precedes a command enclosed in backticks.

  2. Error Handling: Although the catch statement captures errors, it's often good practice to handle the error or at least print a message indicating the plugin couldn't be loaded.

Here's a revised version of your script:

 

global proc loadPluginCmd(string $path)
{
    // Check if the plugin is not loaded
    if (!`pluginInfo -q -loaded $path`)
    {
        // Attempt to load the plugin and catch any errors
        if (catch(`loadPlugin $path`))
        {
            // Print an error message if the plugin fails to load
            warning("Failed to load plugin: " + $path);
        }
    }
}

 

Explanation:

  • Error Handling: The if (catch(...)) structure captures any errors during plugin loading. If an error occurs, a warning message is printed.
  • Consistent Formatting: The code is formatted to enhance readability, ensuring consistent indentation and structure.

This version should handle errors more gracefully and provide feedback if the plugin fails to load.

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Adobe Employee ,
May 31, 2024 May 31, 2024

Thanks for the suggestion Lao, I'm flagging this internally so that we can improve the way these errors are reported in the future. Thanks for taking the time to look at that and explaining the suggested changes!

Going back to the main error, I'm not seeing any new info that can be of use in this situation. All I can suggest for the moment is tring again on a 2020+ version, or waiting for our next 3.0.1 plugin release to see if that fixes the issue (this should release soon).

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
Jun 11, 2024 Jun 11, 2024
LATEST

Thanks Aldo!

I just went to the pain stacking process of closing Maya/installPlugin/restart/load plugin for ALL versions from 2018 to 2023.
No luck neither.
I´ll keep checking for ipdates.
Thanks!



LAO

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines