I think you installed the alpha version of Unity 2019.3. Alpha versions are not official releases and change often, so we can’t guarantee support for them. Unfortunately the Unity Hub selects the alpha by default - something Unity is aware of and is planning to fix.

Please install Unity 2019.1 instead. This is the current official Unity release.

What is the full PlayMaker version: PlayMaker > Help > About.

We released an update a while back to fix moving states in 2018.3+

Did you import any scripts recently? From that error I would guess that another script is defining Array in the global namespace, hiding the system Array type.

It looks like the 2019.3 alpha has removed support for the old GUI Element system. You can try deleting the PlayMaker/Actions/GuiElement folder to fix the errors.

Note, it’s better to use an official Unity release instead of a beta or alpha version. We cannot guarantee compatibility with alpha and beta versions since they are not stable yet. Alpha versions especially can change with each release. We try to fix issues as they come up so you can use PlayMaker with the new features Unity introduces in alpha/beta versions, but there might be some lag...

At the same time it’s good to get reports about issues with alpha/beta versions, so thanks for letting us know about this!

I've updated the YouTube mod used by the forums. It should now auto-detect YouTube and Vimeo urls and add the necessary tags to the post.

If you're curious what options are supported, this is the mod:
http://custom.simplemachines.org/mods/index.php?mod=3268

Also, I noticed large images were breaking the layout in posts, so I tweaked the css to set a max-width for img blocks. You can click on the image to see it full size.

Let me know if you run into any issues with either of these changes!

You should be able to click any username and select User Profile > Show Posts.
Do you see that option?

If you're able to share a project with bad performance please PM me a download link so I can check it out. Thanks!

EDIT: Also does collapsing the PlayMakerFSM editor in the Inspector help? Or resetting the windows layout?

We released a patch that should fix this error in the 2019.3 alpha.
Import and install the latest version: 1.9.0.p16