Under v5.2, what could be the reasons the fn entry UnityPluginLoad of a plugin in a WSA build being no longer called? The same source compiled for PCStandalone woks fine. I verified the dll's exports, and other exported functions can be called from scripts just fine, so the DLL is deployed and correctly found. How does one suggest tracking this down? The debug output does not show anything out of the ordinary, [RESOLVED] I had removed the Module Definition file from the linker options, assuming the __declspec(dllexport) in the source file was sufficient. By removing it, all the exported functions were then defined with a '_' prefix. Adding the Module Definition file back into the linker option fixed it.