Ashley's Forum Posts

  • IG is also invite only now, so if you are not approved you cannot release any game at all anyway. So the plugin is not used so much any longer..

    It is indeed a rarely used export option since Meta changed Instant Games to be invite only. It is now one of the least used export options in Construct.

    We developed the Instant Games plugin on the understanding it was a platform open to anyone and so potentially attractive to many Construct users. Then Meta went and changed the rules and it is far more exclusive now and harder to justify having in Construct. So I don't think we will do any more work on the Instant Games plugin. Third party addons can still extend it or you can use JS coding directly in Construct to access the API yourself.

  • Just a reminder that connectivity related issues are discussed near the beginning of the first multiplayer tutorial which discusses things like mobile networks and TURN servers.

  • If you look at the issue tracker, this is a known issue in the latest beta and will be fixed in the next beta release.

    Beta releases sometimes have issues like this. While helping test them is useful, if you don't want to put up with occasional issues you can stick to stable releases.

  • See this thread which answers the same question.

  • I think the only way for iPhones is to publish an app. Apple don't allow Safari on iPhones to go fullscreen, and because Apple ban other browsers (no idea how they get away with that), other browsers are just skins over Safari and so have the same limitations. So if you try Chrome, Firefox, Edge or anything else on iPhone, you're still using Safari but just with different branding.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • The screenshot is taken at the same resolution the game is displayed at.

  • iPhones run iOS, and so Apple just don't support fullscreen in Safari there yet unfortunately.

  • It downloads a PNG file with your screenshot. It doesn't copy it to the clipboard. You should see the download happen as soon as you click the screenshot button.

  • Saving to a folder is currently only supported in Chrome and Edge. If you're using Firefox or Safari, it's not supported there, because those browsers don't support accessing local folders.

  • There's already a screenshot button in the debugger.

  • Is it Safari on macOS, iPad or iOS?

    IIRC Apple do not support letting Safari go in to fullscreen on iOS.

  • It's covered in the Addon SDK documentation.

  • The library we depend on for Android publishing - Cordova Android - only recently published an update to meet the latest requirements. We've now updated to use that, but then it needs some more time for the update to reach a stable release as per our normal release schedule.

    These days Google increase the API level requirement once a year, so I don't think there will be any new requirement until next year. Sometimes updating does not require any changes at all, but this year Android made a range of changes that mandated updates and so meant a bunch of things had to be changed both in the Cordova library and in our code. All the work's done though, and it's there on the latest beta releases.

  • I haven't isolated the issue yet on a blank project, but my project is a bit jittery when vsync is on, as well as slight input lag (as always with vsync). This happens even on a 240hz monitor with vsync on.

    At 60 Hz the frame display latency is 16ms; possibly 32ms if it takes two frames for a change to appear. At 240 Hz the frame display is around just 4ms, or 8ms if it takes two frames - a fraction of a single frame at 60 Hz. This suggests vsync is not actually the thing imposing latency; it may not be the cause of jittering either. Are you sure it's not that your project is using too much CPU/GPU? That would also explain why it would be difficult to reproduce in a blank project.

  • I think we will leave the current platform up until the end of 2022 and then move to annual refreshes. I realised the description and forum post were out of date so I updated them to clarify that.