Playmaker Forum

PlayMaker Help & Tips => PlayMaker Help => Topic started by: Rabagast on September 25, 2017, 08:21:22 PM

Title: Playmaker 1.8.5 doesn't work in Unity 5.6.1[SOLVED]
Post by: Rabagast on September 25, 2017, 08:21:22 PM
Hi!
When I created a brand new project in Unity 5.6.1 and installed Playmaker 1.8.5, I got a lot of these errors:

TypeLoadException: Could not load type 'UnityEngine.ImageConversion' from assembly 'PlayMakerEditor'.
HutongGames.PlayMakerEditor.FsmEditorStyles.InitCommon () (at c:/Users/Alex/Documents/Unity/Playmaker/Projects/Playmaker.source.unity/Assets/PlayMaker/Editor/Classes/FsmEditorStyles.cs:1103)
HutongGames.PlayMakerEditor.FsmEditorStyles.Init () (at c:/Users/Alex/Documents/Unity/Playmaker/Projects/Playmaker.source.unity/Assets/PlayMaker/Editor/Classes/FsmEditorStyles.cs:1096)
HutongGames.PlayMakerEditor.FsmEditor.OnGUI () (at c:/Users/Alex/Documents/Unity/Playmaker/Projects/Playmaker.source.unity/Assets/PlayMaker/Editor/Classes/FsmEditor.cs:626)
HutongGames.PlayMakerEditor.FsmEditorWindow.DoGUI () (at Assets/PlayMaker/Editor/FsmEditorWindow.cs:95)
HutongGames.PlayMakerEditor.BaseEditorWindow.OnGUI () (at c:/Users/Alex/Documents/Unity/Playmaker/Projects/Playmaker.source.unity/Assets/PlayMaker/Editor/Classes/BaseEditorWindow.cs:72)
System.Reflection.MonoMethod.Invoke (System.Object obj, BindingFlags invokeAttr, System.Reflection.Binder binder, System.Object[] parameters, System.Globalization.CultureInfo culture) (at /Users/builduser/buildslave/mono/build/mcs/class/corlib/System.Reflection/MonoMethod.cs:222)


It worked in Unity 2017.1, but then, there is a problem with Text Mesh Pro.

Does anybody else has problems with Playmaker 1.8.5 in Unity 5.6.1 and Textmesh Pro in Unity 2017.1?
Title: Re: Playmaker 1.8.5 doesn't work in Unity 5.6.1
Post by: Alex Chouls on September 26, 2017, 09:55:31 PM
It seems the Asset Store is kind of buggy at managing downloads for different versions of Unity. It looks like it's trying to import the Unity 2017.1 version of Playmaker (probably the last version you downloaded) into Unity 5.6. UnityEngine.ImageConversion was new in 2017.1 so wouldn't work in Unity 5.6.

In Unity 5.6.1 make sure you go into the Asset Store download manager and re-download Playmaker. This should get you the correct version of Playmaker for the version of Unity you're using. If you've previously imported the 2017.1 version, you may need to restart Unity before and/or after downloading and importing the new version.
Title: Re: Playmaker 1.8.5 doesn't work in Unity 5.6.1
Post by: Rabagast on September 27, 2017, 05:52:43 PM
Hi, Alex!
It worked! Thank you! :D
Title: Re: Playmaker 1.8.5 doesn't work in Unity 5.6.1[SOLVED]
Post by: Alex Chouls on September 28, 2017, 06:38:08 PM
Cool! Thanks for reporting this. I submitted a bug to Unity (Case 954335) and they were able to reproduce, so hopefully, they will fix it...
Title: Re: Playmaker 1.8.5 doesn't work in Unity 5.6.1[SOLVED]
Post by: Rabagast on October 01, 2017, 02:22:03 AM
Hi!
No problem. :)
Title: Re: Playmaker 1.8.5 doesn't work in Unity 5.6.1[SOLVED]
Post by: Marc Saubion on February 22, 2018, 06:03:03 AM
Cool! Thanks for reporting this. I submitted a bug to Unity (Case 954335) and they were able to reproduce, so hopefully, they will fix it...
Hi.

I don't think this was solved. I have to work on 5.5.6 for a client and had the same issue when installing Playmaker. The error message lead me here and even after restarting Unity and redownloading from the asset store, I still couldn't use Playmaker.

Hopefully, I had an older project with playmaker 1.8.3 on it and could install it.

Related error message: TypeLoadException: Could not load type 'UnityEngine.ImageConversion' from assembly 'PlayMakerEditor'.
Title: Re: Playmaker 1.8.5 doesn't work in Unity 5.6.1[SOLVED]
Post by: Alex Chouls on February 27, 2018, 05:53:27 PM
Weird. What version of Playmaker were you downloading?

It could be an asset store bug in that version of Unity.
If you have another version installed, you could try downloading in that version (e.g., Unity 5.4)

Unity has confirmed this is an issue with the current Asset Store. Unfortunately, it seems they don't have plans to fix it anytime soon given their response:

It was marked as "Wont fix" for now and will be touched once revamping the whole Asset Store in the next couple of years. We are sorry for inconvenience.