Oh cool, this thread is still kind of active. I e-mailed you about this a couple days ago SailorSat and have been playing around with the Daytona live spectator program and trying to get it to work. For the time being I'm using the files and instructions in
this post since it's the most complete and straightforward explanation I've seen so far. I haven't messed around with
the other tools you linked very much yet since some of the config files in there are a little different and I'm trying to take this one step at a time and not bombard everyone with too many troubleshooting questions.
Anyway, I'm trying to set up a full count of 8 Daytona game sessions plus a spectator on one computer, just for the sake of testing for now. The 8 actual game sessions are fully booting and running correctly, which suggests that the lagfix tool is configured correctly, but the spectator session gets stuck on the "NETWORK CHECKING" screen and never advances, and I can't figure out the cause. For what it's worth, the stats program does seem to correctly identify the instance of the emulator that is meant for spectating; the overlay wraps around that specific emulator window.
These are all of the config files:
The top 8 docs are the m2network settings for each of the 8 player stations.
On the bottom, the first doc is the m2network settings for the spectator station, followed by the config files for the stats and lagfix tools.
On the player stations, car 1 is set to Master and the rest to Slave. The spectator station is also set to Master and car 1; it wasn't clear to me whether this was correct or not.
All other game settings are identical between emulators, and they're all running the "Saturn ads" version of the game. The cabinet type is set to "Special" for all of them.
All IP addresses in these files are set to localhost since it's all running on one PC at the moment.
Did I mess up the port assignments somewhere or is something else the cause?
EDIT: Also, uh, when I started messing around with these tools, my laptop keyboard's Windows key stopped working. If I plug in a USB keyboard or use the Win10 OSD keyboard, the key functions fine on those. I've tried several googled suggestions for fixing this but no luck. I guess there's a chance that this might be an unrelated hardware failure but just throwing this out there.