• Products
    • Isadora
    • Get It
    • ADD-ONS
    • IzzyCast
    • Get It
  • Forum
  • Help
  • Werkstatt
  • Newsletter
  • Impressum
  • Dsgvo
  • Press
  • Isadora
  • Get It
  • ADD-ONS
  • IzzyCast
  • Get It
  • Press
  • Dsgvo
  • Impressum

Navigation

    • Register
    • Login
    • Search
    • Categories
    • Recent
    • Popular
    • Tags

    [SOLVED] Limit-Scale Value Bug or misunderstanding?

    Troubleshooting and Bug Reports
    3
    5
    1554
    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.
    • R
      Reinhard last edited by

      Hi,

      I want to change the 'out max' value of a Limit-Scale Value Actor within a scene (from 100 to 50 in the example file), but when returning to the scene, start with 100 again, so I set the initialize of 'out max' to 100\. As I trigger 50 everything works as expected. When I leave the scene and return I can see the 'out max' has returned to 100 but the output stops at 50\. This behavior remains (even if you close the file and reopen) until you manually change the 'out max' setting. Any explanation highly welcome.
      best
      r

      061183-limit_scale_test.izz

      mbp 16", 2021, m1pro, 16gb, 12.6 / 6core trashcan, 11.2 / youngest Izzy

      1 Reply Last reply Reply Quote 0
      • Michel
        Michel Izzy Guru last edited by

        @Reinhard

        I can recreate this and it seems to be a bug. Can you file a formal bug report? To get around this you have to de-select the initialize value and ad another trigger value of 100 with a enter scene trigger connected to it.

        Best Michel
        a963a9-limit-scale.png

        Michel Weber | www.filmprojekt.ch | rMBP (2019) i9, 16gig, AMD 5500M 8 GB, OS X 10.15 | located in Winterthur Switzerland.

        1 Reply Last reply Reply Quote 0
        • R
          Reinhard last edited by

          @Michel

          Bug report filed. Your workaround does not work - it has to be something else than 100 - 99,99 works.
          best r

          mbp 16", 2021, m1pro, 16gb, 12.6 / 6core trashcan, 11.2 / youngest Izzy

          1 Reply Last reply Reply Quote 0
          • Michel
            Michel Izzy Guru last edited by

            @Reinhard

            It did work for me, but it only works with 100 if you untick the initialize value that already initializes 100.

            Best Michel

            Michel Weber | www.filmprojekt.ch | rMBP (2019) i9, 16gig, AMD 5500M 8 GB, OS X 10.15 | located in Winterthur Switzerland.

            1 Reply Last reply Reply Quote 0
            • mark
              mark last edited by

              Dear @Reinhard,

              Thanks for your patience in awaiting my reply to this, but I wanted to let you know this bug is solved. It was really the result of a bad design decision on my part, to automatically set the 'Limit Min' and 'Limit Max' of the output port based on the 'out min' and 'out max' inputs. (This has been part of the Limit Scale Value actor since I first made it.) I've removed this "feature" and I think the updated version of the plugin will work as you expect.
              Best Wishes,
              Mark

              Media Artist & Creator of Isadora
              Macintosh SE-30, 32 Mb RAM, MacOS 7.6, Dual Floppy Drives

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