• 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

    Sometimes Unable to Enter Complex Scenes

    Troubleshooting and Bug Reports
    3
    3
    1441
    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.
    • Woland
      Woland Tech Staff last edited by Woland

      Hello all,

      I'm experiencing a bug where if I have a lot happening in a Scene, (I think it has to do with being very User Actor heavy specifically), I cannot enter that Scene. (I'm running Isadora Beta 2.5.2b09 on the Mac Pro in my signature.)

      • If I go to the Scene before or after it and try to use a Jump or Jump++ actor, it will not go into the Scene.
      • If I go to the Scene before it and press "Spacebar" it will not go into the Scene.
      • If I click on the Scene in the Scene List at the bottom of the screen it will not go into the Scene.

      The only way I can access the Scenes for which I'm experiencing this bug is to click on them in the Scene List and then duplicate the bugged Scene, which, while it doesn't technically allow me to get into the bugged Scene, does place me in a duplicate of it. What I've been doing from here is deleting as many superfluous actors and User Actors as possible in the duplicate Scene and then testing whether or not I can leave and re-enter the duplicate Scene. If I can, I delete the original, bugged Scene. If I can't, I rinse and repeat the duplication process. 

      Has anybody else run into this?

      Best Wishes,

      Woland

      TroikaTronix Technical Support
      New Support Ticket: https://support.troikatronix.com/support/tickets/new
      Support Policy: https://support.troikatronix.com/support/solutions/articles/13000064762
      Add-Ons: https://troikatronix.com/add-ons/ & https://troikatronix.com/add-ons/?u=woland
      Professional Services: https://support.troikatronix.com/support/solutions/articles/13000109444

      | Isadora Version: all of them | Mac Pro (Late 2013), macOS 10.14.6, 3.5GHz 6-core, 1TB SSD, 64GB RAM, Dual AMD FirePro D700s |

      1 Reply Last reply Reply Quote 0
      • DusX
        DusX Tech Staff last edited by

        Your current approach is likey best.

        My guess would be that there is some initialization issue. Maybe a feedback loop, although isadora is setup to catch these and give warnings.. it maybe something outside the reach of the usual exception catching.

        I don't think is and matter of size. I have some massive projects.. my vj tool built in 1.3 is many mbs (1 scene) and still opens and runs in 2.x ( it doesnt load instantly 😉)

        You can open a support ticket.. and share your file, one of the support staff can try to open the file. . Perhaps it's a system/hardware side effect. 

        Troikatronix Technical Support

        • New Support Ticket Link: https://support.troikatronix.com/support/tickets/new
        • My Add-ons: https://troikatronix.com/add-ons/?u=dusx
        • Profession Services: https://support.troikatronix.com/support/solutions/articles/13000109444-professional-services

        Running: Win 11 64bit, i7, M.2 PCIe SSD's, 32gb DDR4, nVidia GTX 4070 | located in Ontario Canada.

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

          sounds a bit like the activity I was getting in elcapitan and movie playback, it would just become unresponsive, I could click on a scene, but the scene contents would not change, no response at all. I was developing on Sierra, and playing on Elcapitan, eventually upgraded the Elcapitan machine to Sierra and went for the new beta.

          Want to send a patch and see if it behaves?

          http://www.fredrodrigues.net/
          https://github.com/fred-dev
          OSX 13.6.4 (22G513) MBP 2019 16" 2.3 GHz 8-Core i9, Radeon Pro 5500M 8 GB, 32g RAM
          Windows 10 7700K, GTX 1080ti, 32g RAM, 2tb raided SSD

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