WebGL Bug with VariableSeperator

Forums 💬 NodeCanvas ⚙️ Support WebGL Bug with VariableSeperator

Viewing 5 posts - 1 through 5 (of 5 total)
  • Author
    Posts
  • #18306
    patientzerogames
    Participant

      Hi

      just wanted to let you know that there seems to be a bug when using Nodecanvas in a WebGL build.
      It is caused by the VariableSeperator and throws the following error:

      b>(Deserialization Error)</b>: Constructor of NodeCanvas.Framework.Variable1[NodeCanvas.Framework.VariableSeperator] threw an exception when creating an instance
      at ParadoxNotion.Serialization.FullSerializer.fsMetaType.CreateInstance () [0x00000] in <filename unknown>:0
      at ParadoxNotion.Serialization.FullSerializer.Internal.fsReflectedConverter.CreateInstance (ParadoxNotion.Serialization.FullSerializer.fsData data, System.Type storageType) [0x00000] in <filename unknown>:0`

      Adding a #if UNITY_WEBGL in the Variable.cs class seems to fix the error

      #18310
      Gavalakis
      Keymaster

        Hey,
        I’m very sorry for the late reply, but I was ill for the last couple of days.
        Thanks a lot for the bug report and fix!
        I will also investigate further to find the real cause of this 🙂

        #18309
        patientzerogames
        Participant

          Hey,
          No problem!

          I came across another small bug.
          If you use the Control Graph Owner Task triggered by a ConcurentState or AnyState to stop a FSM it will cause a Nullreference exception in the FSM.OnGraphUpdate() method

          #18308
          Gavalakis
          Keymaster

            Ah. Thanks for that too 🙂
            The problem is more relevant to GraphOwnerControl task. Here is a fixed version. A bit tricky 🙂

            Thanks 🙂

            #18307
            patientzerogames
            Participant

              Great!
              Thx for the quick fix!

            Viewing 5 posts - 1 through 5 (of 5 total)
            • You must be logged in to reply to this topic.