Ouch! I hadn't considered that. Why would the antivirus even pick up on it? Hmm...

Good news is, I'm working on a new version that allows communication between BMSwitch and nw.js builds. What that means is you'll be able to set resolutions and switch between fullscreen and window modes from within the game itself! It also means the Launcher.exe becomes a bit redundant, and if that's the only one virus scanners get freaked out by I guess I could just ditch it for the new version.

Okay, here's how to use it.

Export your game with nw.js and place Launcher.exe and Game.exe in the win32/64 folder.

Run Launcher.exe and select a resolution and screenmode. Then press either launch or exit, in both cases your choices get saved. After pressing launch the game will run with your choices applied. If you want the 'window' choice to work though, you'll need to set up some events at the start of your game like I've done in the test.capx example.

If you've run the launcher once and don't want to change resolution or screenmode again you can just run Game.exe directly with your saved settings.

EDIT:

Oh, and you need to turn kiosk mode off in build settings or you won't be able to cancel fullscreen in C2.

-----------

Quick breakdown of what the different cfg files do:

launch.cfg:

Used by Game.exe to get the name of the executable (nw.exe), the desired resolution to run in, the delay in seconds before switching to the desired resolution, and the time in seconds to display a black background while the game loads. (The last one doesn't work properly so I'd leave it alone for now.)

You should only change "nw.exe", and the two last lines in launch.cfg. The resolution values get overwritten every time launcher.exe gets run so there's not much point changing those.

mode.cfg:

fullscreen/window toggle. 0 = fullscreen, 1 = window. Set by launcher.exe. Read by Game.exe (tells it not to switch resolution in window mode) and by your nw.js build (check out the capx to see how).

osH.cfg/osW.cfg:

Reference values. Allows C2 to read the resolution selected in launcher.exe. Best not mess with these.

osDH.cfg/osW.cfg:

Same as above but for system resolution.

res.cfg:

This is the file where you set up all the different resolution choices you want to make available to the player.

ui.cfg:

You can set your own names for launcher.exe's window and buttons here.

Okay here it is! No proper readme in there yet. I'll write one up when I feel less lazy <img src="{SMILIES_PATH}/icon_razz.gif" alt=":P" title="Razz">

https://www.dropbox.com/s/r1nwmlpav9629 ... 0.rar?dl=0

New in this build:

Window mode – you’ll need to set up a couple of things in your game’s events for it to work. See the testbuild capx inside the archive for an example.

Future plans (v2.0):

Switch resolutions in-game, switch between window and fullscreen in-game, and restore system resolution when the game is minimized (Alt-TAB).

Mac/Linux support.

Customizable launcher with various graphics and layout options.

Sure thing! I'm looking into license options atm for something as permissive as possible; no need to credit me, use however you like etc. Might just go with public domain to minimize the amount of headache

I do plan to offer another version in the future with support for mac/linux and more customization options for the launch window, including using your own graphics, buttons, layout style etc, which will be commercial. Small fee, the price of a cup of coffee or two probably. You'll be able to use that however you like as well, with the exception of re-selling the software itself.

Nah I don't think it's your windows version. I have one win7 and one win8.1 system to test on, and it works as intended on both of those.

What this does is simply change the system resolution temporarily, forcing everything (including your game) to run in that resolution for as long as the target process (your game) is running.

Have you tried lowering the resolution manually through Control Panel/Display to see if the scaling gets stretched the same way? If it doesn't, then the problem is on my end. But if it does, then maybe it's something to do with the way your display/display driver handles non-native resolutions. For instance, many if not most laptops will stretch everything to fit the screen by default, instead of scaling to fit aspect ratio.

Anonnymitet:

Thanks <img src="{SMILIES_PATH}/icon_e_smile.gif" alt=":)" title="Smile">

Here's the updated version!

Test build (Launcher.exe and Game.exe is in here):

https://www.dropbox.com/s/b2ehi0odblvz4 ... d.rar?dl=0

Test capx:

https://www.dropbox.com/s/w7ikvdcyxc2ue ... .capx?dl=0

Some notes:

The program consists of two files. Launcher.exe and Game.exe. Launcher.exe is the UI part. This is where you choose your resolution and window/fullscreen (which doesn't work atm <img src="{SMILIES_PATH}/icon_razz.gif" alt=":P" title="Razz">). Game.exe reads the resolution set in Launcher.exe and switches to it before executing nw.exe. So you don't need to run the launcher itself every time you want to run your game.

Both Launcher.exe and Game.exe will create a new folder "cfg" inside your build folder and fill it with some txt files if they don't exist already. You can edit these to configure the button texts, window title text, and the resolutions you want to make available to the user. Launcher.exe will check the resolutions listed in 'res.cfg' against the ones available to the system you're running on, so it'll only list valid resolutions (as reported by the system).

'ui.cfg' is where you can set the texts displayed in Launcher.exe to your liking. Pretty straightforward stuff. At the bottom of 'ui.cfg' you'll see the line 'Game.exe'. Set that to whatever you want to rename Game.exe to to point Launcher.exe in the right direction.

Please let me know how it works out for ya and what system you're running on <img src="{SMILIES_PATH}/icon_e_smile.gif" alt=":)" title="Smile">

EDIT:

Almost forgot.

In 'launch.cfg' you'll see this:

nw.exe (change this if you want to call nw.exe something else)

1920 (current resolution as set by Launcher.exe)

1080

2.50000000 (delay in seconds before switching resolution. Tweak to suit your game's loading time)

0.000000000 (time period in seconds to display a black screen while loading. The nw.js game window will display on top of it so you can safely leave it high if you want)

Thanks! I've tweaked the implementation somewhat since before so hopefully that helped. I'll throw a test build together and be back in a bit

The games I wrote in Blitz Basic 3D (a DirectX 7 engine from 2001) are still working on my Windows 10 PC. Most of the Construct 2 games I made in 2014 don't work properly anymore in any of the current versions of web browsers

Yeh the Blitz languages were always rock solid. Too bad Mark Sibly never knew (or cared) how to market them properly. That said, C2 at least is very solid too, just let down by the wrappers.

Hmm... well that's not good. I think I need to find myself a win10 machine and do some thorough testing. Thanks for the help

Damn haha

You didn't rename nw.exe to something else by any chance?

Hi everybody!

I'm writing a resolution switching tool to allow for better performance on gpu's with low fillrate capacity, intel integrated and the like. I don't have a computer with windows 10 installed so if you do, I'd be really grateful if you'd be willing to test it out for me and see if everything works the way it's supposed to.

Here's how to install and use it:

Extract the 'Launcher.exe' file to your win32 or win64 build folder and then run it.

You'll see a pop-up window with one rolldown to change resolution and another one for windowed or fullscreen mode. Change the resolution to 1024x768 and then press 'Launch'.

The screen resolution should change to 1024x768 for as long as the game runs and revert back to desktop resolution when you quit. Works best on exports with 'kiosk mode' enabled.

Thanks for helping out, I really appreciate it

https://www.dropbox.com/s/6mu5zf3qou791cm/Launcher.rar?dl=0

Can you post an event sheet screenshot of your attempt so far? I haven't played Shinobi 3 so don't really know how that attack works