Problem in Moving Playmaker Globals to another Unity Project[SOLVED]

[Farwest]

I was unsure should I post this topic in Bug Reporting, or Feature Request, in the end I decided to share here.

Problem is, I was working on a Unity project with many Playmaker FSMs I had created. Then I decided to move the FSM's to another Unity project but I realized all the Global Variables are lost, thus the FSMs are no longer working correctly in the new Unity project.

Normally, I have to move the "PlayMakerGlobals.asset" from Project1/Assets/Playmaker/Resources to Project2/Assets/Playmaker/Resources.

However I already have many works done with Playmaker and Global Variables in the Project2. By copy&pasting PlaymakerGlobals.asset will only create further frustrations and replace over my previous global variables.

Is there any better way or fix to move the Globals without pasting over the previous, but by adding a second "PlaymakerGlobals.asset" and continuing using both Global variables?

(Note: under the bottom side of Globals window (opened via upper bar: UnityEditor>Playmaker>EditorWindows>Globals) it is written that Global variables are stored in Playmaker/Resources/PlaymakerGlobals.asset, so I thought moving it from project1 to project2 will solve the issue, but this will create other issues for me)
 

[Alex Chouls]

You should be able to use PlayMaker > Tools > Export/Import Globals to merge globals from another project. Export Globals in the old project and use Import Globals in the new project to merge with existing Globals.

Let me know if you run into problems with this and I'll take a look...

[ToxicFrog]

This video worked for me. NOTE: It did not appear to work at first, but after restarting Unity, all my globals were in the project as expected. So, restart after you do this:

https://www.youtube.com/watch?v=NJrZdlqeAx8

[Alex Chouls]

I didn't even know about that video, thanks ToxicFrog!

[djaydino]

Hi.
Lol i even forgot i made that video!