| Main > Driving & Racing Cabinets |
| fooling with m2emu network |
| << < (61/68) > >> |
| Super-Becker:
Everything has been working out for me in the link games on M2. I saw that some colleagues' files have different information than mine: PC1: m2network.ini: [Network] Rxport=11200 NextIP=PUT PC2 IP HERE NextPort=44405 FrameSync=1 m2lagfix.ini: [m2rx] LocalHost=127.0.0.1 LocalPort=8001 RemoteHost=127.0.0.1 RemotePort=9002 StallDetection=1 [m2tx] LocalHost=127.0.0.1 LocalPort=9001 RemoteHost=127.0.0.1 RemotePort=8001 [m2stats] RemoteHost=127.0.0.1 RemotePort=8000 PC2: m2network.ini: [Network] Rxport=44405 NextIP=PUT PC1 IP HERE NextPort=11200 FrameSync=1 m2lagfix.ini: [m2rx] LocalHost=127.0.0.1 LocalPort=8001 RemoteHost=127.0.0.1 RemotePort=9002 StallDetection=1 [m2tx] LocalHost=127.0.0.1 LocalPort=9001 RemoteHost=127.0.0.1 RemotePort=8001 [m2stats] RemoteHost=127.0.0.1 RemotePort=8000 I ran the emulator using "EMULATOR.EXE" because "emulator_multicpu.exe" caused some problem that I no longer remember. Now I use SailorSat's multicpu_1.1b which is the best version. I would also like to take this opportunity to thank you: -Congratulations on your work and thank you very much SailorSat! I don't use any lua scripts from SailorSat. I always use m2lagfix in linked games. The flashing cars rarely appear for me, and when they do I just close m2lagfix and the emulator, and open them again. I did several random tests to try to find out what favors flashing cars or not, but I didn't come to a conclusion. I hope I helped someone. |
| MrThunderwing:
--- Quote from: PL1 on June 11, 2024, 07:05:51 pm --- --- Quote from: MrThunderwing on June 11, 2024, 02:38:36 pm ---If I click on the link, this is what I get on-screen in attachment one, there's no download option anywhere I can see on screen. --- End quote --- Here's an easier link. https://github.com/SailorSat/daytona-utils/tree/master/src/scripts - Click on the desired script. - On the script page, there's a download link. Scott --- End quote --- Scott my dude! Thanks for sharing that link, the OG Indy 500 still keeps failing the link a few seconds after connecting, but the LUA script for Indy 500d seems to be creating a nice stable connection. I'm able to drag windows around the screen to reposition them and the link doesn't immediately disconnect, so that's cool. |
| jorgenjl2:
--- Quote from: Super-Becker on June 12, 2024, 01:11:01 pm ---Everything has been working out for me in the link games on M2. I saw that some colleagues' files have different information than mine: PC1: m2network.ini: [Network] Rxport=11200 NextIP=PUT PC2 IP HERE NextPort=44405 FrameSync=1 m2lagfix.ini: [m2rx] LocalHost=127.0.0.1 LocalPort=8001 RemoteHost=127.0.0.1 RemotePort=9002 StallDetection=1 [m2tx] LocalHost=127.0.0.1 LocalPort=9001 RemoteHost=127.0.0.1 RemotePort=8001 [m2stats] RemoteHost=127.0.0.1 RemotePort=8000 PC2: m2network.ini: [Network] Rxport=44405 NextIP=PUT PC1 IP HERE NextPort=11200 FrameSync=1 m2lagfix.ini: [m2rx] LocalHost=127.0.0.1 LocalPort=8001 RemoteHost=127.0.0.1 RemotePort=9002 StallDetection=1 [m2tx] LocalHost=127.0.0.1 LocalPort=9001 RemoteHost=127.0.0.1 RemotePort=8001 [m2stats] RemoteHost=127.0.0.1 RemotePort=8000 I ran the emulator using "EMULATOR.EXE" because "emulator_multicpu.exe" caused some problem that I no longer remember. Now I use SailorSat's multicpu_1.1b which is the best version. I would also like to take this opportunity to thank you: -Congratulations on your work and thank you very much SailorSat! I don't use any lua scripts from SailorSat. I always use m2lagfix in linked games. The flashing cars rarely appear for me, and when they do I just close m2lagfix and the emulator, and open them again. I did several random tests to try to find out what favors flashing cars or not, but I didn't come to a conclusion. I hope I helped someone. --- End quote --- I will have to try using the new multicpu1.1b emulator and m2lagfix again since my flashing is pretty bad. What does the m2stats do? I thought that was a 9th (or third in your case?) pc that displays where people are on the track but admittedly I did not really look closely at that part yet. SailorSat - Do you have a m2lagfix and m2network ini settings you recommend for 2p and 4p so we have a single set of ini’s that we know work? I can try what Super Becker has and try to translate to 4p if having the stats doesn’t hurt anything. |
| SailorSat:
First of all, please don't quote the whole wall of text every time you reply :) the configuration you've posted does not utilize m2lagfix at all. m2network.ini #1 receives on 11200 and points to ip2:44405 m2network.ini #2 receives on 44405 and points to ip1:11200 Second... I managed to "fix" the receive code - that seems to fix overrev and sgt24h in 4 player mode (no more glitchfest). But I found yet another issue... (although that is a good thing, as that might be the initial issue all along) stay tuned :) *EDIT* mhm... I sometimes feel stupid that "fix" enables OverRev and WaveRunner to boot up quite reliable. and earlier today I had SGT24H and STCC running with 4 players - I then took a nap. having changed nothing since, I cant get them to link up anymore. it feel like once in a 50 restarts, they link up (and play) fine. otherwise they just stay at ther "network check ok!" screen and do nothing. |
| SailorSat:
Guess it's time to update the initial post in this thread. Today I bring you... M2EM 1.1c ( grab a copy at http://files.arianchen.de/m2em/emulator_multicpu_11c.zip ) the network code for receiving data has been fixed - this allows most games to link up. Super GT 24h still feels like gambling for some reason. On that note - I fixed the script for indy500 and added scripts for waverunr and stcc to boot reliable. you can find the scripts at https://github.com/SailorSat/daytona-utils/tree/master/src/scripts ( click on the script you want, then click on the download icon in the top right corner ) As for the flickering cars issue... I now know for sure there is a timing issue! If I slow down the network even a little bit, basically all error disappear - be it link up issues (without scripts that is) or flickering cars. Still trying to figure out the timing logic in m2em... so there may be a 1.1d someday. I'll do some tests on my setup with slowing down the network by "external" ( m2lagfix 2.0? :) ) - as I found the offset for the audio rate, I should be able to fix any stuttering that a slight slowdown would introduce. |
| Navigation |
| Message Index |
| Next page |
| Previous page |