Problems setting variables on FSMs via a custom inspector on prefabs

[cheese_block]

I've been having problems with my script. I'm using a custom inspector which changes the variables in a playmaker FSM in the editor - this seems to work fine. However when the custom inspector makes changes to a FSM on a prefab - the changes appear in the editor - but at runtime the variables switch back to their old variables. It only seems to happen when the FSM is on a prefab - does anyone have any ideas why this might be happening? Anything I might have missed?
Thanks

[Christoph]

What custom inspector? How does it work?

[djaydino]

Hi.
Probably some 'Set Dirty' issue changes are probably not saved until you do a set dirty. (like with scriptable objects)
but I believe PM has its own version of it, but I forgot what it was.

maybe you can find something in the PlayMaker API

[cheese_block]

I built a little custom inspector (based on Editor class) to make changes to a referenced FSM.

It does indeed look like I needed to use the "Set Dirty" flag - that seems to have sorted it out.

Thanks

[Christoph]

Can you share more about this? Curious, is it similar to the "Playmaker Controls" component?

[cheese_block]

I've created a custom inspector using the Editor class - I associate it with an FSM and it shows it's variables. I can then put these inspectors at the top of a hierarchy and change several FSM from one place. I can also add my own functionality to speed up filling in variables.

The Set Dirty flag fixed the initial problem where the variables were being reset on play. However now I'm getting some weird, scary behaviour where chunks of the hierarchy seem to be deleted after hitting play and then stopping, which is worrying. I see lots of "Failed to unpersist" in the console - so possibly it's similar to the problem mentioned here:

https://hutonggames.com/playmakerforum/index.php?topic=25455.0

[djaydino]

Hi.
If you Are using Enter Play Mode Setting, that might be the issue

[cheese_block]

Hi - thanks for the reply - not using the Enter Play Mode options.

It only happens when the gameobject is in a scene that's been loaded additive - possibly that's connected. I'm going to dig into it today.

[cheese_block]

The problem doesn't actually seem to be with my custom inspector script - it happens the same if I just change variables directly on the FSM. It certainly seems to be to do with multiple scenes and possibly to do with what's selected in the scene (though this seems inconsistent).

If anyone has any other ideas or has come across the problem please let me know. There does seem to be plenty of people online having this problem with Unity and not many solutions to it.

Thanks

[Christoph]

Ah that's cool. I wished I had the knowledge to do stuff like this myself. Question remains though: why don't you use Playmaker Controls component for this? In my understanding it does exactly what you want it to do.

Otherwise I can't help unfortunately, hope you resolve the problem soon.

[djaydino]

Hi.
@Christoph

well that's not really true

you can make an editor window and set values directly from that window, which can be very helpful for balancing you game.

in our game I Actually use Scriptable objects for data so that we can adjust @runtime.

[Christoph]

Maybe I just can't imagine it can you show me a screenshot to see an example?

[djaydino]

Hi.
Here is a small part of my editor window



but you can also change values directly on scriptable objects

[Christoph]

Oh wow, this is amazing. I can definitely see why and I wished I had the knowledge to setup something like this. Any place where I could start learning about it that you recommend?

[cheese_block]

That looks great! Hoping to create something similar for our game. Just need to try and solve this "Failed to unpersist" problem first.