Ashley's Recent Forum Activity

  • The spikes might be the same causes of jank as in the sbperftest demo which is already in a Chrome bug report. I think it would be best to see what they can do to improve that demo and see how that impacts other games.

    Tests like sbperftest are essential for bug reports, because it makes objective measurements and is 100% repeatable. That's difficult to get with a full blown interactive game.

  • You should read the multiplayer tutorials so you don't run in to problems they cover.

    [quote:294wvouc]It's also possible someone will already be hosting the tutorial but you won't be able to connect to them. If that happens, change either the game, instance or room name and you'll start a new game which you host yourself.

  • You generally only have to wait 1-2 weeks to find out what's in the next release

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • It looks like you've filled the images right to the edges. Hit 'crop' in the image editor and it adds a 1px transparent border around the edge. That allows for soft-edged blending along the image edges. Note that is not antialiasing, it's just linear sampling along the edge, but it looks similar and is far faster than an expensive fullscreen antialiasing effect.

  • The golden rule: if you can measure a performance improvement, it's worth it; if not, you're wasting your time.

    I doubt you will be able to measure any performance improvement from disabling when there are no instances, because in that case there are no instances to run conditions/actions/loops on, so there's still nothing to do.

  • Actually while Chrome 38 gives me a terrible dt variation (typically 8 - 45ms), Chrome Canary seems a lot better, ranging only 21-24ms. It also subjectively looks better - it's not perfectly smooth in Canary (obviously, since at 45 FPS there's no choice but to skip some frames), but it doesn't have the eye-straining extreme juddering which Chrome 38 has with its wide dt variation. So it may be that it's already been fixed and we only need to wait for Canary to come through (currenty v40).

    Can anyone with affected games give them a spin in Canary and say if it seems any better? You can install it side-by-side with normal Chrome: https://www.google.co.uk/intl/en/chrome/browser/canary.html

    Canary might have also improved the input latency so you can test that with it too.

    BTW in the test I posted earlier the rectangle count is completely irrelevant, it's only aimed at measuring the dt variation.

  • blackhornet - you should report the min/max dt at 45 FPS, is that what your data is?

  • But what measurements made you identify this event even when it ran every tick? Are you sure you are not wasting your time chasing the wrong thing?

  • It's a bit like the stable/beta separation in C2: the betas eventually become stable, but you can try them early to test the latest features but possibly risking new issues. I think the way Crosswalk works the next version is based on the next version of Chromium too.

  • What measurements have you made that identify this event as the cause?

  • Crosswalk is just a custom build of Chromium, so I don't think there's any point reporting it to them as well, just wait for it to get fixed in Chromium.

    A monitor running at 59 Hz will probably not help! A lot of games and possibly browsers are tuned to work at 60 Hz since it's the most common refresh rate, and being slightly off that could make you drop frames...

  • I don't think it's a C2 bug, there's nothing much we could change on our end. It's a question of getting a minimal repro to pass over to browser vendors.

    I tried a bit harder and came up with a new GPU-based repro, and I can get it to vary severely by drawing much larger rectangles on a mid-range laptop:

    http://www.scirra.com/labs/bugs/fpstest-gputhrottle.html

    (If you've viewed it before press refresh to get the latest test - should draw ~1000x1000 rectangles and aim for 45 FPS)

    I can get severe dt variations from 8ms to 44ms in Chrome. That's pretty extreme and the juddering is visible on the moving black box.

    I guess we just need to figure out if this is widely reproducible (i.e. is it a good demo to show to browser vendors?) and then if so use it to file a bug report with affected browsers. So, does it reproduce it for everyone else?

    BTW I tried that test in IE11 and the dt variation is sometimes much smaller (22-24ms) but it still looks pretty bad on the motion. Are actual games any better or worse in IE11? (I think a bug report with a title like "Chrome does X worse than IE11" should get their attention - it's worked before )

Ashley's avatar

Ashley

Online Now
Early Adopter

Member since 21 May, 2007
Last online 27 Oct, 2026

Twitter
Ashley has 1,835,272 followers

Connect with Ashley

Trophy Case

  • Jupiter Mission Supports Gordon's mission to Jupiter
  • Forum Contributor Made 100 posts in the forums
  • Forum Patron Made 500 posts in the forums
  • Forum Hero Made 1,000 posts in the forums
  • Forum Wizard Made 5,000 posts in the forums
  • Forum Unicorn Made 10,000 posts in the forums
  • Forum Mega Brain Made 20,000 posts in the forums
  • x126
    Coach One of your tutorials has over 1,000 readers
  • x74
    Educator One of your tutorials has over 10,000 readers
  • x6
    Teacher One of your tutorials has over 100,000 readers
  • Sensei One of your tutorials has over 1,000,000 readers
  • Regular Visitor Visited Construct.net 7 days in a row
  • Steady Visitor Visited Construct.net 30 days in a row
  • RTFM Read the fabulous manual
  • x44
    Great Comment One of your comments gets 3 upvotes
  • Email Verified

Progress

32/44
How to earn trophies

Blogs