Experimental new lightweight Windows wrapper

Ashley

I am experimenting with using multiple windows at the same time for the same game. In my first test I used a local server and WebSock to make the different windows communicate. But I think it might be interesting to get the same result without using external tools.

WebSockets can be replaced with LocalStorage: all instances of WebView share the same memory (and they always refer to app.localhost/index.html)

I have two problems left

1. the ability to launch a new instance of WebView directly from WebView itself. If there will be a specific plugin for WebView I would like an action like "run file" of the NWjs plugin

1. 2. the possibility of launching WebView with arguments readable by Construct 3

My idea is a command (PowerShell or command line) like MyProject.exe x=5 y=6

In C3 I would likethe opportunity to have something similar to:

const x = runtime.WebView.arguments[0]; 
const y = runtime.WebView.arguments[0]; 
 
// or  
const { x, y} = runtime.WebView.arguments; 
 
 
const result = x + y; 
 
runtime.objects.Text.text = result; 

This would allow you to open multiple windows at the same time, each on a different layer portion always using the same source file.

In my experiment I used Deno to launch WebView 4 times, each time from a different folder.

 await Deno.run({ cmd: ["./webview/cameras/A/MultiWindows.exe"] }); 
 await Deno.run({ cmd: ["./webview/cameras/B/MultiWindows.exe"] }); 
 await Deno.run({ cmd: ["./webview/cameras/C/MultiWindows.exe"] }); 
 await Deno.run({ cmd: ["./webview/cameras/D/MultiWindows.exe"] }); 

It would be nice if it were possible to avoid such code perhaps using an event similar to:

// pseudocode 
Run File: "MultiWindows.exe layout=A" 
Run File: "MultiWindows.exe layout=B" 
Run File: "MultiWindows.exe layout=C" 
Run File: "MultiWindows.exe layout=D" 
 
//or 
Run File: "MultiWindows.exe A" 
Run File: "MultiWindows.exe B" 
Run File: "MultiWindows.exe C" 
Run File: "MultiWindows.exe D" 

// pseudocode 
On start: go to layout WebView.arguments.layout 
 
// or 
On start: go to layout WebView.arguments[0] 

I believe that the combination of these two things can allow the creation of projects like this without having to go through other applications.

Obviously, I don't know if it's technically feasible, if it's worth the effort, if it's in your priorities.

Hi, I have a problem.

1) If I export via NW.js, then the game does not slow down and gives out 144 FPS ( " every tick - set text to - fps" ), good!

2) If I export a clean, empty project-project via webview2, then the game does not slow down and gives out 144 FPS ( " every tick - set text to - fps" ), good!

3) But, if I export my game not through NW.js, but through webview2 using the same Project settings as in the base project (if I create a new clean project), then the game gives out not 144 fps, but 50-55 ...

4) If you lower all the Project settings in the game, such as anisotropic filtering, the frame rate and so on, or turn it off, then you get a fps of 70-85, but not higher.

5) I tried running the game directly in the Microsoft Edge browser and everything worked smoothly there. (I actually use C3 in google chrome)

I don't think the game can consume a lot of video memory or processor resources, in any case, I have a powerful computer, this is not crisis 3 .... any ideas how to help me? I thought, after export, the FPS limiter would be set, but depending on whether several of them are enabled or disabled, the FPS settings may be slightly lower or higher. It turns out that the computer gives 144 fps, the game is 50-70 fps and I see micro-micro freezes (sorry, I use google translator)

My game, you can try to export via webview2 and check if you will have fps 70 - 85 cloud.mail.ru/public/UB6F/6DxgrYrZU

UPD: I found a problem, when I used export via NW.js, then I entered this into the command line '--in-process-gpu --disable-direct-composition --enable-features=nw2' , now I did export with a clean command line and everything is fine

Hello, how can I disable the cntrl-P cntr-R keyboard shortcuts when exporting via Microsoft Edge WebView2 ... or how can I disable the buttons participating in the keyboard combination, for example P or R, etc ...?

For example, for export via NW.js, such a script is implemented and work:

window.addEventListener('keydown', ev => {

if (ev.ctrlKey && (ev.code === 'KeyP' || ev.code === 'KeyR' || ev.code === 'KeyF')) {

ev.preventDefault();

}

});