Ashley's Forum Posts

  • Sorry, it's not something we do ourselves so I don't know how to help. It would be best to use Apple's support if available - it's all their code and services.

  • Looks like this known issue which is a bug in the Chrome browser, not Construct. It appears to be fixed in the next Chrome update.

  • It's based on an internal project unique ID. There isn't currently any option to change it, although if you were determined, you could save the project to a folder and modify the "uniqueId" property in project.c3proj.

  • It's entirely up to you which you use. If you're experienced with both, event sheets and JavaScript code still have their own strengths and weaknesses. For example in my Command & Construct game project, I mostly used JavaScript coding, but I still used event sheets for the menu systems, because it's quicker and easier than having to write code for a menu system.

  • We did some maintenance on the Remote Preview server last week and it accidentally introduced a bug where the host would be disconnected after 25 seconds. This has now been resolved so it should be working normally again (I just did a test and I could successfully host a Remote Preview for 5 minutes). Apologies for the inconvenience.

  • I can't tell what the problem might be just from that. I'd suggest reversing the changes and retry the merge, and make sure you do it carefully. It's best to avoid merging if you can - if you have two branches where someone does something like add an event variable with the same name, then merging them will result in a bad project. So avoid merging, and if you have to, do it really carefully. And... yeah, if you're still using r225, you should definitely update. It might be related to a bug we already fixed long ago.

  • I'd recommend a good game development maths textbook if you want to learn more - and there's a good one available free online at gamemath.com! I have the hardback edition and it's proved useful.

  • I think you'll have to report it to Valve as a bug in the overlay. The overlay is entirely controlled and rendered by Steam and the app itself has virtually no influence over it at all.

  • Construct's Mobile IAP plugin was already updated to use Google Play Billing library v5 in r347, released back in June. If you're using a third-party addon, you will need to contact the addon developer for support.

  • My best guess is it's a graphics driver bug. Try updating your drivers or test it on another machine with different hardware to see if it works there.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • It doesn't look like that message is referring to anything that Construct itself uses. Perhaps you are using a third-party addon that uses the SafetyNet Attestation API. In that case you'd need to contact the addon developer for support.

  • On an unrelated note, I would also like to add that indeed the lack of File System access for the WebView2 export is sad.

    FWIW I submitted a WebView2 suggestion to fix that. I think a relatively small addition to WebView2 could potentially allow full file system access without prompts using the existing browser File System Access API from JavaScript.

    It's technically possible that we could hack in unrestricted file system access ourselves via the WebView2 wrapper, but it would probably mean maintaining two entirely separate file system APIs. We've been round this process a few times over the years and it's always a nightmare doing that. It's by far the best solution to get everything to work consistently cross-platform from existing browser JavaScript APIs.

  • If the same project works on other devices, I would guess it's a problem with Raspberry Pi's graphics driver. It would probably be best to report it either to the Raspberry Pi team (to fix the root cause) or to Google if the issue happens in Chromium (who might be able to work around it).

    Or, if nothing is visibly wrong with the game, you might just be able to ignore it!

  • beforelayoutstart does fire just before 'On start of layout', so it should be firing whenever that triggers, including when returning to a layout already visited. Could you share a project demonstrating your code? Perhaps there is a mistake that has confused you. For example these events fire on ILayout, and you talk about ILayer which is unrelated here, so it seems likely you mixed up something.