Ashley's Forum Posts

  • The engine is not designed to support this. It only works in C2 by accident. In C3 we tightened things up so things that are not supported are not allowed.

    There's no need to do this anyway: just put all the events in the included event sheet in a group instead.

  • Error 1214 is ERROR_INVALID_NETNAME ("The format of the specified network name is invalid."). The IP address looks mis-typed, local addresses like that usually start with 192, not 198. Alternatively perhaps your local IP address changed.

  • As noted in the documentation:

    Each release of the Greenworks plugin must be used with a specific version of NW.js, and a specific version of the Steamworks SDK. Make sure you get the right versions, otherwise the plugin may not work. The release notes for each release of the Greenworks plugin specify which versions you must use it with.

    NW.js 0.30.4 is currently the latest version supported by Greenworks. If you use the wrong versions it won't work.

  • I haven't checked the Raspberry Pi lately, but last I checked the GPU driver was very iffy. C3 could run, but it took some extra configuring, performance wasn't great, and it was quite unreliable. In contrast the Tinker Board is great - C3 seems to run just fine on it out of the box. Just make sure you do a software update after setting it up so Chromium updates to the latest version.

    • Post link icon

    Closing this thread now. It's 4 years old, 40 pages long, and the information is no longer up-to-date.

    Please find the Greenworks plugin now on the Addon Exchange:

    For Construct 2: https://www.construct.net/construct-2/addons/83/greenworks

    For Construct 3: https://www.construct.net/make-games/addons/84/greenworks

    If you have further questions about the Greenworks plugin please start new forum threads.

  • Please just vote on the features on the suggestion platform. Posting threads about them doesn't mean we have more hours in the day to work on features, and when we come to work on new features, we will use the vote counts as our preferred measure of how many users want to have it.

  • Providing the Audio plugin's "Play in background" setting is disabled (the default), then Construct also suspends all audio playback when going in to the background. So that should not be a problem either.

  • You just need one input event to enable all audio playback. It doesn't have to be every layout, just once on startup.

  • Desktop browsers are starting to implement the restriction too. NW.js should not be affected though.

  • Canvas+ has not been supported for over 3 years. Use a webview-based platform instead.

  • In mobile apps sound should be able to autoplay automatically.

    In browsers sound cannot autoplay until the first input event, as a deliberate measure to prevent web pages annoying you.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • This is exactly why things like "disable WebGL 2" are pretty poor hacks. If there is a GPU driver issue, it could well affect WebGL 1 too. Disabling WebGL 2 is merely papering over the cracks and other issues could crop up elsewhere because the real problem hasn't been addressed. I would encourage anyone affected to make minimal reproduction test cases and file issues with Google at crbug.com.

  • It hasn't aged well - it's ended up full of cruft nobody uses any more, like "Windows Phone 8 App", "Crosswalk" etc. I think we should come up with a better alternative that won't meet the same fate...

  • It looks like it might have shipped accidentally. It wasn't a listed release, the tracking issue isn't marked "fixed" yet, and the latest spec differs from what was shipped. I've asked for clarification on the tracking issue. Obviously we'd like to implement this but if it's likely to change in feature to what the spec says, it would be better to wait, otherwise we'll be writing code that is going to be broken in the near future.

  • I just realised we only made the change for the C3 runtime. I don't generally like doing this but I did the same for the C2 runtime as a last-minute change for today's stable release (r111). So can you give it a go with that release and see if that helps?

    If it still displays a blank screen it's possible it's actually a different issue not to do with WebGL 2.