playMaker

Author Topic: PlayMaker Globals compatibility[SOLVED]  (Read 2891 times)

grahamH

  • Playmaker Newbie
  • *
  • Posts: 10
PlayMaker Globals compatibility[SOLVED]
« on: January 14, 2016, 08:54:52 AM »
Hi,

From the upgrade notes, I see that fsms opened in 1.8 beta cannot be opened in earlier versions of playmaker.

Given that incompatibility, is it possible to export globals from project using PM 1.7.8.3 and import them into a 1.8 version project?

I've tried and can't seem to get it to work.
« Last Edit: February 04, 2016, 01:57:16 AM by jeanfabre »

jeanfabre

  • Administrator
  • Hero Member
  • *****
  • Posts: 15500
  • Official Playmaker Support
Re: PlayMaker Globals compatibility
« Reply #1 on: January 14, 2016, 11:57:36 AM »
Hi,

 yes it works. I am currently trying to go around this myself to distribute the 2d Platformer project.

 what happens when you export/import the globals?

also, are you talking about global events or global variables?

 Bye,

 Jean

grahamH

  • Playmaker Newbie
  • *
  • Posts: 10
Re: PlayMaker Globals compatibility
« Reply #2 on: January 14, 2016, 03:11:04 PM »
Hi,

I think the problem I've got is occurring in the project where I'm trying to export the PlayMakerGlobals.

It affects both global variables and global events.

When I try to export the globals I'm getting the following errors:

Timestamps (8561) and assets (8562) maps out of sync.
UnityEditor.AssetDatabase:Refresh()
HutongGames.PlayMakerEditor.FsmEditorUtility:ExportGlobals()
PlayMakerGlobalsInspector:OnInspectorGUI() (at Assets/PlayMaker/Editor/PlayMakerGlobalsInspector.cs:87)
UnityEditor.DockArea:OnGUI()

and

Asset with GUID ebed278b2f9b51c4b80876a005653238 has empty path but has assettimestamp???
UnityEditor.AssetDatabase:Refresh()
HutongGames.PlayMakerEditor.FsmEditorUtility:ExportGlobals()
PlayMakerGlobalsInspector:OnInspectorGUI() (at Assets/PlayMaker/Editor/PlayMakerGlobalsInspector.cs:87)
UnityEditor.DockArea:OnGUI()


I'm assuming it has something to do with a corruption that has occurred after using source control (but, to be honest, I'm just guessing).

Alex Chouls

  • Administrator
  • Hero Member
  • *****
  • Posts: 3987
  • Official Playmaker Support
    • LinkedIn
Re: PlayMaker Globals compatibility
« Reply #3 on: January 14, 2016, 11:27:25 PM »
You could try just exporting the globals using Export Package. Right click Assets\PlayMaker\Resources\PlayMakerGlobals.asset and Export Package...

 Then Import Globals on the other end...

kavery

  • Full Member
  • ***
  • Posts: 149
Re: PlayMaker Globals compatibility
« Reply #4 on: February 03, 2016, 07:17:48 PM »
I had luck copying and pasting PlayMakerGlobals.asset in windows explorer. There were a few broken associations but mostly intact.