ayonUsdResolver plugin fails to load in Maya 2026

Hi everyone!

Theres seems to be an issue with the AyonUsdResolver Binary for Maya2026 (tested in Maya2026.3):

The AyonUsdResolver Plugin fails to load with USD v25.05 with the error:

Error in 'pxrInternal_v0_25_5__pxrReserved__::PlugPlugin::_Load' at line 244 in file D:\Jenkins\workspace\EMS\ECG\ecg-usd-build\full\windows-release\ecg-usd-build\usd\pxr\base\plug\plugin.cpp : 'Failed to load plugin 'ayonUsdResolver': Die angegebene Prozedur wurde nicht gefunden.
 in 'C:/Users/{USERNAME}/AppData/Local/Ynput/AYON/addons/usd_0.1.4/ayon_usd/downloads/Maya2026_Py311_Win_Windows_AMD64/ayonUsdResolver/lib/ayonUsdResolver.dll''

However, with USD v24.11 the plugin loads without errors. But, as stated in the AYON Maya OpenUSD Workflow the resolver fails to resolve the entity URIs.

Below a summary of the log (I deleted some lines) where you can see that the binarys are initilized correctly at startup.
(Don´t mind the Rez Launching - I also tested it without Rez, with just a clean vanilla Maya 2026.3 install and it gives me the exact same error.)

PS C:\Users\sophia.zauner\AppData\Local\Ynput\AYON\shim> .\ayon_console addon applications launch --app maya/dws-maya-2026 --project dev --folder assets/element/torus --task lookdev --debug --use-staging
>>> Reached main entry point (0.13s).
>>> Connected to AYON server SERVER_URL
>>> Global AYON connection created (1.12s).
>>> Distribution finished (1.44s).
>>> Bootstrap finished (Total: 1.58s).
*** AYON [1.4.3] ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>>> Using AYON from [ C:\Program Files\Ynput\AYON 1.4.3 ]

...
...
...

  - { AddonsManager }: [  *** AYON addons initialization.  ]
  - { AddonsManager }: [  [X] aftereffects (0.2.16)  ]
  - { AddonsManager }: [  [X] applications (1.3.4)  ]
  - { AddonsManager }: [  [X] ayon_ocio (1.2.2)  ]
  - { AddonsManager }: [  [X] ayon_third_party (1.4.0)  ]
  - { AddonsManager }: [  [X] blender (1.0.19)  ]
  - { AddonsManager }: [  [X] cinema4d (0.1.9)  ]
  - { AddonsManager }: [  [X] deadline (0.7.0)  ]
  - { AddonsManager }: [  [X] houdini (0.9.5)  ]
  - { AddonsManager }: [  [X] max (0.4.0)  ]
  - { AddonsManager }: [  [X] maya (0.5.3)  ]
  - { AddonsManager }: [  [X] motionbuilder (0.1.5)  ]
  - { AddonsManager }: [  [X] nuke (0.4.0)  ]
  - { AddonsManager }: [  [X] openrv (1.1.6)  ]
  - { AddonsManager }: [  [X] premiere (0.1.10)  ]
  - { AddonsManager }: [  [X] resolve (0.5.7)  ]
  - { AddonsManager }: [  [X] slack (1.3.0)  ]
  - { AddonsManager }: [  [X] substancepainter (0.2.14)  ]
  - { AddonsManager }: [  [X] timers_manager (0.2.0)  ]
  - { AddonsManager }: [  [X] traypublisher (0.3.12)  ]
  - { AddonsManager }: [  [X] usd (0.1.4)  ]
  - { AddonsManager }: [  [X] zbrush (0.3.3)  ]
  - { AddonsManager }: [  Has 21 enabled addons.  ]
  - { GlobalHostDataHook }: [  Last workfile should be opened on start.  ]
  - { GlobalHostDataHook }: [  Setting last workfile path: X:\dev\ayon\dev\assets\element\torus\work\lookdev\dev_torus_lookdev_v001.ma  ]
  - { ApplicationLaunchContext-maya/dws-maya-2026 }: [  Executing prelaunch hook: OCIOEnvHook  ]
>>> [  Colorspace management is disabled globally.  ]
  - { OCIOEnvHook }: [  OCIO not set or enabled  ]
  - { ApplicationLaunchContext-maya/dws-maya-2026 }: [  Executing prelaunch hook: PreRemoveLauncherPaths  ]
  - { ApplicationLaunchContext-maya/dws-maya-2026 }: [  Executing prelaunch hook: MayaPreAutoLoadPlugins  ]
  - { ApplicationLaunchContext-maya/dws-maya-2026 }: [  Executing prelaunch hook: MayaPreOpenWorkfilePostInitialization  ]
  - { MayaPreOpenWorkfilePostInitialization }: [  Opening workfile post initialization.  ]
  - { ApplicationLaunchContext-maya/dws-maya-2026 }: [  Executing prelaunch hook: AddLastWorkfileToLaunchArgs  ]
>>> [  It is set to not start last workfile on start.  ]
  - { ApplicationLaunchContext-maya/dws-maya-2026 }: [  Executing prelaunch hook: CreateWorkdirExtraFolders  ]
  - { ApplicationLaunchContext-maya/dws-maya-2026 }: [  Executing prelaunch hook: PreCopyMel  ]
  - { ApplicationLaunchContext-maya/dws-maya-2026 }: [  Executing prelaunch hook: InitializeAssetResolver  ]
>>> [  Using resolver from lakeFS: lakefs://ayon-usd/main/AyonUsdResolverBin/MayaWin/Maya2026_Py311_Win_Windows_AMD64.zip  ]
>>> [  Initializing USD asset resolver for application: maya/dws-maya-2026  ]
  - { ApplicationLaunchContext-maya/dws-maya-2026 }: [  All prelaunch hook executed. Starting new process.  ]
>>> [  Launching "maya/dws-maya-2026" with args (5): ['rez-env.exe', 'maya', 'dws_daywalker_config', '--', 'maya']  ]
  - { ApplicationLaunchContext-maya/dws-maya-2026 }: [  Executing postlaunch hook: PostStartTimerHook  ]
*** WRN: >>> { PostStartTimerHook }: [  Couldn't find webserver url  ]
  - { ApplicationLaunchContext-maya/dws-maya-2026 }: [  Launch of maya/dws-maya-2026 finished.  ]

I also tested the Resolver in In Maya 2024 and Houdini 21.0.x (both launched with Rez) the resolver worked perfectly fine there.

So, the question now: Is there indeed an issue with the binary, or did I forget something to make it work in Maya 2026.3?

Cheers!

Hi,

Thank you for reporting this issue. I investigated it, and I most likely found the issue. The ayonUsdResolver for Windows was built against Maya 2026.0, which completely lacks Maya USD 0.33, which includes USD v25.05. Moreover, it is working without any issues and completely ignoring the 25.05 variable with the older Maya 2026 version.

I don’t think building against the newer version will break compatibility with the older Maya2026. I will try building the resolver against a newer version and let you know when it’s finished.

It should be fixed now. I have pushed the new build to this branch lakefs://ayon-usd/fix-maya2026-windows/. You can test it and let me know if it’s working.

1 Like

Just tested in Maya 2026.3 and it works! Thanks for the quick fix, Tadeáš!

I’m glad to hear that! I hope we will soon create a new release with this fix on lakefs.

1 Like