![]() Support for Autodesk Application Plug-in Packagesģds Max will find and load plugins that have a PackageContent.xml file installed in one of the these two standard locations: The DLL search paths are restored to their standard state with a call to SetDllDirectory(nullptr)įor more information see the MSDN topic on Dynamic-Link Library Security.The changes to the DLL search path are in effect for as short of a code-scope as possible.The SetDllDirectory() API is used instead of AddDllDirectory() to modify the DLL search path.Simply deploy the dlls the plugin depends on side-by-side within the same folder where the plugin resides, and 3ds Max will be able to load the plugin.ģds Max expects that code that makes changes to the dll search path respects the following rules: In other words, the dll the plugin depends on does not have to be installed in 3ds Max's root folder ( ), nor does the plugin need to do extra work to load the dlls at run-time (by calling LoadLibrary() for example). Plugin Installation Improved support for loading binary dependenciesģds Max will load dynamic-link libraries (dlls) that plugins have a link-time, or implicit, depency on from the folder where the plugin resides. 3rd party plugins can compile against the official Qt 5.6.3 version. Qtģds Max 2019 uses Qt 5.6.3 which is binary compatible with Qt 5.6.2 used by 3ds Max 2018. This means that plugins will need to be re-compiled in order to work in 3ds Max 2019. The 3ds Max 2019 SDK is not binary backward compatible with the 3ds Max 2018 SDK. Improved support for saving to previous scene file versions of PB1 plugins migrated to PB2.Support for Autodesk Application Plug-in Packages.Improved support for loading binary dependencies. ![]() ![]() ![]() This topic describes new items and changes that affect the 3ds Max 2019 C++ SDK. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |