PlayMaker Updates & Downloads > Pre-release Discussion

Unity 2018.3b2 compatibility[SOLVED]

<< < (2/3) > >>

Fat Pug Studio:
Contact Jean on Djaydino.

jeanfabre:
Hi,

 I can't repro this. Can you give me some steps to reproduce?

currently, even in beta, you should not try to edit the fsm of a prefab instance, period. This is not supported. what you can do is expose fsmvariables to the inspector, that works for all cases ( nested, overrides management, variants)

 Bye,

 Jean

wilczarz:
I can also see the same error spamming the console.

Amitloaf:
Happens to me whenever I try to edit any fsm. Inside a prefab or just on an object in the game.
It doesn't happen to my friend on the same project though.

Amitloaf:
It seems like something happened and now I can't open the object browser in any fsm.
I did find a workaround!
Open an empty scene. Open the Playmaker Editor. It should stop spamming the error and actually open the Action Browser. Now close everything, go back to your scene and it should work again.
Now we're just left to find what causes this weird limbo state.

Navigation

[0] Message Index

[#] Next page

[*] Previous page