← All ideas
  • Published 25 Jul 2024

Management of Extensions and Addons as global or project-specific

Those who have many add-ons or extensions installed get a Blender that is much slower to open and it is not uncommon for add-ons to have conflicts with each other that generate errors or problems that are difficult to identify and resolve (extensions are new and I don't know if will suffer from the conflict problem like add-ons).

While some add-ons are useful all the time, many are only useful in specific projects. For example, an add-on for vegetation is only useful if the project requires the presence of vegetation, or one that generates parametric cities is not useful in an industrial machine project.

It would therefore be very advantageous to be able to decide which add-ons and extensions are "global", i.e. always active: basically what happens now in the Preferences. However, it would also be very useful to be able to activate add-ons for the current project that will not be activated when Blender is opened but when the projects in which those add-ons is activated is loaded. We are only talking about activation, of course the add-ons must be installed. This would make Blender faster, lighter and with less risk of conflict.

100%

Development Status: Open

Upvote 9 Downvote 0
Michele-Moscon
25 Jul 2024

1 Comment

Maarten77

Great idea. Fully agree that would help a lot. When working in a character file we need things like sculpting and rigging, but no vehicle-rigging addons for instance. When working in an animation file we need animation tools, but no sculpting tools etc.

Sure, there are workspaces, but every project and file is different so that's not the best solution to the problem. Your solution does exactly what we're after I think.

1