WebView2 experimental Steam support in r502

Not favoritedFavorited Favorited 1 favourites
  • 5 posts
From the Asset Store
Controller Support ,TouchScreen Support , Keyboard Support , Action Platformer, Lots of Animations
  • As of r502 we have implemented an experimental new mode to improve Steam support with Windows WebView2 exports. This thread has more information, and we're interested for your feedback on how it works out for you.

    Update: as of r503 you can now choose both the old and the new Steam modes. The details below have been updated accordingly.

    When you export to Windows WebView2 in r503, there are three options for the Steam mode export setting. These are:

    • None: does not do anything different to support Steam. This will most likely show fallbacks for the Steam Overlay (e.g. showing the actual Steam app over the window)
    • Overlay: this is the mode used in r501 and older. This renders a transparent surface over the app for the Steam Overlay to render into. That works for showing the Steam Overlay, but it means other features like video recording capture the empty transparent surface, and so they don't work.
    • Capture: this is the new mode supported in r502 and newer. This captures frames generated by WebView2 and copies them into the main application window. This means Steam sees the main app process rendering the actual game content like it expects. Therefore the Steam Overlay works, as well as other features that depend on using the window content, such as video recording from the Steam Overlay.

    Note that to use the new capture mode, for the time being you must also uncheck 'Enable overlay' in the Steamworks plugin. The reason for this is enabling that still activates the old overlay mode, which will conflict with capture mode. We intend to publish an update to the Steamworks plugin in future that handles this automatically.

    Note that the new capture mode logs its status to the browser console, as well as any error messages that were encountered. If anything seems wrong, or you just want to check what its status is, check the browser console as usual (make sure dev tools are enabled on export, and press F12 in your app to open it).

    In our testing capture mode seems to work well, and ideally we'd remove the older overlay mode in favor of capture mode. However we want to have your feedback to make sure the new mode is working reliably before we remove the older mode.

    We're keen to make sure Construct's Steam export works as well as possible despite the limitations of Steam's support for browser technology and Valve's unresponsiveness to requests to improve it, and we've gone to great lengths implementing this new mode to try to make sure it can work better. So please give the new mode a try and let us know how it works out for you in this thread.

    Tagged:

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads
  • I’m guessing this might fix the remote play together issue I ran into a few months ago - I’ll give it a try when I get a chance.

    And thanks working on this - it rather came out of the blue!

  • I noticed with both Steam Overlay fixes modes, on focus/on blur dn't work for the exported game. And the new capture mode makes my game stutter.

  • Danwood - we'd like to fix any stutter with the new mode. Can you share your system configuration (e.g. Windows version, GPU, verify GPU drivers are up-to-date, how many displays, what refresh rate the displays run at), and your project configuration (use worker, enable WebGPU, framerate mode, GPU preference, and if changing any of those affects it)?

  • Danwood - the r507 beta release has some improvements for frame scheduling with the new 'Capture' mode. Could you try it out and let me know if it's better?

Jump to:
Active Users
There are 1 visitors browsing this topic (0 users and 1 guests)