Playmaker Forum

PlayMaker Updates & Downloads => Pre-release Discussion => Topic started by: welltold on September 21, 2018, 01:11:01 PM

Title: Unity 2018.3b2 compatibility[SOLVED]
Post by: welltold on September 21, 2018, 01:11:01 PM
Hello,

I was wondering if there was beta version of Playmaker that fixes some of the issues I was having with Playmaker in the Unity 2018.3 beta. I am assuming it has to do with the new nested prefab functionality with errors like this:

Code: [Select]
MissingMethodException: UnityEngine.Object UnityEditor.PrefabUtility.GetCorrespondingObjectFromSource(UnityEngine.Object)
It also seems like opening the action browser doesn't work.

Any help would be much appreciated!

Thanks!
Title: Re: Unity 2018.3b2 compatibility
Post by: krmko on September 21, 2018, 01:21:28 PM
I'm not having that problem. Actually, i don't have any errors.

https://docs.unity3d.com/ScriptReference/PrefabUtility.GetCorrespondingObjectFromSource.html

Does it appear when you try editing a prefab fsm from instance?
Title: Re: Unity 2018.3b2 compatibility
Post by: welltold on September 21, 2018, 01:26:33 PM
What Version of Playmaker were you using? I just have 1.9.0 currently.

Thanks!
Title: Re: Unity 2018.3b2 compatibility
Post by: krmko on September 21, 2018, 01:44:44 PM
1.9.1 beta, but it's the iteration before improved prefabs came out, so i don't think anything's been changed.
Title: Re: Unity 2018.3b2 compatibility
Post by: welltold on September 21, 2018, 03:10:52 PM
Yeah, the error was from editing an fsm on a prefab it was attached to. Do you know how to get access to the beta versions to see if that might fix this issue?

Thanks again!
Title: Re: Unity 2018.3b2 compatibility
Post by: krmko on September 22, 2018, 02:52:32 AM
Contact Jean on Djaydino.
Title: Re: Unity 2018.3b2 compatibility
Post by: jeanfabre on October 04, 2018, 12:28:54 AM
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
Title: Re: Unity 2018.3b2 compatibility
Post by: wilczarz on November 19, 2018, 08:40:54 AM
I can also see the same error spamming the console.
Title: Re: Unity 2018.3b2 compatibility
Post by: Amitloaf on November 25, 2018, 09:33:39 AM
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.
Title: Re: Unity 2018.3b2 compatibility
Post by: Amitloaf on November 25, 2018, 09:43:16 AM
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.
Title: Re: Unity 2018.3b2 compatibility
Post by: Amitloaf on November 25, 2018, 10:55:10 AM
Ok so apparently it happens when trying to mess with fsms in prefabs. Mostly when you accidentally try that from the instance. But also when not. It doesn't work well with prefabs in the current non-beta version. Which makes sense.
Title: Re: Unity 2018.3b2 compatibility
Post by: jeanfabre on November 25, 2018, 11:54:31 PM
Hi,

 uhm... if you have a some steps that I can follow to reproduce, I'll double check.

 Bye,

 Jean
Title: Re: Unity 2018.3b2 compatibility
Post by: monsieureureka on January 15, 2019, 03:36:24 PM
Hello there!

What worked for me is deleting all the objects in the scene and ctrl+z to get them back in and it removed the error!
Title: Re: Unity 2018.3b2 compatibility
Post by: monsieureureka on January 16, 2019, 11:06:31 AM
nope, I lied, still can't use FSM on the new nested prefabs workflow
Title: Re: Unity 2018.3b2 compatibility
Post by: monsieureureka on January 16, 2019, 11:24:06 AM
ok turns out updating on the Asset Store didn't work out and I needed to go through the Playmaker Welcome Screen to install the latest playmaker version and it works fine now