Dataclay — Automating Digital Production
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Register
    • Login

    Spatial/temporal changes in chained layers bug?

    Scheduled Pinned Locked Moved
    Templates
    2
    2
    117
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • jbenton42undefined
      jbenton42
      last edited by

      Weird behavior I’m seeing-- with 3 text layers chained together, if I change any setting in “Templater Settings”, like Scale Factor, or alignment, etc, when I hit the Spatial/Temporal preview button or Data Merge a single time, only one of the text layers moves into the updated layout. The other 2 layers move into the wrong place. If I hit the Spatial/Temporal preview button or Data Merge a second time, then everything moves properly into place. With it’s current behavior, I’m not sure how I could run an automated process, because it requires doubling the preview or data merge operation to get everything to fall into place.

      Jeffundefined 1 Reply Last reply Reply Quote 0
      • Jeffundefined
        Jeff @jbenton42
        last edited by

        @jbenton42

        Hello, hope you’re doing well. We’ve seen the sort of behavior you’re describing here before, and it generally comes from a logic problem with the setup of the Time Sculpting layers. It’s a bit difficult to explain, but usually, the issue comes from a layer that’s dependent on the logic of another layer that, in turn, doesn’t adjust properly.

        To resolve this, the first thing that I would recommend would be to ensure that the system in question is running the latest version of Templater. We’ve made some recent adjustments to the Time Sculpting logic in the latest version of the plugin to specifically address the type of issues that are being described here.

        If installing the latest version doesn’t make a difference, there are some additional troubleshooting techniques that we could recommend, but they tend to be a bit tedious, so if we can solve the issue with the updated Time Sculpting logic, that would be ideal.

        Let’s start there and if the issue persists, we can consider what other troubleshooting steps we might take to get this issue resolved.

        Thanks,

        Jeff

        1 Reply Last reply Reply Quote 0
        • First post
          Last post