hyperPad hyperPad Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Login

    Frame Rate Slow Down...

    Scheduled Pinned Locked Moved
    Bug Reports
    4
    24
    874
    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.
    • Aidan_FireA
      Aidan_Fire @Deeeds
      last edited by Aidan_Fire

      @Deeeds Wrong solution for the wrong problem. You’re getting laggy editor as well as laggy game. Deselecting graphic is a fix for just a particle constantly lagging for no reason. That’s why I was asking for a link, so I could see what you mean for myself.

      D 1 Reply Last reply Reply Quote 0
      • D
        Deeeds @Aidan_Fire
        last edited by

        @Aidan-Oxley FFS.

        They are TWO DIFFERENT problems.

        I'm only pointing out the laggy editor to show there are OTHER leaks.

        Aidan_FireA 1 Reply Last reply Reply Quote -1
        • Jack8680J
          Jack8680 @Deeeds
          last edited by

          @Deeeds said in Frame Rate Slow Down...:

          Soon after this, all hell broke loose and your engine became so laggy that it was incredible. Not just in play testing, but also in editing behaviours and scenes. I was frantically deleting scenes, particle systems and all sorts of objects and behaviours, mistakenly thinking it must be something I did.

          By the time I got to a scene with nothing more than the hero, ground and camera controller, and it was still stuttering away, I realised the problem wasn't me.

          I don't think I've ever had lag continue into the editor like that. By stuttering away, do you mean constantly lagging or random lag spikes?

          It seems unlikely to me it's a memory leak because I'd expect the app to crash eventually from running out of memory, unless there's some kind of garbage collector that's causing the lag.

          It also sounds very weird that you'd have to quit the app twice to fix it; I wouldn't expect memory to persist into the next launch.

          I've heard about ios11 running badly, could it be a related bug causing a memory leak?

          1 Reply Last reply Reply Quote 0
          • Aidan_FireA
            Aidan_Fire @Deeeds
            last edited by Aidan_Fire

            @Deeeds I got the wrong idea. I haven’t had this problem, which was why I was asking for a link so that I could try to replicate it.

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