Can't delete tracks from any cutscenes under 2018.3

Forums 💬 Slate Sequencer ⚙️ Support Can't delete tracks from any cutscenes under 2018.3

  • This topic has 0 replies, 4 voices, and was last updated 7 years ago by Gavalakis.
Viewing 6 posts - 1 through 6 (of 6 total)
  • Author
    Posts
  • #20401
    dgoyette
    Participant

      This is easy to reproduce: Tools -> Paradox Notion -> SLATE -> Create new Cutscene. Now try to delete any of the tracks, and I get this error:

      “This track is part of the prefab asset and can not be deleted from within the prefab instance. If you want to delete the track, please open the prefab asset for editing.”

      I’m not editing a prefab, it’s just a cutscene that exists in a Unity scene. And this applies to all tracks, not just the pre-populated tracks. It seems I can’t delete tracks under 2018.3.

      #20406
      Gavalakis
      Keymaster

        Hello!

        This bug has already been fixed and is part of the new version that is sent to the asset store a few days ago. The new version is though still pending review, but it should go live in any day now, maybe even today :).

        Thanks!

        #20405
        b4th
        Participant

          This is still happening in Slate V 1.9.1

          🙁

          EDIT: Oops, it looks like the logic might be inverted:

          If I’m not mistaken, this function (which sounds like it’s trying to determine if an object is SAFE to delete) is actually finding out whether the game object is part of a prefab, and therefore is UNSAFE to delete. Therefore, the function should be changed to something like IsUnsafePrefabDelete, and the logic where it gets called should be flipped?

          EDIT 2: The above change seems to fix the issue.

          #20404
          spinalcord
          Participant

            hey Breaking Fourth thanks, this seems to work. I would also change the line with

            #if UNITY_2018_3_OR_NEWER

            to

            #if UNITY_2018_3_OR_NEWER && UNITY_EDITOR

            to prevent build errors.

            #20403
            b4th
            Participant

              Hey @Gavalakis, think you could double-check this?

              #20402
              Gavalakis
              Keymaster

                Hey,
                Sorry for the late reply!
                Yes, using #if UNITY_2018_3_OR_NEWER && UNITY_EDITOR is correct.

                Thank you.

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