Change in Manual Update from version 1.8.3 and 1.9.0?

[PercyPea]

This is more a question but may actually be a bug.

We're currently upgrading a Unity 2017.3.1 project to Unity 2018.2 (beta 10), in preparation for the full release of 2018.2.

We were using PlayMaker 1.8.3 but are now using 1.9.0

One of our FMS's we have ManualUpdate set, but in 2017.3, we could still have call the current States 'FINISH' event and move on to the next state despite nothing actually calling the FSM Update.

In 2018.2b10 with 1.9.0, we have to call the Update to get it working (without it, in the playmaker editor window you briefly see the state jump/arrow flash to the next state, but then it stays on the original state).

Now obviously it seems like if there is a bug, it was actually to do with version 1.8.3. and Unity 2017. But just wanted to check if that is the case, we kind of relied on Actions still firing a Finish Event to move on to another state even when the FSM wasn't meant to update, so if there is a work around, that is great

[jeanfabre]

Hi

2018.2 is giving us trouble for sure, so I wouldn't count on anything stable while 2018.2 is in beta.

 Having said that, it's great that you find cases like that for us to look at this, and thanks for reporting, it does help us a lot to squeeze all these issues and also report back to Unity if needed.

- Could you send us a repro case?
- Is it all states and all finish transition that have this problem?
- What action are you using?

Everything else is working fine?

Bye,

 Jean