Eisenhans's Forum Posts

  • imaffett

    Suggestion: The space blaster is a rather old and in a way peculiar product. Are you open for other "benchmark" games/projects? There are a lot of things that the old space blaster does not cover.

  • —

    The new Arcade is yet to be released.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • Typically everything that says "Xbox360-compatible" on the box.

    Some had luck with PS3-compatibles, but that depends on a lot of factors (meticulous driver setups, for instance)

    A wider range isn't supported, unfortunately. That's not up to Construct2 though, it's entirely browser-shenanigans.

  • Imagine a cellphone or tablet held either upwards (portrait) or sideways (landscape).

    It's just a different default resolution and ratio. You can reset that later if you like, you are not bound to these values, they are just there for convenience. Like if you know you make a game like Tetris for mobile phones that is supposed to be played with the phone held upwards, then you would choose "portrait" and would not have to set the ratio yourself.

  • Don't use the height directly to display the text, but rather store it in a variable instead and only count up the variable, if the current height is higher than the value already stored. So no matter if the player goes down again, the variable will hold the highest point.

  • [quote:2m3261an]what Intel can do about jittering Chromium?

    Which hurts more? When a juggernaut like Intel Corp. kicks you in the balls or some small timers on a forum?

    If Intel comes running with a serious case of reproducible bugs I think you take a look at it, at the very least.

  • Dude.. the thread right next to yours..

    Intel wants APKs that demonstrate the performance regression. So go forth and post your stuff!

  • Colludium Thanks for saving us the work.

  • JamardaDigital Would you please file an offical bug for this?

  • That's because 1920x1080 is an even multiple of your original resolution. The other resolution is not..

    Your problem cannot be solved - unless you use letterbox integer fullscreen, with all that it implies (black frame to the nearest even multiple resolution).

    There is no way of having point sampling upres work on arbitrary resolutions without a jagged outcome.

  • [quote:2r9wq9kc]how can Scirra know how much revenue I made with my games?

    Divine epiphany.

  • eli0s

    [quote:1n329ajm]When you say that it gets fixed at 30 fps at start up, you mean that if you leave it running forever, it will still stay at 30 fps and never go up?

    Yep. Never had seen that before so it made me curious. I typically have shaky fps for the first few seconds on my own products, after that it settles at or around 60.

    Somebody

    [quote:1n329ajm]I believe pre 42 builds of Chrome had this fps rounding weirdness. It would sort of luck onto a fps and just stay there.

    Hm. Sounds just like it.

    I wonder why I've never seen it before.

  • eli0s

    [quote:w7e4kfq5]Here is a Fancy Benchmark I put together in a day or so. I wanted to test the recent improvements in jerkiness on both C2 and on the browsers. It's a bit heavy with many sprites.

    Mildly interesting find:

    On a high end rig (linux xeon workstation with a quadro K-Series Graphics card by nvidia) with latest drivers under chromium 40 (that's basically chrome, just the open source build of it) I get a fixed 30fps frame rate at startup. If you go fullscreen it goes up to 60fps and then stays there when I switch the browser back to windowed mode. The 30 fps also does not look glitchy but perfectly in sync. Is there anything special you did to lock at 30fps or is that just a random thing happening?

    In the past Ashley tried to implement a regular 30fps mode, but this failed somehow for a reason I have alrady forgotten and it was thrown out shortly after.

  • Katala is the "reserve" your pooling? And if so: Isn't C2 supposed to handle that for you by now, instead of new()-ing around?