Ashley's Forum Posts

    JiyaHana - this is an unhelpful post to a 5-month old thread, and looks to me like it may be AI generated, like a couple of your past posts. This is a warning that if you continue posting like this you may be banned on the assumption you are using AI to make plausible-sounding but useless posts.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads
  • I don't know. Construct just reports the mouse position as soon as it possibly can. Any delays are probably in the browser or system.

  • Make sure you use 'Invoke download of string' with a string of CSV data. If you're passing CSV data as a URL, it's not a valid URL and so will fail to download.

    Please don't post the same thread multiple times. A similar thread was also posted here so closing this one.

  • I downloaded the project, did 'Set up TypeScript', opened it in VS Code, and started watch mode. It reported 0 errors. So I don't see any problem.

  • The GitHub link doesn't work (perhaps it's a private repository). The quickest way to help would be to share some minimal code that demonstrates the issue in the form of an actual project that can be opened up in VS Code and experimented with.

  • It's difficult to help without seeing all your code, but one mistake I can spot right away is where you have class EnemyControl extends ISpriteInstance, it's incorrect to extend from ISpriteInstance - you should extend from its InstanceType class, e.g. InstanceType.Enemy.

  • This is a deliberate restriction by Apple. Construct will happily run at more than 60 FPS if the browser/system allows it, but Apple have limited the framerate in Safari to 60 FPS. Apple ban other browser engines on iOS, so all other browsers on iOS are just wrappers around the Safari browser engine, so none of them can escape the restriction either. That's Apple for you!

  • You don't need to use base64. You can save the recorded audio in the Binary Data object directly to storage using the 'Set binary item' action. You can then load it again later with 'Get binary item', and once that completes the BinaryData object's 'Get URL' expression provides a URL to the audio data.

    Normally you can't pass a URL directly to a 'Play' action. Instead to play a URL, use the 'Add remote URL' action to assign the URL a name, and then use the name in a 'Play' action.

  • Memory usage and framerate are not directly related. It's possible to have a low memory use and still have poor performance, or a high memory usage and excellent performance.

    If the framerate is struggling, it's not necessarily (and I would say probably not) the memory usage. Use Construct's profiling tools to try to identify what is causing the slowdown.

  • It doesn't detect Y or Z keys. The default controls only use the arrow keys (up, left, down, right).

  • The discrepancy in reported image memory may be due to compression, mipmapping, or engine-specific optimizations. Modern GPUs handle non-power-of-two textures well, and memory is often influenced by viewport size and scaling. To reduce image memory, consider using compressed formats and optimizing resolutions.

    This is, I'm afraid, in the context of Construct and this discussion, largely nonsense.

    If you are using AI to generate replies, don't do that. It will generate things that sound plausible but are in fact completely irrelevant and misleading.

  • Construct actually uses higher-frequency raw pointer input events to avoid being limited to V-sync rate input events.

    As I said before, the frame latency is pretty much all controlled by the browser/OS/graphics driver. There's not much Construct can do to influence it.

  • Try setting downscaling quality to "High", which can help avoid artefacts like that when resizing objects smaller.

  • One of the reasons Construct's behavior's default controls use arrow keys is because they are consistent across keyboard layouts.

    If you want WASD-style controls, it might be possible to just implement all controls (e.g. both W and Z are up, A and Q are left) and so the first thing people reach for will work - but I'm not sure if there are conflicts if you take in to account other keyboard layouts, especially if you use other keys.