Hello!
I'm trying to export globals from one project and import them into another project. Both projects are using the same version of Unity (5.4.3f1) and PlayMaker (1.8.3).
I am exporting/importing by using PlayMaker > Tools > Export Globals in the old project and then PlayMaker > Tools > Import Globals in the new project.
When first exporting from the old project, the tool was generating a "playermakerglobals.asset" file. From the researching I've done, the tool isn't supposed to be working this way anymore, and should be generating a "playmakerglobals.unitypackage" file instead, correct?
Just to be safe, I stuck with the ".asset" file on my first attempt. When opening the new project and attempting to import the globals, the "playmakerglobals.asset" file was visible, but wasn't selectable.
On my second attempt, I went back into the old project and exported the globals again. This time I manually entered ".unitypackage" into the name, and it properly exported a "playmakerglobals.unitypackage" file.
Now, in the new project, I tried again to import globals. This time the file browser allowed me to select "playmakerglobals.unitypackage" for import, but upon doing so, I received the "no globals to import" popup window.
After seeing the "no globals to import" popup, the console stays displaying "Importing globals.." When I click on that console entry, the resulting text says:
Importing Globals...
UnityEngine.Debug:Log(Object)
HutongGames.PlayMakerEditor.GlobalsAsset:DoImport() (at c:/Users/Alex/Documents/Unity/Playmaker/Projects/Playmaker.source.unity/Assets/PlayMaker/Editor/Classes/GlobalsAsset.cs:80)
UnityEditor.EditorApplication:Internal_CallUpdateFunctions()
I've tried searching for solutions but so far haven't found any examples of this happening across the same Unity version - only for people moving between Unity versions.
Any help or guidance greatly appreciated!
