How does the Node export work?

  • I got how the awesimiunminmmniuom exporter worked. But I'm curious how the current desktop exporter work. The reason is, I want to know what browser engine is at the core, so I can know which developers to poke to work on gamepad support.

  • Chrome, (Well, technically Chromium), same as Awesomium. But better.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads
  • nice. I will keep talking to the chromium team about trying to add more support for more gamepads....slow but steady!

  • Chromium already supports the gamepad API - it should work with XBox 360 controllers - but certain other kinds of controller need special support from Google, I think.

  • Chromium already supports the gamepad API - it should work with XBox 360 controllers - but certain other kinds of controller need special support from Google, I think.

    This is my issue. It's really not fun to tell a user they have to go buy a new 40$ controller because for some reason only 4-5 controllers are supported well. I had been talking to the guy who manages the code for it, my intention is get to the real source of the issue and see if there is a realistic solution. It may be to have people use a plugin like the x360 emulator or to just add more robustness to the gamepad API.

    This all stems from the fact that I have a bunch of really good (main stream) controllers here at my house, yet only one works. I want to try and fix that and make the experience more clean

    End Goal: No matter what joystick you plug in, it will work. This benefits HTML5 and it benefits C2 and most of all, the user.

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