Ian wrote:Nice to hear 3-way and 4-way link-ups are working well for you! As to the issue of only the emulator in focus picking up inputs, I'm not exactly sure as to the cause of that since I haven't changed anything regarding inputs; perhaps it's just the way Visual Studio is building the executables. I'll take a look at it and see if I can figure it out.
Key presses normally are only sent to the active or top window in windows. Otherwise pressing buttons would make all the background apps go crazy. Other than hooking the keyboard input (which you can do in the win32 api) this is basically by design. But I am sure most people if they are playing network will be running on separate pcs.
It's joypad inputs I'm specifically referring to here Ian, not the keyboard, a feature the old network supported for single PC play.
I set up several single PC multiplayer games using the old network with me and two other friends all using pads - you can see it working here in a 3P game of Daytona 2 https://youtu.be/d0cyyaqYes8 and Scud Race https://youtu.be/wOdIg9gTl5M
This worked right from the onset with the old version of the network. I was also able to set multiple versions of the emulator to all respond to one single pad - I'm controlling 6 versions of Scud Race off the one pad in this video: https://youtu.be/Je2_LdCyi34
In the new network builds, I need to actually click on one of the emulators for it to pick up what my pad's doing and doing this will then make any other version of Supermodel that are open no longer respond, regardless of whether they're set up as Joypad 1 or 2.
my PC was starting to struggle with 4 versions open. You must have an absolute beast of a setup. Outstanding work! FYI, if you want to organise your screens more easily on the desktop, just minimise all the cmd prompt Windows that open, minimise all the GUI's you've got open, then right click down in the task bar to the right of your open windows, and you'll get an option to arrange the open windows side-by-side.