playMaker

Author Topic: [SOLVED] Editor sometimes loses changes  (Read 3203 times)

ElBueno

  • Playmaker Newbie
  • *
  • Posts: 10
[SOLVED] Editor sometimes loses changes
« on: July 19, 2012, 11:20:34 AM »
About half of the times that I make a change to an FSM, when I run the game, the changes do not take effect. When I get back into the editor, I see that the changes were lost.

For example, I might change the value of a variable, hit enter, then hit Play. I'd see no changes to the behavior affected by the variable in the game, and when I return to the editor, the variable would be back to its original value.

Is this a bug with Unity, PlayMaker, or what?

[EDIT] Sometimes this even happens when I make changes and then save my scene.
« Last Edit: July 22, 2012, 02:53:36 PM by Alex Chouls »

Alex Chouls

  • Administrator
  • Hero Member
  • *****
  • Posts: 3987
  • Official Playmaker Support
    • LinkedIn
Re: Editor sometimes loses changes
« Reply #1 on: July 19, 2012, 02:23:59 PM »
Are you using the latest version of Playmaker? There was a bug in 1.4.2, but it should be fixed in 1.4.3.

ElBueno

  • Playmaker Newbie
  • *
  • Posts: 10
Re: Editor sometimes loses changes
« Reply #2 on: July 19, 2012, 03:12:16 PM »
How would I check what version I'm using?

Lane

  • Administrator
  • Hero Member
  • *****
  • Posts: 2511
  • Mender of the past
    • Cleverous
Re: Editor sometimes loses changes
« Reply #3 on: July 19, 2012, 05:06:43 PM »
The playmaker button up top then About PlayMaker.
Products by Cleverous
|| Vault Core : Database
|| Vault Inventory : Multiplayer Inventory
|| Vault Attributes : Character Stats
|| That Hurt! : Dmg Floaties
|| Quinn : 3D

jeanfabre

  • Administrator
  • Hero Member
  • *****
  • Posts: 15500
  • Official Playmaker Support
Re: Editor sometimes loses changes
« Reply #4 on: July 20, 2012, 03:12:37 AM »
Hi,

 Do you have errors in the Unity console? that could play a role

bye,

 Jean

ElBueno

  • Playmaker Newbie
  • *
  • Posts: 10
Re: Editor sometimes loses changes
« Reply #5 on: July 20, 2012, 06:27:28 AM »
Looks like I was indeed using 1.4.2. I've updated to 1.4.3. We'll see how it goes. Thanks!