Creating new plugins is buggy in 4.14

Development Pipeline & Plugins Plugins
, , , ,
1

I tried to create a new plugin (using the blank template) and encountered the following error when I tried to restart the editor:

Found 'MyPlugin' plugin in two locations (E:\MyProject\Plugins\MyPlugin\MyPlugin.uplugin and E:\MyProject\Plugins\MyPlugin\MyPlugin.uplugin). Plugin names must be unique.

Doing the same with 4.13 works though.

And when I delete all project files and hit “Generate visual studio project files” from the windows explorer, I get this error message:

 Messages while compiling E:\MyProject\Intermediate\Build\BuildRules\AeonModuleRules.dll:
 warning CS2002: Die Quelldatei 'E:\MyProject\Plugins\MyPlugin\Source\MyPlugin\MyPlugin.Build.cs' wurde mehrmals angegeben.
 warning CS2002: Die Quelldatei 'E:\MyProject\Plugins\MyPlugin\Source\MyPlugin\MyPlugin.Build.cs' wurde mehrmals angegeben.
 warning CS2002: Die Quelldatei 'E:\MyProject\Plugins\MyPlugin\Source\MyPlugin\MyPlugin.Build.cs' wurde mehrmals angegeben.
 ERROR: Found 'MyPlugin' plugin in two locations (E:\MyProject\Plugins\MyPlugin\MyPlugin.uplugin and E:\MyProject\Plugins\MyPlugin\MyPlugin.uplugin). Plugin names must be unique.

(The warning states: The source file … has been referenced multiple times.)

I am using a blank C++ project for this, without starter content and using the “Basic Code” configuration.

Steps ro reproduce:

  1. Create a new C++ Basic Code project with 4.14
  2. Create a new plugin using the plugin UI and selecting the blank template
  3. Restart editor
2

I found out that this error does not happen if I add the plugin to a project that I had migrated from 4.13 to 4.14. This bug occurs only on a project that has been created anew with 4.14.

3

Hi rYuxq,

I did some testing on this and was able to confirm the behavior that you described. However, in my case it would only happen if I created a new 4.14 project in the root location on my drive (eg. D:\MyProject). If I created a new folder on my drive and created the project in that folder (eg. D:\MyUEProjects\MyProject), then everything seemed to work fine. Would you be able to confirm that creating a new 4.14 project in a folder on your drive will allow you to add a new custom plugin without any problems?

I went ahead and entered UE-39044 to report the behavior that I observed in 4.14.

4

Yes I can confirm that. Everything works when I dont create the project at the root level of my hard disk. That’s an interesting bug though

5

Confirming that using the 4.14.3 AdvancdedSteamSessions plugin source with source built 4.14.3 UE4 was causing this problem when building required .dll’s for said plugin. Project was on root, added folder to root named “Projects” to move it down a level, built without issue. Been trying to fix this for hours and it was this simple all along…LOL!