playMaker

Author Topic: Copyoutputvariables error on build (1.9.1)  (Read 554 times)

dmak20

  • Playmaker Newbie
  • *
  • Posts: 1
Copyoutputvariables error on build (1.9.1)
« on: March 23, 2021, 10:07:00 AM »
Does anyone know how to solve the following issue:

NullReferenceException: Object reference not set to an instance of an object
HutongGames.PlayMaker.FsmTemplateControl.CopyOutputVariables (HutongGames.PlayMaker.FsmTemplateControl source) (at C:/Projects/Playmaker_1.9.1/Projects/Playmaker.source.unity/Assets/PlayMaker/Classes/CustomActionTypes/FsmTemplateControl.cs:276)
HutongGames.PlayMaker.FsmTemplateControl..ctor (HutongGames.PlayMaker.FsmTemplateControl source) (at C:/Projects/Playmaker_1.9.1/Projects/Playmaker.source.unity/Assets/PlayMaker/Classes/CustomActionTypes/FsmTemplateControl.cs:193)
HutongGames.PlayMaker.ActionData.CopyFsmTemplateControlParams () (at C:/Projects/Playmaker_1.9.1/Projects/Playmaker.source.unity/Assets/PlayMaker/Classes/ActionData.cs:500)
HutongGames.PlayMaker.ActionData.Copy () (at C:/Projects/Playmaker_1.9.1/Projects/Playmaker.source.unity/Assets/PlayMaker/Classes/ActionData.cs:179)
HutongGames.PlayMaker.FsmState..ctor (HutongGames.PlayMaker.FsmState source) (at C:/Projects/Playmaker_1.9.1/Projects/Playmaker.source.unity/Assets/PlayMaker/Classes/FsmState.cs:129)
HutongGames.PlayMaker.Fsm..ctor (HutongGames.PlayMaker.Fsm source, HutongGames.PlayMaker.FsmVariables overrideVariables) (at C:/Projects/Playmaker_1.9.1/Projects/Playmaker.source.unity/Assets/PlayMaker/Classes/Fsm.cs:1603)
PlayMakerFSM.InitTemplate () (at C:/Projects/Playmaker_1.9.1/Projects/Playmaker.source.unity/Assets/PlayMaker/PlayMakerFSM.cs:286)
PlayMakerFSM.Preprocess () (at C:/Projects/Playmaker_1.9.1/Projects/Playmaker.source.unity/Assets/PlayMaker/PlayMakerFSM.cs:236)
HutongGames.PlayMakerEditor.PlayMakerBuildCallbacks.OnPostProcessScene () (at Assets/PlayMaker/Editor/PlayMakerBuildCallbacks.cs:70)
System.Reflection.MonoMethod.Invoke (System.Object obj, System.Reflection.BindingFlags invokeAttr, System.Reflection.Binder binder, System.Object[] parameters, System.Globalization.CultureInfo culture) (at <d7ac571ca2d04b2f981d0d886fa067cf>:0)
Rethrow as TargetInvocationException: Exception has been thrown by the target of an invocation.
System.Reflection.MonoMethod.Invoke (System.Object obj, System.Reflection.BindingFlags invokeAttr, System.Reflection.Binder binder, System.Object[] parameters, System.Globalization.CultureInfo culture) (at <d7ac571ca2d04b2f981d0d886fa067cf>:0)
System.Reflection.MethodBase.Invoke (System.Object obj, System.Object[] parameters) (at <d7ac571ca2d04b2f981d0d886fa067cf>:0)
UnityEditor.Build.BuildPipelineInterfaces+AttributeCallbackWrapper.OnProcessScene (UnityEngine.SceneManagement.Scene scene, UnityEditor.Build.Reporting.BuildReport report) (at /Users/builduser/buildslave/unity/build/Editor/Mono/BuildPipeline/BuildPipelineInterfaces.cs:163)
UnityEditor.Build.BuildPipelineInterfaces+<OnSceneProcess>c__AnonStorey1.<>m__1 (UnityEditor.Build.IProcessSceneWithReport spp) (at /Users/builduser/buildslave/unity/build/Editor/Mono/BuildPipeline/BuildPipelineInterfaces.cs:387)
UnityEditor.Build.BuildPipelineInterfaces.InvokeCallbackInterfacesPair[T1,T2] (System.Collections.Generic.List`1[T] oneInterfaces, System.Action`1[T] invocationOne, System.Collections.Generic.List`1[T] twoInterfaces, System.Action`1[T] invocationTwo, System.Boolean exitOnFailure) (at /Users/builduser/buildslave/unity/build/Editor/Mono/BuildPipeline/BuildPipelineInterfaces.cs:356)
UnityEngine.GUIUtility:ProcessEvent(Int32, IntPtr)

I'm working in Unity 2018.3.14f1 with Playmaker 1.9.1 (the latest version I could get off the asset store). This error wasn't happening in the previous version of playmaker but playmaker was spamming the console with errors and I was unable to edit FSM's.

Thanks in advanced for any help!

Dan

Alex Chouls

  • Administrator
  • Hero Member
  • *****
  • Posts: 4000
  • Official Playmaker Support
    • LinkedIn
Re: Copyoutputvariables error on build (1.9.1)
« Reply #1 on: March 23, 2021, 10:17:42 AM »
This is fixed in the next update currently in beta. I sent you an invite to the beta group.

The workaround in the current version is to resave the template with 1.9.1.