[SOLVED] 2.17 Template Editor Plugin is not loaded by Editor

[Amerio.Stephane]

Hi,

With 2.17, I create a new project with a template Editor plugin (named MyFeature), and compile it. The plugin LocalMyFeature_editorplugin_double_x64.dll is correctly compiled and placed in bin\plugins\Local\MyFeature. But when the editor is launched, the plugin is not loaded (not visible in the Edtior Plugin Manager window).

What am I missing?

[silent]

Hi Stephane,

Is there any warnings/errors in console?

Thanks!

[Amerio.Stephane]

The editor_log shows this:

10:12:23 WARNING:    Editor.PluginSystem: Your plugin is ignored by UnigineEditor due to incompatible version/precision.
10:12:23 WARNING:    UnigineEditor v.2.17.0.1 (double precision)
10:12:23 WARNING:    LocalMyFeature_editorplugin_double_x64.dll plugin v.2.17.0.1 (float precision)
10:12:23 WARNING:    
10:12:23 WARNING:    Plugin precision (float) and Editor precision (double) do not match.
10:12:23 WARNING:    Your project seems to be configured improperly. Try adding the UNIGINE_DOUBLE preprocessor definition to your plugin project and rebuilding it.

 

But the plugin IS compiled with UNIGINE_DOUBLE:

(In fact, no modification has been made from the files installed by the SDKBrowser created project)

[silent]

Yep, that's a bug in SDK Browser template generation.

Please check this post that contains a fix:

• https://developer.unigine.com/forum/topic/8707-solved-compile-the-library-with-double-precision-support/?do=findComment&comment=42581

[Amerio.Stephane]

Indeed.

So for completeness, the vcxproj contains the MOC step, which uses $(MOC_DOUBLE) which should be evaluated to -DUNIGINE_DOUBLE but for some reason this setting is missing in 2.17.

Simply replacing $(MOC_DOUBLE) with -DUNIGINE_DOUBLE is enough to make it work. But for a more robust fix, where would you set the MOC_DOUBLE variable?

[silent]

That's internals of SDK Browser and due to the bug in SDK Browser this line is not being replaced to the correct form. Once SDK Browser will recieve an update we hope that this behavior will be also fixed :)