Ashley's Recent Forum Activity

  • It doesn't always break the code - it depends on your code. It's not possible to automatically solve this, which is why you have to adjust the way you write your code, as the guide describes.

  • Graphic glitches are commonly caused by system issues like broken graphics drivers rather than being anything to do with Construct. Try installing the latest graphics drivers, or install any available system software updates.

  • Most authentication services don't provide an email address for privacy reasons. You would probably have to ask the user to enter their email address separately.

  • Simple minify should always be safe to use. If you want to use advanced minify, see the guide Exporting with advanced minification for the kinds of code changes you might need to make.

  • Thanks for checking - based on this:

    So I uploaded a new build with that option - XBox controller works but the overlay doesn't.

    ...it sounds like gamepads do actually work when specifying "allow-host-input-processing": false providing Steam Input is configured appropriately. So you can work around gamepads not working, at the cost of not having the Steam overlay work until the WebView2 issue is fixed.

    The "allow-host-input-processing": false should have no impact on any Steam features other than the overlay. All other features like achievements should still work.

  • It looks like a bug. It's best to report such things to the issue tracker following the guidelines.

  • In the past cases of "400 Bad Request" are due to buggy browser extensions, VPNs, or security software, that interfere with the network requests the browser is making, and ends up making them invalid. In particular the error beginning "YIkPfp2E9gyQ09dk_yNy9scwlvKH58Ft..." does not look like a request Construct would normally make. So I would guess this is not actually a problem with Construct.

    If you disable browser extensions/VPNs/security software, you may need to also clear your browser cache afterwards to allow it to start over properly - otherwise it may still be getting error responses from the cache.

  • Yes, large tilemaps are optimized: the tilemap is internally split in to chunks and only nearby chunks are processed for both rendering and collision detection. You could make a test project to check the performance.

  • I tried registering and allocating an app ID, but the Steam SDK fails to initialize, presumably because it's not published yet. I don't want to have a public storefront app just for testing purposes, and I doubt something like an empty "Scirra test app" would be approved for such a purpose anyway, so it seems like we're stuck without a good way to test this ourselves at the moment. I've asked Valve for advice on how to better test this.

  • I just want to mention Valve got back to me about gamepad input - see this post.

  • Just to update this thread regarding the gamepad input issue - Valve got back to me about this, and it turns out that Spacewar - the title with app ID 480 often used for testing purposes - has a custom Steam Input configuration which appears to be why gamepad input doesn't work. I think that means Steam is taking over gamepad input and expecting the app to use Steam Input APIs, but in a Windows WebView2 export it's just using the regular browser Gamepad API, which inside Chromium is using the regular Windows gamepad APIs. So basically it's a configuration issue.

    If you have your own app ID, you should be able to configure Steam Input for that app in the Steamworks app admin - I think you just want to turn it off (from the documentation it looks like you can choose 'None selected') or use a default mapping. As we don't publish titles ourselves we don't have an easy way to test this right now - perhaps someone can give it a go? Hopefully this means you can both initialize the Steamworks SDK and still use gamepad input (providing you set "allow-host-input-processing": false for now until the WebView2 bug is fixed).

    I've also asked Valve for advice on how we might be able to set up a testing mode where you don't need your own app ID to check Steamworks integration and gamepad input are working - hopefully we can make this a bit simpler to try out.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • I think we will get round to this at some point - there's just a lot of other work to be done at the moment - but I would point out that the place we normally advise to post feature suggestions is here: https://github.com/Scirra/Construct-feature-requests

Ashley's avatar

Ashley

Early Adopter

Member since 21 May, 2007

Twitter
Ashley has 1,788,577 followers

Connect with Ashley

Trophy Case

  • Jupiter Mission Supports Gordon's mission to Jupiter
  • Forum Contributor Made 100 posts in the forums
  • Forum Patron Made 500 posts in the forums
  • Forum Hero Made 1,000 posts in the forums
  • Forum Wizard Made 5,000 posts in the forums
  • Forum Unicorn Made 10,000 posts in the forums
  • Forum Mega Brain Made 20,000 posts in the forums
  • x126
    Coach One of your tutorials has over 1,000 readers
  • x74
    Educator One of your tutorials has over 10,000 readers
  • x5
    Teacher One of your tutorials has over 100,000 readers
  • Sensei One of your tutorials has over 1,000,000 readers
  • Regular Visitor Visited Construct.net 7 days in a row
  • Steady Visitor Visited Construct.net 30 days in a row
  • RTFM Read the fabulous manual
  • x43
    Great Comment One of your comments gets 3 upvotes
  • Email Verified

Progress

32/44
How to earn trophies

Blogs