![]() ![]() Keeping a messy plugin folder is a fastest way to "dll hell". ![]() (In the past I had same problems as you, because I wasn't organized) I try to keep things clean so things don't get mixed up so I never have that problem now. LoadPlugin() - I don't know which takes precedence. When things get updated, they often rely on newer dll's newer plugins, newer dependencies so things get brokenĪs for autoloading vs. If you're using the old plugin pack, then you would have to use the older, matching QTGMC version, not 3.3.61 or whatever. Vit hasn't been active in a few years (2014). And if I call LoadPlugin() at least one time, does that mean that the script won't autoload any other plugins anymore? In other words, if I explicitly load the required plugins, I can leave those two obsolete DLLs in the plugin folder? I think the problem might be the missing MSVC runtimes, since I read something about that before ( ). All those three plugins are included in the "Plugin Pack" provided with the v3.32 release of QTGMC ( ), so I'm wondering why Vit would include all three of two are obsolete. And if explicitly loading a plugin fails, but auto-loading does not throw anerror, it probably means that the plugin does not get loaded, and the most probable reasons are a) wrong bitness (32/64) and b) missing MSVC runtimes in the matching version. You should definitely remove the obsolete RemoveGrain/Repair pack if you use the modern RgTools instead. Having several plugins in the auto-load directory which provide functions of the same name is an issue. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |