Ashley's Forum Posts

  • Yes, it should work fine. Did you try it yourself?

  • The Nexus 7 is a cheap and decent tablet that can run Chrome for Android.

  • Construct 2 never exports .wav files, so you don't need to delete them or set up your server for them.

  • OK - I guess there are a lot of you still asking for this, so we'll bring it back for the next build. I guess it's not your fault if publishers want to support old versions of iOS.

  • You only need .m4a (not .mp4a) as audio/mp4 and .ogg as audio/ogg.

  • Closing, please report CocoonJS issues to Ludei.

  • You don't need to use anything other than the 'Request fullscreen' action in the Browser object in Chrome for Android. One limitation is it only works in a user-input event, so you need to use it in an 'On touch' trigger or similar.

  • Huh, that's odd - desktop Chrome fires a devicemotion event with null values. It's strange devicemotion would fire at all for a desktop computer. I've added a workaround for the next build, thanks for the catch.

  • I've updated the tags to have stable ordering in the next build (alphabetical by ID). I don't know why you would mark any of the files read-only though - if Construct 2 needs to change the file but it can't write to it, it can't then change other files otherwise it might corrupt the project. Hopefully this change is enough to avoid having to have any project files read-only. Let me know if there are any other changes you need to avoid unnecessary diffs in source control.

  • Closing as not a bug, you can ignore those messages.

  • Construct 2 sets the canvas size automatically. If you want it to be a fixed size, turn off 'fullscreen in browser' in project properties and set the window size property to 618x463.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • It sounds like the window size is smaller than the layout size, in which case it's working correctly.

  • This is suggested every couple of months and I don't really feel like typing out the whole rationale every time... tl;dr - it would be a different product, we're not going to support it, outside of the Javascript SDK.

  • They mean different things. The X and Y co-ordinates are where the object is. The vector X and Y are the velocity of the object.

  • As far as my own testing showed, the option never worked on Android, only iPhone. On Chrome for Android, the Fullscreen API is supported, which is a much better solution. You should start using this feature if you are not already ('Request Fullscreen' in the Browser object). Chrome is steadily replacing the stock browser on Android, and it's just a waiting game before it's the vast majority of Android devices. I don't know what more we could do for Android.

    iOS 7 removed the ability to hide the address bar, and the vast majority of iOS users are on the latest version - Apple are generally very good with getting everyone on to the latest version quickly. According to Apple's stats 82% of devices use iOS 7 and this number has increased about 3% in the past month, so soon enough it will be nearly universal, which to me would seem to make iOS 6 on the cusp of irrelevance if it is not already (notwithstanding fussy publishers).

    iOS 7.1 is due out in a month and supports the new minimal-ui directive. This is not as good as the fullscreen API in Chrome, but is a big improvement on iOS 7.0's restrictions. Soon enough after launch I would imagine the majority of iOS devices would be updated, and then the problem is solved for the majority, rather than a rapidly disappearing minority.

    If you have publishers who insist, and they cannot be persuaded otherwise, you can try implementing the scrolling hack using the Browser object's 'Execute javascript' action.