Editor plugins and "runtime" plugins

[K.Wagrez]

Hello everyone,

I had a question about editor plugins and runtime plugins.

We had in the past extensively used "runtime" plugins, which we loaded dynamically in editor and in our runtime application using -plugin_path and -extern_plugin command line arguments. Recently we started creating editor plugins to replace the plugins we want to integrate more fully into the editor. However apparently for these, we have to place the dlls in the Unigine's installation plugins folder, as is written there Creating C++ Plugin — Documentation — Unigine Developer.

Is there no way to have the same behavior as with runtime plugins, loading them through command line anywhere ?

Thanks in advance.

[silent]

Hi Kevin,

Unfortunately, Editor plugins paths are hardcoded and unified that way to ease the integration with asset store. Editor expects it's plugins to be stored in the exact path and it's currently can't be changed.

Which leads to the question about the use-case that you are trying to solve with this - could you please give us a bit more details what you are trying to achieve?

Thank you!

[K.Wagrez]

Well, we were trying to have the same behavior as before, when we actually had plugins in our editor that could be loaded by command-line.

But that's not a big problem, we will work around this.

[silent]

Thanks for explanation.

Yes, for now you can only unload plugin from Editor menu (Windows -> Editor Plugin Management) or manually in code via unloadPlugin method.

We also plan to extend the Editor Plugin Management window so it would save the preferences and you will not need to disable the same plugins each time you start the Editor, hope that would make things easier in the future.

[K.Wagrez]

Actually it was more about our deployed projects where we used Unigine as a dependency and we build our own editor plugins. We wanted to see if we really needed to deploy our plugins in the Unigine SDK folder, but I guess we do :). More a matter of organizing things