Playmaker Forum
PlayMaker Updates & Downloads => Pre-release Discussion => Topic started by: hh on March 02, 2016, 10:06:56 AM
-
Getting these errors using Unity 5.4.0 beta 7 and version 1.8.0.f41 of PlayMaker:
GetBool is not allowed to be called from a MonoBehaviour constructor, call it in Awake or Start instead. Called from script 'PlayMakerWelcomeWindow' on game object ''.
See "Script Serialization" page in the Unity Manual for further details.
UnityEditor.EditorPrefs:GetBool(String, Boolean)
HutongGames.PlayMakerEditor.PlayMakerWelcomeWindow:.cctor() (at Assets/PlayMaker/Editor/PlayMakerWelcomeWindow.cs:97)
SetLogCallbackDefined is not allowed to be called during serialization, call it from Awake or Start instead. Called from script 'FsmEditorWindow' on game object ''.
See "Script Serialization" page in the Unity Manual for further details.
UnityEngine.Application:add_logMessageReceived(LogCallback)
HutongGames.PlayMakerEditor.FsmDebugger:.ctor() (at c:/Users/Alex/Documents/Unity/Playmaker/Projects/Playmaker.source.unity/Assets/PlayMaker/Editor/Classes/FsmDebugger.cs:51)
HutongGames.PlayMakerEditor.FsmDebugger:.cctor() (at c:/Users/Alex/Documents/Unity/Playmaker/Projects/Playmaker.source.unity/Assets/PlayMaker/Editor/Classes/FsmDebugger.cs:22)
The GetBool one is easy enough to remove but not sure how to fix the SetLogCallbackDefined error.
-
Hi, these look like new restrictions in the 5.4 beta.
I'll need to update the build to fix these...
Are they blocking errors or can you continue to use Playmaker after the error?
I'll PM you about getting access to the Playmaker beta so you can test the fix asap.
-
Thanks for the quick response. We can still use PlayMaker in the editor but are unable to make builds.
-
Not in my case. I cant even run test game since it spits out exact same errors as above :/
-
@Devis I sent you a PM about joining the Playmaker beta group.
-
I'm having this issue too, anything I can do on my end to resolve it?
-
I also have the same problem with Unity 5.4 (Beta) if there is a solution available i would also be happy to get notified. Thanks
-
I'm moving over to 5.4b
Is there a package I should use for this?
I bought Playmaker from your store, not the Asset store. :)
I don't get on the forums much here, but I'll try to check this often
-
First make sure you're using the 1.8.0 beta.
There are still a few errors on import and when you press play, but they are relatively harmless. As far as I can tell they don't actually break anything, at least when playing in the editor. To make standalone builds you'll probably need to wait for the next Playmaker update. If you need it now, send me a PM with your Playmaker invoice number and a google/gmail account and I'll send you an invite to the Playmaker Beta Group.
If you want to remove a few of the errors you can delete Assets\PlayMaker\Editor\PlayMakerDefines.cs. Unity 5.4 beta removes a few platforms so they throw errors when setting up the scripting defines. Again, the rest of the platforms work, it just fails on the removed platforms.
If you are seeing other problems with Unity 5.4 please let me know! Submitting a bug report works best since it's easier to track. Thanks!
-
Hello. I just bought this wonderful program today but I too have the error messages for the 5.4 beta version of unity. Also, when I download and import from the Asset Store, it won't load into my available assets. I've done everything. I can select it as an asset option when I create a new project but then it makes me download the entire version inside the project and then prompts all those errors. I haven't been able to enjoy your work thus far and I'd really appreciate some guidance. Thank you.
-
Hello, I have the same problem ("SetLogCallbackDefined is not allowed to be called during serialization, call it from OnEnable instead. Called from ScriptableObject 'FsmEditorWindow'."), with Unity 5.4.0b17 and Playmaker 1.8.0.f43.
I deleted Assets\PlayMaker\Editor\PlayMakerDefines.cs. but the error is still there.
I can play the project in editor, but I can't make a build. Is there a solution?
Thanks.
-
Playmaker 1.8.1 should be out next week and will address 5.4 beta compatibility.
-
Thank you for your answer. Great new!
-
Still having compatability errors like the original message of this thread, and also seeing lots of warnings showing up for upcoming deprecated functions. Any word on when these will be fixed with unity 5.4.0f3 ? Currently running 1.8.2 for playmaker. I commented out the code saying GetDevice is not allowed to be called from a MonoBehaviour constructor etc. And so it works, but have lots of warnings
This is an example of the deprecated stuff:
OnLevelWasLoaded was found on PlayMakerFSM
This message has been deprecated and will be removed in a later version of Unity.
Add a delegate to SceneManager.sceneLoaded instead to get notifications after scene loading has completed
-
Hi,
You can safely ignore the deprecated warnings, this will be address int he next version of PlayMaker when this deprecated features will be covered by PlayMaker internally.
If you still have the issues of the original post, maybe the project needs cleaning up. For example, on a fresh empty project, when you import PlayMaker, do you get errors ( apart from the deprecated warnings I mean).
Bye,
Jean
-
Hey Jean,
I can confirm that the project just needed cleaning up. I had similar problems with unity 5.4. After deleting the playmaker folder and re-importing playmaker fixed the SetLogCallbackDefined is not allowed to be called during serialization, call it from OnEnable instead. Called from ScriptableObject 'FsmEditorWindow' for me.
Thanks
Rock on!
-
This is really helpful and i am thankful for posting such an informative article.
-
Hi!
I'm using Unity 5.4.0f3 and Playmaker 1.8.0.f43. I also get this error.
"SetLogCallbackDefined is not allowed to be called during serialization, call it from OnEnable instead. Called from ScriptableObject 'FsmEditorWindow'.
See "Script Serialization" page in the Unity Manual for further details."
And these warnings:
OnLevelWasLoaded was found on PlayMakerFSM
This message has been deprecated and will be removed in a later version of Unity.
Add a delegate to SceneManager.sceneLoaded instead to get notifications after scene loading has completed
OnLevelWasLoaded was found on PlayMakerUnity2d
This message has been deprecated and will be removed in a later version of Unity.
Add a delegate to SceneManager.sceneLoaded instead to get notifications after scene loading has completed
OnLevelWasLoaded was found on ES2AutoSaveManager
This message has been deprecated and will be removed in a later version of Unity.
Add a delegate to SceneManager.sceneLoaded instead to get notifications after scene loading has completed
I know these warnings are harmless. And the error doesn't affect the game in the editor or when I build it.
But is it any update for this now?
-
Yes, these should be fixed in 1.8.3. Make sure you update Playmaker in the asset store downloads manager in Unity 5.4 to get the latest version for 5.4.
-
Hi!
Thanks! I updated Unity and Playmaker to the latest version. Now I only get two of this warning:
OnLevelWasLoaded was found on PlayMakerUnity2d
This message has been deprecated and will be removed in a later version of Unity.
Add a delegate to SceneManager.sceneLoaded instead to get notifications after scene loading has completed
Is it a way to remove this warning? Or will it be removed automatically in a later version of Unity as it says in the warning msg?
-
PlayMakerUnity2d is not part of the official Playmaker installation. It's probably part of an add-on or ecosystem download. It sounds like it was probably part of the Unity2D add-on that's no longer required with Playmaker 1.8.1+
Did the Update Check find this add-on in your project? You should be able to remove the Unity2d add-on from your project (backup first!).
Otherwise Jean will have to look into this...
-
Hi,
yes, PlayMakerUnity2d script isn't necessary anymore if you have the latest version of PlayMaker.
I would suggest the following:
1: backup your project
2: get the latest version of PlayMaker
3: during installation, check the updater, it shoudl prompt you with what's not included officialy within PlayMaker. clean up your project so that the updater finds nothing potentially clashing and you'll be good.
Let me know if you struggle with this.
Bye,
Jean
-
Hi!
So you mean I can delete the PlayMakerUnity2D script which is inside the folder Playmaker Unity 2D?
See the screenshot. Should I delete the script marked in yellow?
I have the latest version of both Unity and Playmaker.
-
Hi,
yes, and you should actually be able to get rid of the whole folder "PlayMaker Unity 2D".
Back up before you do so as always.
Bye,
Jean
-
Hi Jean,
I'm currently trying to upgrade to 1.8 to correct the serialization issue. Do I need to be on the beta list to receive it? I looked for an install folder in Playmaker>Editor as suggested in another post and I don't see it.
---------------
EDIT - The asset store showed Playmaker 1.8.3 available today from my laptop but 1.7.x on my iMac yesterday. The strange thing is that my iMac has a newer version of Unity (The latest 5.5). Very strange. I did find the install folder and installed from there and all is well with Playmaker. Now on to the Vuforia problems.
-
So I've looked at this again. I have a machine with updated OS and latest Unity which will not update Playmaker in the Download manager of the Asset store past 1.7.8.3. Even when I go direct to Playmaker's asset store page and download into a new project I get the redundant resource errors. Is this a Unity 5.5 issue?
-
Hi,
I don't experience this locally, so it's tricky to give you an exact procedure currently
but it's likely solved by cleaning up PlayMaker install totally, Make sure you back up first, and/or move the global resources and templates out of the PlayMaker folder first.
Bye,
Jean