Playmaker Forum
Bug Reporting => PlayMaker Bug Reporting => Topic started by: NateGallardo on August 18, 2016, 06:13:52 AM
-
I've updated two different unity projects to Unity 5.4 and PlayMaker 1.8.2 in the last few days. One went fine once I removed the duplicate scripts that have since been integrated into Playmaker, but the other is giving me a few compile errors.
Assets/PlayMaker Utils/Editor/PlayMakerEditorUtils.cs(102,94): error CS0618: `HutongGames.PlayMakerEditor.FsmEditorUtility.GetActionScriptAsset(HutongGames.PlayMaker.FsmStateAction)' is obsolete: `Use ActionScripts.GetAsset instead.'
Assets/PlayMaker Utils/Editor/PlayMakerEditorUtils.cs(111,90): error CS0618: `HutongGames.PlayMakerEditor.FsmEditorUtility.GetActionLabel(HutongGames.PlayMaker.FsmStateAction)' is obsolete: `Use Labels.GetActionLabel instead.'
Any ideas, team?
-
Hi,
I would suggest you clean up PlayMaker in your project and import again. you may have had some bad merging when installing the update.
Else, the problem could be in another place and when Unity can not compile, other errors popups but aren't the source of the problem. So make sure you look up all errors.
Bye,
Jean
-
Hi Jean,
How should I go about cleaning up PlayMaker in the project? Are there some key folders I should delete and re-import or something?
-
Hi,
yes,
--Delete the "PlayMaker" folder
-- Delete inside "Plugins",the "PlayMaker" folder.
then, you reimport PlayMaker from the Asset store.
Bye,
Jean
-
I removed all traces of PlayMaker from the project, and then started to re-import it all.
It threw up this error after the PlayMaker installation:
Assets/PlayMaker/Editor/PlayMakerProjectTools.cs(220,115): error CS0618: `UnityEngine.ParticleEmitter' is obsolete: `This component is part of the legacy particle system, which is deprecated and will be removed in a future release. Use the ParticleSystem component instead.'
Which I got around temporarily by commenting out that particular line of code. Obviously not a permanent solution, but it let me continue for the time being.
Then, I downloaded and imported Array Maker from the Ecosystem, at which point it gave me those same original errors again:
Assets/PlayMaker Utils/Editor/PlayMakerEditorUtils.cs(102,94): error CS0618: `HutongGames.PlayMakerEditor.FsmEditorUtility.GetActionScriptAsset(HutongGames.PlayMaker.FsmStateAction)' is obsolete: `Use ActionScripts.GetAsset instead.'
Assets/PlayMaker Utils/Editor/PlayMakerEditorUtils.cs(111,90): error CS0618: `HutongGames.PlayMakerEditor.FsmEditorUtility.GetActionLabel(HutongGames.PlayMaker.FsmStateAction)' is obsolete: `Use Labels.GetActionLabel instead.'
So it's clearly linked in some way to the PlayMaker Utils stuff that is imported when I import Array Maker.
-
Hi,
Yeah, ok I see, I need to update the package of ArrayMaker to use the latest PlayMaker Utils.
Can you import ArrayMaker from the ecosystem again, let me know how it goes, PlayMaker Utils files should now be up to date and not giving you any errors.
Bye,
Jean
-
Hi Jean,
I updated Arraymaker, and removed and updated Playmaker, but I still have the same two errors.
-
Hi,
uhm... let me run some tests locally, I'll get back to you on this.
Bye,
Jean
-
Hi,
I think I discovered something with 5.4 and PlayMaker, it seems PlayMaker can't setup the Player settings properly to include some Scripting Define Symbols.
Can you double check that your Scripting Define Symbols are filled in with Playmaker entries?
Bye,
Jean
-
Hi Jean,
Attached is what I currently have in my Scripting Define Symbols.
Hope that helps :)
-
Hi,
Ok, then you are fine on that aspect.
Do you still get this issue?
Bye,
Jean