Ashley's Forum Posts

  • Normally you shouldn't set a minimum delta time at all. You don't want your game to start running in fast-forward if it goes over 60 FPS - what if someone has a 120 Hz display? It's intended to only be set for things like catch-up time.

  • There's no way to identify the real physical screen size, at least from information browsers give you. How do you know if the display is a colossal display used by the stage at a concert, or a desktop monitor? There may be no difference in the resolution or device pixel ratio in either case.

    On mobile devices, your best bet is probably just to rely on the screen size reported by Platform Info. That is in CSS pixels so does not vary with the device pixel ratio, and so you can probably work on the assumption CSS pixels are about the same physical size across devices, and so the screen size is a rough indication of the display size.

  • You do not have permission to view this post

  • What's the point of allowing developers to define their own c3runtime/main.js if other different files are automatically searched anyway?

    Construct only looks for files that your addon configures. But the default configuration includes runtime files plugin.js, type.js, instance.js etc. If you don't want the default configuration, call SetC3RuntimeScripts() with an array of just the script files you want to use.

  • Try clearing your browser cache.

  • As ever, we get far, far more feature requests than we can possibly act upon, which is part of the reason we have the addon SDK in the first place. If you want to submit an official feature request, you can do so here.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • Your code also confuses object types and instances. I'd suggest going through the Learn JavaScript in Construct tutorial, or the quick-start guide, or using TypeScript which will catch such mistakes for you.

  • When you choose to use a third-party addon, you are trusting the developer of that addon for long-term maintenance. If they give up on it for any reason - which they are perfectly entitled to do, especially if it's free - then it won't be supported any more. You should bear this in mind when choosing to use third-party addons.

    The entire purpose of the addon SDK is to allow other developers to implement more features than we have the resources to do ourselves. It is not generally feasible for us to officially reimplement any particular third-party addon, and besides doing so defeats the purpose of the SDK.

    The Addon SDK v2 ought to have the technical capability to support this - it supports all officially supported APIs from the old SDK, and if any are missing, we will prioritize implementing them.

  • It all works for me - the key is to put the code with the call to registerProcessor in a separate JavaScript file in the 'Files' folder, and load it with audioContext.audioWorklet.addModule("audioWorklet.js"). Here's an example.

    • Post link icon

    digitalsoapbox please note from the Forum & Community guidelines:

    Be polite, respectful and welcoming

    Be supportive of the products we all use and the team behind it, and make sure feedback is constructive (no pun intended.)

    Having a persistently antagonistic, cynical, combative, sceptical or complaining attitude. For example, no software is perfect, but if you continuously claim that our products are absolutely terrible in every way, you may quickly wear out your welcome.

    Deliberately trying to provoke a reaction.

    Your recent posts have repeatedly gone against these guidelines and are not acceptable. I am closing this thread and please be warned that if your posting continues to go against the Forum & Community guidelines, further moderation action may be taken.

  • You do not have permission to view this post

  • I would advise to file any problems to the issue tracker, as we have a process designed to help identify and resolve problems there, and issues only mentioned on the forum are easily lost and forgotten.

  • If this only happens in preview or remote preview, try clearing your browser cache. There were some server-side changes for the new preview system. They should have already come through by now, but I guess old or rarely used devices might not have updated yet.

  • There has not been any intentional change in support. If you think there is a problem with the latest release, please file an issue.