sqiddster's Forum Posts

    Whoa, nice! I'll definitely give that a try.

  • The bug with my game would cause keys to get read as pressed when the mouse was used in the same tick as the keyboard. It was fixed but by then I'd moved on to other things.

    To be honest I'm not sure this is the issue my game has. If it is, it's been magnified greatly. Honestly all the demos I've seen have the issue, but it's not too noticeable. In my game, it's game-breaking. Could be the same issue, but it might be something different, and it's very hard to tell if there's any way of knowing. I'm pretty sure my issue is GPU-related and it could have something to do with the dt inconsistencies in this thread.

  • — there's a common misconception that not making a profit means you don't have to worry about copyright violation, that's simply not true.

    I definitely have heard of Nintendo being OK with fan-games, however all it takes is them deciding they don't want your game out there and there's nothing you can do.

    How do you know that the C&D reports are fake? This isn't nintendo, but I remember one major story where a fairly large scale mlp smash game was cancelled due to a C&D.

    Tetriser I played Brawl very casually with friends, I typically played Kirby

  • Has anyone noticed that this has gotten worse over time? I don't remember this being an issue like a year ago - but maybe that's because I wasn't looking for it.

    I'm not looking forward to waiting on Chrome to fix the issue. My last game died because Chrome took too long to fix something...

  • I have played Smash Bros, not this game though.

    'Fan Games' like this are always problematic. It's against the law to use other's copyrighted characters in your work and you can guarantee that if the game gets popular enough, you'll get a C&D from Nintendo.

    In my opinion making a game like this is a total waste when you could be coming up with your own characters and ideas.

  • The question now, is finding a repro for the jerkiness and spikes, which also seem to occur during GPU lag only.

  • Yep.

  • ArcadEd I just tried the game in Firefox, and while Firefox can't run the game nearly as well as Chrome can (at a comparable resolution) it feels perfectly smooth all the way down at 40fps - whereas Chrome feels pretty bad at anything sub-60fps.

  • Canary showed a definite improvement, both ingame and in the throttle test.

    There are still some severe issues though - I get a lot of spikes and jerkiness even at relatively high FPS's, and the input lag definitely isn't solved.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • Hmm, interesting results from Colludium - Did you every try it out on Chrome 38?

    Something else I'm a little worried about is that this test doesn't account for the significant input delay that I also experience when this GPU lag is happening. Ashley, could you ever reproduce that?

  • Chrome: 7 - 50ms

    Firefox: 20 - 25ms

    IE: 15-30ms

    This is at around 50 rects on all browsers (60-70 for IE actually) I didn't check if any of the browsers are using the GPU (I'm on a dual GPU machine) but I don't think they are.

  • Yeah, C2 definitely is supposed to do a lot of recycling like this under the hood, I'm surprised the performance difference is so big.

  • Here's a log to verify that claim:

    dt: 0.017 | FPS: 56
dt: 0.03299 | FPS: 56
dt: 0.00999 | FPS: 56
dt: 0.016 | FPS: 56
dt: 0.016 | FPS: 56
dt: 0.019 | FPS: 56
dt: 0.024 | FPS: 56
dt: 0.01399 | FPS: 56
dt: 0.01799 | FPS: 56
dt: 0.01799 | FPS: 56
dt: 0.03399 | FPS: 56
dt: 0.017 | FPS: 56
dt: 0.016 | FPS: 56
dt: 0.03299 | FPS: 56
dt: 0.01499 | FPS: 56
dt: 0.01799 | FPS: 56
dt: 0.01799 | FPS: 56
dt: 0.016 | FPS: 56
dt: 0.01499 | FPS: 56
dt: 0.018 | FPS: 56
dt: 0.03299 | FPS: 56
dt: 0.016 | FPS: 56
dt: 0.01599 | FPS: 56
dt: 0.018 | FPS: 56
dt: 0.01599 | FPS: 56
dt: 0.017 | FPS: 56
dt: 0.01699 | FPS: 56
dt: 0.016 | FPS: 56
dt: 0.016 | FPS: 56
dt: 0.01699 | FPS: 56
dt: 0.033 | FPS: 56
dt: 0.01099 | FPS: 56
dt: 0.01499 | FPS: 56
dt: 0.016 | FPS: 56
dt: 0.01699 | FPS: 56
dt: 0.02199 | FPS: 56
dt: 0.013 | FPS: 56
dt: 0.023 | FPS: 54
dt: 0.01799 | FPS: 54
dt: 0.019 | FPS: 54
dt: 0.032 | FPS: 54
dt: 0.01499 | FPS: 54
dt: 0.01699 | FPS: 54
dt: 0.03399 | FPS: 54
dt: 0.024 | FPS: 54
dt: 0.01699 | FPS: 54
dt: 0.016 | FPS: 54
dt: 0.017 | FPS: 54
dt: 0.01699 | FPS: 54
dt: 0.016 | FPS: 54
dt: 0.01699 | FPS: 54
dt: 0.016 | FPS: 54
dt: 0.017 | FPS: 54
dt: 0.01699 | FPS: 54
dt: 0.016 | FPS: 54
dt: 0.02499 | FPS: 54
dt: 0.025 | FPS: 54
dt: 0.01699 | FPS: 54
dt: 0.017 | FPS: 54
dt: 0.01699 | FPS: 54
dt: 0.016 | FPS: 54
dt: 0.01799 | FPS: 54
dt: 0.01499 | FPS: 54
dt: 0.018 | FPS: 54
dt: 0.01599 | FPS: 54[/code:2xktw1s1]

  • Ashley are you looking into this?

    It's basically made my game completely unplayable below 60fps. Even in the high 50's the input delay and dt inconsistency are really noticeable.

  • Yes, I ran into the same issue so I had to do a Monitor Capture. It worked fine.