Ashley's Forum Posts

  • If you intend to refer to a Construct object, you need to use runtime.objects.ObjectName. This is covered in part 11 of the 'Learn JavaScript in Construct' tutorial series.

  • Where is there a variable that declares ARRAY_TotalDLs?

    There doesn't seem to be one. That's why it's not working.

  • It's not yet supported in the Addon SDK v2 - it's on the list to get implemented soon though. I think this is also a good case to redesign the API so you don't have to write so much code to make a looping condition.

  • It's not possible to tell without seeing all your code. It means that variable is undefined though. You need to declare variables before using them - Construct does not declare anything for you (other than occasionally passing 'runtime' and 'localVars'). If you are getting stuck on things like variable declarations I would recommend going through the tutorial course Learn JavaScript in Construct which covers that.

  • Does the ILayer renderScale property do what you need?

  • Please refer to the Forum & Community guidelines. We don't have forum signatures. Everything posted should be at least vaguely connected to game development. I suppose you could post a thread like "what coffee best helps you to do game development", but that would likely involve mentioning brands or otherwise promoting commercial entities which may be construed as spam, and that type of thread tends to be a spam magnet as well as all the bots pile in to post their own links, so I don't think that would be appropriate to discuss on our site. Anything else actually meaningfully related to game development is OK though.

  • A fundamental limitation of the web platform is web workers can't access the DOM directly. In worker mode Construct runs in a web worker and so there is no direct access to the DOM - internally it works around that with lots of message passing.

    If you write JavaScript code in a project, worker mode "auto" defaults to DOM mode to avoid this problem. If you have set worker mode to "yes" to force running in a worker, but you need to access the DOM, set it back to "auto" or "no".

  • It's up to the receiving app what it does with the shared data. A quick test showed a text-only share worked with WhatsApp and email for me, but not with Twitter. If a particular receiving app doesn't do anything with the share, then it's that app that needs updating - the browser is using the standard system share feature.

  • Just write it like you would for any other web content: 

    	const response = await fetch("file.json");
	const myJson = await response.json();
	console.log("Fetched JSON: ", myJson);

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • It depends how you've added it to your project. The easiest way to get help is to share your project file.

    For example if you pasted all that HTML in to a HTML Element object, then it probably won't work, as the HTML is a full document, whereas the HTML Element is just one element inside an existing document. So things like the <html> and <head> tags probably won't work as expected.

  • IIRC, the Steam Overlay will not appear unless you have --in-process-gpu, because Steam doesn't understand Chrome's multi-process architecture. Using --in-process-gpu is a hack to work around that bug in Steam. They really should fix the Steam overlay, otherwise you just keep getting deeper and deeper in to hacks and workarounds, and you eventually get cornered with situations like this, where you have to choose between good performance or having the Steam overlay work.

    IIRC there was some other way to modify a binary to force the high-performance GPU, and maybe that works with --in-process-gpu, but that's still going down the rabbit hole of hacks. The best approach is and always has been for Steam to fix the overlay.

    I've done by best to contact Valve about that, and so far they've ignored us. In situations like this we need every individual developer affected to contact Valve about it so they better understand the scope of the problem.

  • There are many mistakes in your script - inst, LOS, ray and Player are all undeclared, it's console.log not Console.Log, and the first reference to IsFalling is undeclared. I would suggest going through the Learn JavaScript in Construct course which covers the basics of things like variable declarations.

  • Try again with r399 - does it work now? It fixes a bug where it wasn't setting up TypeScript for addons properly.

  • We've recently added back Xbox support. The extent we can support it depends largely on console makers. IIRC the original Xbox support was deprecated because Microsoft dropped support for it. Support is essential to ensure things keep working - keeping using unsupported software means risking waking up one day and suddenly it's all permanently broken and Microsoft won't provide any support and everyone's projects and game launches are ruined. (The same rationale is behind the Addon SDK v2 - addons using unsupported features risk the same thing in Construct itself; experienced developers know not to go anywhere near anything that risks that level of disaster, and that's the same thinking behind not trying to use unsupported Xbox technologies, no matter how important it might be for the product.) In my view it's better for us to say we don't support it either than try to keep using it with that risk hanging over us. IIRC it also used the legacy Internet Explorer browser engine, which we dropped support for years ago, so we wouldn't have been able to keep supporting it until now anyway.

    The new Xbox support is based on WebView2 which is based on the Chromium browser engine. From my tests the technology works great. The main issue is it only works in UWP and Microsoft have restrictions on how you can publish UWP games. I don't know why they have those restrictions and I don't know if they plan to change it. It would be best for anyone interested in Xbox publishing to contact Microsoft about that directly as it's entirely out of our control.

    Supporting other consoles has been extensively discussed in the past, but in summary, if console makers provide something like WebView2, it is fairly easy for us to support; if they don't, it is extremely difficult to support and so far I don't think it is feasible for us to do it. Xbox has WebView2 but only for UWP, and as far as I'm aware (NDAs make it harder to tell), PlayStation and Switch do not have anything equivalent. The status quo is using third-party porting companies converting Construct games to console, which is probably the best we can do for the time being without support for web technologies on consoles.

  • The Platform Info script interface was added in r393.