Unity version: 5.3.1p1
Previous Playmaker Version: 1.7.8.2
OS: Win7
Having issues upgrading my (pretty large) project to the recommended version of playmaker but I thought I'd ask here before going full on bug report.
Summary:
I have noticed that 1.8's attitude towards getting/setting fsm variables that are not present very is different to 1.7.8.2, unfortuately thats really bad news for me see pic:
http://imgur.com/lhLQ5XnThe previous behaviour was to do nothing - at worst i'd get the odd yellow 'hey no variable' warning so I've been taking advantage of this & treating it like udp and not rellying on variables being present to be set which was very useful until 1.8.
I've also got similar problems with accessing fsm variables from script using ActionHelpers.GetGameObjectFsm & FsmVariables.GetFsmFloat throwing warnings and errors it didn't before.
What makes me really suspicious is the weird ones - like createObject throwing a missing float error message - createObject does not use any floats!
http://imgur.com/vLL4T9RI can repro this behaviour disparity by getting or setting non existent variables in version 1.7.8.2 with no issues & then getting show stoppers in 1.8 doing the same thing.
So thats the bad news - weird thing underneath the error message spam my game is still working just fine, I just have to unpause the game & things carry on as normal until it throws me another.
Seems to me like there is an over aggresive error checker screwing up the works any advise would be welcome on narrowing this down as right now 'everything' is kinda broken by 1.8
Oh btw: disabling realtime error checking, like the goggles, does nothing