Announcements

Between mid-October and November, the content on AREA will be relocated to the Autodesk Community M&E Hub and the Autodesk Community Gallery. Learn more HERE.

I keep getting an error message about lookdevx.

I keep getting an error message about lookdevx.

ahyeon251
Participant Participant
867 Views
1 Reply
Message 1 of 2

I keep getting an error message about lookdevx.

ahyeon251
Participant
Participant
Hello, I'm a student who is working on an animation graduation work.
 
I'm currently in the middle of a rigging process, and when I right-click on the joint or Nurbs curve, the following error messages appear. (There was no problem when I chose mesh.)
 
Clearing and reloading Maya altogether does not fix the problem by modifying the prefs file name and opening Maya again.

Actually, there is no problem working on it now, but I am worried that it will be a problem later because the error message appears in red.

Is it okay if I leave it and proceed with the work?


the error messages :

select -r L_leg_ctrl ;
// Error: file: /Applications/Autodesk/lookdevx/maya2025/1.6.0/lookdevx/scripts/LookdevXViewportMenu.mel line 32: No object matches name: L_leg_ctrlShape.surfaceShader

or

select -r joint1 ;
// Error: file: /Applications/Autodesk/lookdevx/maya2025/1.6.0/lookdevx/scripts/LookdevXViewportMenu.mel line 32: No object matches name: joint1.surfaceShader

 

--------------------------------------------------------------------------------------------------------

PS: Please understand that the expression may not be smooth using a translator.

 

0 Likes
868 Views
1 Reply
Reply (1)
Message 2 of 2

DavidxPombo
Observer
Observer

Understanding the Error

The error message suggests that Maya is trying to find a surface shader for your NURBS curve or joint, which do not have shaders assigned the way meshes do. The error is coming from LookdevX, a tool related to shading and rendering in Maya. Since joints and NURBS curves are not renderable by default, LookdevX should not be affecting them.

Possible Causes

  1. LookdevX is interfering with selection menus

    • LookdevX may be trying to apply a shading function to non-mesh objects when you right-click.
    • The script causing the issue is:
      /Applications/Autodesk/lookdevx/maya2025/1.6.0/lookdevx/scripts/LookdevXViewportMenu.mel line 32
      CopyEdit
      1. Maya is trying to apply a surface shader to a non-mesh object

        • This could be a bug, especially if you didn't modify LookdevX settings.
      2. A missing plugin or conflict

        • The error could be from an incomplete LookdevX installation or a conflict with other tools.
      Is It Safe to Ignore?

      If everything else in your rigging workflow is functioning correctly, the error is not immediately critical. However, ignoring it might cause problems later, especially when working with LookdevX or rendering.

      Possible Solutions 1. Disable LookdevX (Temporary Fix)

      If you are not using LookdevX, try disabling it:

      1. Open Maya PreferencesPlug-in Manager
      2. Find LookdevX.mll (Windows) or LookdevX.bundle (Mac)
      3. Uncheck "Loaded" and "Auto-load"
      4. Restart Maya and see if the error disappears.
      2. Manually Edit the LookdevX Script (Advanced Fix)

      If you need LookdevX but want to stop it from interfering:

      1. Open the script file:
        /Applications/Autodesk/lookdevx/maya2025/1.6.0/lookdevx/scripts/LookdevXViewportMenu.mel
        CopyEdit
        1. Find line 32 (where the error is happening).
        2. Look for any code trying to apply a surfaceShader to selected objects.
        3. Comment it out using // and save the file.
        3. Reset Maya Preferences (If You Haven’t Already)

        You mentioned renaming the prefs folder, but try fully resetting Maya's preferences:

        1. Close Maya.
        2. Go to: ~/Library/Preferences/Autodesk/maya/2025/prefs/ (Mac)
          C:\Users\YourUser\Documents\maya\2025\prefs\ (Windows)
  1. Rename the prefs folder to prefs_old.
  2. Restart Maya.

4. Report It to Autodesk (If It Persists)

If the problem continues even after these steps, it could be a bug in Maya 2025.


 

0 Likes