Ashley's Forum Posts

  • We have a separate Blackberry exporter and I don't think anyone's really after WebOS or Symbian export, so I think we'll leave it... although our Blackberry exporter does need updating...

  • Are your graphics card drivers up to date? I have no idea what could cause this and we've never seen any other reports of it so far.

  • No idea then... I guess there must be some kind of bug in the browser that we somehow exposed by some change... I don't know how we could track down what it is, I've gone through what I think is every relevant change for r172. Have you done much testing? Are you able to identify the range of Android versions/devices that are affected?

  • Pode - the plugin should not crash on unsupported platforms though, it should do nothing (and possibly log to the console that it's not supported)

  • It looks like they removed support for the other platforms. It might be better to direct questions about this to the PhoneGap Build service.

  • Construct 2 does not build spritesheets on preview, only export. So you can rest assured the time spent building spritesheets when pressing preview is exactly zero.

  • If it has a keyboard and mouse option, it would probably be fine. Construct 2's UI is probably a bit finnicky to use with finger touches.

  • You do not have permission to view this post

  • You do not have permission to view this post

  • It sounds like some publishers blame browser bugs on C2 as well. For example the Android stock browser on old devices is really slow (no GPU acceleration) and can't play more than one audio track at a time, and on top of that can only start that track in a user input event, so it effectively cannot play any game sound effects, only a backing track. I reckon some publishers try a game in the Android stock browser and think "we can't accept Construct 2 games, they are very slow and don't support audio". Well, that is 100% the browser's fault, and will affect any HTML5 game using any framework... but we're not there to tell them that! It might be worth reminding them issues like that are browser bugs, not C2 bugs.

  • You do not have permission to view this post

  • OK... one more last-ditch idea...

    After exporting, edit the .html file. The <canvas> tag sits inside a div with id "c2canvasdiv". Try removing the <div id="c2canvasdiv"> line and the corresponding </div> after </canvas>. r171 did not have that div, and it was added in r172 so that letterbox fullscreen mode could work.

  • How about if you add <gap:plugin name="org.apache.cordova.media" /> as well?

    If that doesn't work I'm all out of ideas... that's about all the changes we made between r171 and r172...

  • flemmig - the only other change I can see in r172 relating to PhoneGap is we removed the 'device' plugin, because it appeared to be unused... but I guess maybe those older devices need it. Could you try exporting as PhoneGap, then edit config.xml and insert this just before the closing </widget> tag:

    <gap:plugin name="org.apache.cordova.device" />

    Then zip and build as usual on PhoneGap Build... does that fix it?

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • gameop - if you file a reproducible bug report following the guidelines I could look in to it again, but it might take a while if we need to find a specific Android device with the right version, and the Android stock browser is total garbage and it may not be fixable anyway. Chrome runs on any Android 4.0+ device and is far, far better for HTML5 games, so I'd strongly recommend using that either way.