Playmaker Forum

PlayMaker Help & Tips => PlayMaker Help => Topic started by: zhing on May 11, 2012, 11:19:07 PM

Title: FsmObject cause NotSupportedException
Post by: zhing on May 11, 2012, 11:19:07 PM
I try to use FsmObject variable to store NGUI's UIAtlas object.
And use my custom action script to get/set it.

When I run my game and select the game object which has FSM.
NotSupportedException cause again and again.

The log as below:
NotSupportedException: The invoked member is not supported in a dynamic module.
System.Reflection.Emit.AssemblyBuilder.GetExportedTypes ()
HutongGames.PlayMaker.FsmUtility.GetType (System.String typeName)
HutongGames.PlayMakerEditor.FsmVariable..ctor (UnityEngine.Object owner, HutongGames.PlayMaker.FsmObject fsmObject)
HutongGames.PlayMakerEditor.FsmVariable.GetFsmVariableList (HutongGames.PlayMaker.FsmVariables variables, UnityEngine.Object owner)
FsmComponentInspector.BuildFsmVariableList () (at Assets/PlayMaker/Editor/FsmComponentInspector.cs:311)
FsmComponentInspector.OnInspectorGUI () (at Assets/PlayMaker/Editor/FsmComponentInspector.cs:157)
UnityEditor.InspectorWindow.DrawEditors (Boolean isRepaintEvent, UnityEditor.Editor[] editors, Boolean eyeDropperDirty) (at C:/BuildAgent/work/b0bcff80449a48aa/Editor/Mono/Inspector/InspectorWindow.cs:888)
UnityEditor.InspectorWindow.OnGUI () (at C:/BuildAgent/work/b0bcff80449a48aa/Editor/Mono/Inspector/InspectorWindow.cs:243)
System.Reflection.MonoMethod.Invoke (System.Object obj, BindingFlags invokeAttr, System.Reflection.Binder binder, System.Object[] parameters, System.Globalization.CultureInfo culture)

But if I didn't select the game object in the hierarchy, the FSM run was running well and no exception.
My PlayMaker is 1.3.3.
Title: Re: FsmObject cause NotSupportedException
Post by: Alex Chouls on May 12, 2012, 01:54:59 PM
Thanks! This is fixed in the next release.
Title: Re: FsmObject cause NotSupportedException
Post by: zhing on May 12, 2012, 11:32:12 PM
Could I have any way to get beta version which fixed this problem? :)
There error logs were printed time and time again. So I really can't debug the state machine. :(