Vikingvikingviking's Forum Posts

  • In Construct 3:

    - Menu -> Project -> Export -> iOS (Cordova)

    When selecting iOS build, choose "Cordova Project"

    Download project and unzip it.

    Install dependencies

    Download and install nodejs (LTS version): nodejs.org/en

    Open terminal and write: sudo npm install -g cordova and enter password.

    Restart terminal.

    Build the project

    Write cd, drag and drop the folder (that was previously unzipped) into the terminal, press enter.

    Write: cordova platfom add ios.

    Then write: cordova build ios.

    Write: open ..

    Finder opens up and you can click on the sub-folder "platforms" -> "ios" open the <projectName>.xcworkspace.

    Build in Xcode.

  • If on windows, press F12. If on mac press, opt+cmd+i.

    Some browsers needs to have developer settings enabled.

    Hope it helps

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • Hello,

    The easy way I found is to export as cordova project and add iOS platform yourself and then it was possible for me to build with Xcode.

    Wrote how to do it in this post: construct.net/en/forum/construct-3/how-do-i-8/fix-issue-podfile-lock-176591

  • I have the same problem, tried a few solution. In the end I exported as cordova and added iOS platform through cordova and it works when building in Xcode.

    The error started for me at the same time the build servers got an update. Files a bug report bug it was later closed with no action because it was hard to reproduce.

  • Hello,

    Run the game and open the developer tools and check the network tab and console for errors.

  • Hello,

    If the events are in two different event sheets check if you need to include one sheet inside the other so the events are available in both event sheets.

    To include, go to an event sheet and press “n”, you’ll be asked which event sheet you like to include.

  • Thanks! I’ll test and see if I still happens.

  • It's common for software to crash occasionally, but you can mitigate the risk of losing your work by saving regularly. Beta versions of software are usually not as stable as fully released versions, so it's important to use them at your own risk.

    If you come across a bug in a stable version of software, the best course of action is to file a bug report. Without a proper report, it can be difficult for developers to reproduce and fix the issue. Be sure to include as much detail as possible, such as what you were doing when the bug occurred and any error messages you received, to make it easier for the developers to identify and address the problem.

  • Hello,

    The game I'm making is for iOS and sometimes when the app is started the screen is positioned at a offset.

    The project settings are the following:

    Viewport: fit

    Fullscreen more: scale outer

    Might be related to safe area offsets but then the tiled background would probably still be scaled to cover the bottom. I've tried using PlatformInfo.SafeAreaInsetTop to position elements but the weird offset rendering still happens.

    See the image below for a visual demonstration.

    All tips are appreciated.

    Tagged:

  • From what I see the latest stable release is 336. Maybe use that one instead of beta versions, beta versions will introduce new bugs.

    construct.net/en/make-games/releases

  • You do not have permission to view this post

  • Same for me. Says free trial and I'm logged in and have a license.

  • First, good that you think about accessibility!

    I don't have an immediate answer, more a theory. This could be a bug.

    Sometimes websites have texts outside of the viewport with information for visually impaired users, the information could be info on how to navigate with a keyboard. It is possible to make the screen reader ignore the element.

    Maybe this is a use case in Construct. Just guessing.

    In web the button would be picked upl, in Constract that seems unnecessary to me.

    Depending how the elements are set to invisible in web has an impact on how the screen readers approach those elements.

    Screen readers behave differently, usually good to do QA with multiple readers.

  • In JS there are no typing of variables.

    As tomsstudio said it is probably caused by the Bundle bundle declaration, try const bundle when declaring the variable.

    Hope it helps

  • I tried adding On start of layout, for me its not underlined