Eisenhans's Forum Posts

  • Stable is currently at 0.14.3, beta at 0.15.

    The scirra package is still stuck at 0.14.0, so you guys might update it, when you get the chance

  • There were.. hints, riddled messages and murmurs that the plugin system is something that is being worked on. For example in one posting it was mentioned that the interface side is subject to change (see for example)

    I am confident that the situation will improve.

  • In case you missed it: it is NOW

  • Well, HTML5 still hasn't become magically great performing on lowest end Intel graphics (the upper end of the Intel IRIS line performs significantly better). I'm afraid if the widest possible deployment base is your No.1 priority, I would consider other options, too.

    We are at long last at a point where the situation on desktop has become bearable for mid-range GPUs and OKish for high-end. But that's it. It won't get better for the lowest end. So old laptops will always be a sore spot.

  • While this is (certainly) true for the basic performance etc. I often found that NW.js exhibits problems that chrome doesn't. Jank were none was present in the same chrome version, the whole business with the dead processes and inability to quit, the fullscreen issues, to name a few.

    So whenever they have something new I grab it as soon as I can

  • i want to know what u guys thinkg? lets just wait for Construct 3? or ask for a Port

    From what I understood from all those postings made in regard to this one of the main motivations behind redoing the editor for C3 was to get rid of some older dependencies like the UI toolkit used, because it effectively prevented ports to other OSes.

    So.. yes. Just wait.

  • Yes, the new minimum framerate is 30 FPS.

    Which was, by the way, a really good idea. A lot of problems simply vaporized by doing this.

  • Desktop releases are indeed letterbox-agnostic.

    It is an issue on mobile, because publishers/sponsors as well as the players are rather sensitive about screen real estate.

    On desktop you can do letterbox fullscreen without thinking twice.

    Those audiences are far more sensitive towards jank, framerate drops and stuff like that.

  • Yes, but everything else doesn't And — seems to have gotten it to run somehow.

  • I am working with a wireless xbox360 and a ps2 wired with an adapter, both works good.

    Did you do anything "special" to get them to run? Or did it just work out of the box?

  • Some people claim that, as soon as you use Steam big picture mode, it would work.

    I have not been able to get it to work though. The only thing that really did it for me are wired Xbox360 controllers and 100% compatibles.

    Wireless ones or something that deviates a bit or is connected via a redirection software has not been working for me.

  • Now stock up on tissue packs, to collect all your tears when it breaks again

  • It depends on what you need. If you are happy with chrome/chromium's developer tools (for example for memory monitoring) you can use them with nw.js too.

    Here's a little explanation on how to get them:

    https://github.com/nwjs/nw.js/wiki/debu ... h-devtools

    If you are looking for something like the Unity profiler for in-depth rendering analysis, I don't have an answer.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • Works here on Android. The controls feel super unresponsive on mobile, but the parallax background works.

    What devices/OS revisions did you test on?

  • At some point, Ashley implemented a 30fps-mode, because of public demand. It died in the same Beta-cycle and never reached stable, because it didn't work right with web tech. It caused a lot of problems, so the idea was abandoned.