I'm experiencing major "Jank" in Construct r130, the latest release. Anyone else experiencing this?

  • So, not sure if you can see this, but I just recorded a sample of its performance on my screen. (This is after tweaking it as much as I could to get it to run smoothly, to no avail...)

    Pay attention to how jerky the movement of the lines that scroll down the screen look. It's practically unplayable like this, and definitely not enjoyable like this...

    I tried my hardest to get it to run smoothly, but it looks like something is wrong with Construct because it is herky, jerky like I have never seen any other app before.

    Especially towards the middle of the video it gets Very very jerky...

    Also, what in the world is that black bar on the bottom of the screen for? That is so annoying. Sometimes it's there and sometimes it's not (when I switch away from the app and come back, sometimes it disappears and sometimes it doesn't.) Why are there so many problems and issues with mobile export???

    Video of stutter on Android 6.0.1 mobile Debug APK (new Construct 3 runtime):

    photos.app.goo.gl/bP3wjCG7fuG3zKy57

  • Here's another one using a different screen recorder = it's SOOooo Jerky!!!!!!

    photos.app.goo.gl/yP8Yv3kVc358EwMB8

  • Thank you for helping me test this EVERYONE, you guys are the best....

  • Here's another one using a different screen recorder = it's SOOooo Jerky!!!!!!

    https://photos.app.goo.gl/yP8Yv3kVc358EwMB8

    Yep, this is pretty much what i'm getting, on my laptop, really unplayable.

    If I was a customer and downloaded this game on my laptop, I would be disappointed and delete it promptly.

    It's a shame really, seeing as we rely on chrome so much, this has been going on for years now, some versions of chrome are better than others, but c3 scrolling is a problem on certain chrome dependant devices, that's a fact.

    I asked for a chromebook test, because I believe this is a growing market, and most new chromebooks play android apps, and have touch screens, so the potential casual chromebook market is going to grow, even Microsoft has an office app for chromebooks now, So it's important that apps that scroll like endless runner's work to a minimum jank free standard.

  • Agreed 150%

  • Jank can be caused by background network activity,

    I think the web worker thing was supposed to solve this by having the game on a separate thread

    but (dont quote me on this as I'm not as up to date on construct news I used to be)

    but the last I read on one of Ashley's updates was that the worker thing was deactivated for now pending a future update of chrome . that was a couple of months back I think so not sure if there has been an update since then.

  • Jank can be caused by background network activity,

    I think the web worker thing was supposed to solve this by having the game on a separate thread

    but (dont quote me on this as I'm not as up to date on construct news I used to be)

    but the last I read on one of Ashley's updates was that the worker thing was deactivated for now pending a future update of chrome . that was a couple of months back I think so not sure if there has been an update since then.

    You can enable web worker in the settings, with enable experimental features checked, this is in the latest stable r131.

    There is no less visible scrolling jank difference, with my laptop, with this enabled.

    I am not knocking c3, in fact I think it's great, and will re-subscribe, but we are limited to chrome, or chrome variants, so it does matter, it affects what we produce, for our target markets, most issues are normally fixed by advances in technology, but this one seems to be hanging around.

  • Try Construct 3

    Develop games in your browser. Powerful, performant & highly capable.

    Try Now Construct 3 users don't see these ads
  • Did some test, this test does not show why some device janks or lag, while project has good peformance, but overall look when fps can change something different then 60, under load.

    So when dt jumps between 0.01666 and 0.03333 very fast it will cause this super bad lag, when sprite jumps back and forth.

    Use example and pressure fps to around 50.

    Example: snipg.github.io/Tests/JankyCranky

    You can pressure CPU or GPU there. Or stop logic to see some last steps distances.

    Line 2 ball uses just self.x -3 while others use bullet behavior, which have dt i think.

    Anyway, if you don't like janks or some sprite lag, don't use dt in sprite logic that is moved with small increments each tick, or least don't use bullet behavior.

  • No jank on any of these examples, no matter how many objects I add.

    5 year old laptop ( but was the top of the line back then, so still pretty badass )

    Running win 8.1 / Chrome Version 70.0.3538.110 (Official Build) (64-bit)

    OK, I got it to drop below 60 FPS after adding some really unrealistic amount of objects, but it's more of a slowdown than jankiness even then.

  • The original test was on mobile with an Android Debug APK, but I guess the "Jankiness" is affecting all/many devices?? Guess the problem is much more widespread than I thought. I just want a smooth gaming experience for my consumers, that should be the base level of what we get from a gaming engine. Without that you don't have a game. People's suggestions are shocking: just make a game with no "scrolling?" Seriously? Don't use delta time? How in the world can you regulate speed then? Don't use bullet behavior? Bullet behavior is the foundational basis for many games! How can this even be considered a game engine? More like an experimental project with no basis in reality!!!! I like programming in construct, but trying to make a finished product with it is torturous (has been since day one). It never comes out as a very high quality product. Why can't it just work?? Apple had that motto for many years, "it just works". Out of the box, it just works. Construct's motto is: "It never works". No matter how hard you try, it will never do just what you need/want it to do... Please help!! Calling all programmers!!! We need help!!!!!! I just want this thing to work!! I wish it just exported to native code like many other engines do instead of relying wholly on a constantly changing framework (the chrome browser) to build apps on top of. What a terribly faulty/risky business model! What a terribly risky foundation!!!! How could anyone trust this engine??? It is not a serious game making tool, and right now, it is not even a serious prototyping tool. The "jank" renders the engine useless for me. For my purposes, it is broken, and it has been for quite some time... I too was called and invited by a Nintendo employee to produce games for the Wii U back in the day. My excitement was hard to contain. But Construct 2 was not suitable to produce games for that platform at that time, HTML5 was too slow on it. Or any platform in my experience. Apps were slow and buggy, PC games were slow and awkward. Everything I have produced with Construct with few exceptions has been a nightmare. I wish I had started on a different engine instead of pouring years into learning this one only to have my dreams dashed to pieces by its flaws and shortcomings...What a tragedy...

    Construct continues to be a disappointment, never fulfilling what it promises to do....

  • I don't mean to be a downer. Just expressing my true feelings here, thank you for the continued testing and hints about how to actually make a game run smoothly with Contruct 3, r131. You guys are great :) :) :)

  • I just want it to work so badly, why can't it "just work???".........

  • I just want it to work so badly, why can't it "just work???".........

    Ye thats what iam talking about, dam we are limited with 60 fps in 2018, should be 600 at least. Multi-trillion companys and we can't use bullet behavior with 500 speed, what a crazy world.

    And then you watch TV and what you see, 30fps. So they fake it by not moving camera fast, instead holding it on same spot and zoom in and out. Same thing in youtube.

    And now we have to wait like at least 50 year to get smoother picture quality, were is justice! I don't have 50 year. So we have to take it on streets, all deviced at least 600 fps, same for videos for basic human eye right.

  • STARTECHSTUDIOS

    Could you try this version? I replaced the bullet behavior and the drag and drop plugin with normal events. I'm curious if this really has an impact.

    drive.google.com/uc

  • Well, I have a game that scrolls a tiled background, each tile/strip is something like 2000 x 150, Some particles here and there and fairly detailed animations in my sprites. It all runs perfectly smoothly on my laptop and on my 3 year old Galaxy phone. Same on iPhones 7 and up. So, I would say it works.

    Only saw problems on 7-8 year old laptops or really crappy newer ones. Even there it is playable, but there is tearing.

    Now this is only HTML 5 export played on phones and laptops. I'm not sure why I even need APK or that other iPhone shit, when this works the same or better. ( yeah, I know, maybe some extra admob money if I get lucky and people find me on one of those shitty app stores ).

    And by the way, that "It just works" by Apple is 110% bullshit. Never worked. Now all PCs work much better, but early 2000s , not a single Mac user that I knew, that did not have serious problems, from freezes 10 times a day, dead RAM modules on arrival, faulty screens, and so on.

Jump to:
Active Users
There are 1 visitors browsing this topic (0 users and 1 guests)