Those reimplementations may be better for your application - it's up to you to decide and do the analysis - but it's time not well-spent, IMO. Use UDP if you want, but you're going to end up reimplementing pieces/parts of TCP like Tepples said. TCP selective acknowledgement (SACK) per RFC 2018 further extends this in the case of packet loss. The 'use UDP because it's fast' mentality is only applicable in one scenario, and that's the handshaking nature of the protocol - which for large payloads isn't even used any more given how the TCP sliding window algorithm works (RFC 1323): you no longer need to send an ACK for every single packet). And for sake of example, WoW and many other modern games use TCP. Tepples wrote:By the time you've implemented reliable delivery of input packets over UDP, with error detection and retransmission and the like, you'll end up having reimplemented most of TCP. If it hasn't arrived emulation freezes until it does On current frame check get own input from buffer and check to make sure input from other player has arrived.

Save own input to buffer for local machineĦ. Frame to execute = current frame + delayĥ. Send input every frame with the frame it is to execute on. Ignore first X frames where X = frame delay since you can't possibly have any input from the other player.Ĥ. Synchronize emulator startup/loading of romģ. Determine number of frames to delay input (typically half the ping rounded up to the nearest integer or +1 frame for margin) on local machine by measuring average ping time over a time interval.Ģ. Especially if more than a few frames have gone by.ġ. Please disregard the ignorance, if I talked nonsense, good emulation to everyone.Typically you want to use UDP as your method for sending packets for these reasons.Īlso most NES games aren't set up to take advantage of prediction since re-emulating the frame really isn't an option in a some games. I think whoever uses old so Kaillera have in mind harm and not play online. If someone can demonstrate video, the problems of using the old customers, to be a reference point to use the 2011. I have gone through several problems with my home server, where people come and drop with old Kaillera unfortunately here there is a help towards emulate and have fun, the owners of the other servers do not help and are knocking your, I would play my Nestopia, it's hard to find people like to emulate it. 'Just like old versions would be banned.' it would be interesting to a filter line in * access.cfg to allow or block Kaillera versions to connect to the server. I ask friends understood if the customer Kaillera 2011 is the best error-free version and recommended for use, and it's okay to use different versions of the client for a match online. I hope I'm not breaking the rules by posting this in this thread but this is the thread that I originally came across when googling my problems. Everyone in our GE group has done clean mupen installs just to see if it was something wrong on our end but to no avail. I REALLY like the new emulinker servers, I just never have any luck with Mupen64++ on them most of the time.

IT was literally one of the few times in the past 6 years when we have had absolutely PERFECT lag-free games of 4 player Goldeneye, Marioparty, and Mariogolf. The few times we were able to play at Demoncat Server on the EMX v1.2, it was smooth as butter and I miss that feeling. It works, but I have no commands and there is more lag and delay. When I host kaillerasvr v.86, we have zero problems whatsoever, its just.I hate using that old server. When I hosted the EMX v1.2, we had slightly more luck but still had DS issues.

When I hosted an EMX v2.0.2, we instantly DS'd.

I have also tried all the above via hosting different version of the servers and we had the same results. We took our game to a v.86 server and everything works perfect (except slightly more delay and lag BUT no desync problems). Now that the new EMX 2.0.2 is out, we tried again at SmashFU and we got the same result, DS literally 10 seconds into the game. The question is, why does Mupen (in my my experience anyways) always desync on EmulinkerSF and EMXv1.2 and up? There is one exception though- Demoncat tribe server was running the EMX 1.2 and we were able to play flawlessly on Mupen64++ there (until the 18 min cutoff lol) but at the same time, Smash FU/Galaxy/etc was also on EMX 1.2 and we would always desync right off the bat there. I use this emu because my friends and I play Goldeneye mostly. Really great work on V2.0.2! I am not sure if this is the forum for this, but I have a question that has been bugging me for years:

Kaillera client nestopia ue