playMaker

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - hh

Pages: [1]
1
Pre-release Discussion / Re: Unity 5.4 beta PlayMaker errors
« on: March 02, 2016, 09:19:30 AM »
Thanks for the quick response. We can still use PlayMaker in the editor but are unable to make builds.

2
Pre-release Discussion / Unity 5.4 beta PlayMaker errors[SOLVED]
« on: March 02, 2016, 08: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.

3
Pre-release Discussion / Re: Any forseeable issues with Unity 5.4?
« on: March 02, 2016, 07:51:00 AM »
I've been unable to make a (x86_64) build using the most recent beta version of Unity 5.4 due to these errors:

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)

4
Feature Requests / Re: Raycast option to ignore triggers
« on: February 09, 2016, 11:35:52 AM »
Thank you.

5
Feature Requests / Raycast option to ignore triggers
« on: February 08, 2016, 10:20:05 AM »
It would be useful for the Raycast action to optionally ignore trigger colliders in the scene.

The ideal functionality would mirror Unity's QueryTriggerInteraction enum:
http://docs.unity3d.com/ScriptReference/QueryTriggerInteraction.html

Pages: [1]