Ricardo Eloy Posted April 20, 2005 Share Posted April 20, 2005 Hi, folks! I've been wondering about the plug-in manager... I figured that if we can use it to prevent Max from loading certain plug-ins, it would start faster and be less memory demanding then when we start it with all its plugins. The problem is that the plug-in manager does not allow you to unload or even to say "ok, I don't want this plug-in to be loaded next time I start Max". Then, I took the time to choose the plug-ins I don't need from the list and moved them to another folder. Now Max says it can't start because of some rollout.cpp error. What should I do? Did I figure the "faster" part right? Link to comment Share on other sites More sharing options...
abicalho Posted April 20, 2005 Share Posted April 20, 2005 The Plugin Manager only works to tell you which plugins are loaded, which are demand loaded, and it allows you to load other plugins. It's not for unloading them. Removing plugins is not recommended, and it's something you should do at your own risk. Link to comment Share on other sites More sharing options...
Ricardo Eloy Posted April 20, 2005 Author Share Posted April 20, 2005 Thank you for you prompt answer, Alex! Still... do you think I shouldn't create a list of plugins I don't need to be loaded and have them in another directory? You see, Max loads about 26 Mb of plugins I really don't need, so I thought maybe I could decrease loading time (and hopefully make it work using less memory) by loading only the plugins I really need... Link to comment Share on other sites More sharing options...
cadworx Posted April 20, 2005 Share Posted April 20, 2005 what i do is to have the plugins i don't usually need in a seperate folder and pointing to that folder with another "_plugin.ini" (including the standard plugins paths), which loads through a new max shortcut by using the "-p" switch hope this helps a little Link to comment Share on other sites More sharing options...
abicalho Posted April 20, 2005 Share Posted April 20, 2005 You can do it, but as I said, it's at your own risk. Why? Well, some plugins depend on others. Example: you can't remove update1.dlo because it contains things other plugins will depend on. You can't remove CurveCtl, because it's the generic Curve Control manager, so anything that depends on it (Output Map, Reactor, etc) will not work. You can get an application called "Depends.EXE" on the web (http://www.dependencywalker.com/) and that application will show you what DLLs are needed for each DLL. Good luck, Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now