Clients may not run ahead of the host - when they receive a frame from the host, they know how much they need to catch up, when to start actually receiving that frame, and in the case of a CMD frame, how long they can run ahead before waiting for another frame. It is actually fairly simple: each frame that is sent has a timestamp attached to it, that is used to keep things in sync. Since version 0.9.5, melonDS uses a synchronization mechanism to ensure this works smoothly. However, the CMD frame and subsequent reply frames use the 802.11 duration field to reserve the needed timeslot for the entire CMD exchange, so that everything can be pretty tight. In a real world setting, you'll want to ensure your wifi channel isn't being used before sending stuff, so that's what the delay is. The CMD frame isn't sent immediately, there is always a variable delay before. I've been experimenting, but for now, nothing really conclusive came out of it.īasically, if you remember your local multiplayer 101, this is how it goes: In the previous post, I mentioned I had an idea to optimize LLE wifi. I'll have to give this a try.Ĥ comments (last by HeroMa圜ry) | Post a comment It may even possible to build something robust around enet. We're also thinking of bringing back LAN, but as a proper LAN mode instead of just tossing packets around the network. I have a bit of an idea what's going on, but I'll need to work on it more.
I'm also trying to fix some other problems, namely how in some games you can't connect more than two players. We still have to see how this goes - we might have to make it optional if it causes problems somewhere. I had to do a few tweaks to get it reliable in certain situations, but so far it gives quite a substantial speed boost and doesn't seem to impact reliability. The only exception to this is when the host sends a beacon frame, but since these are sent at a fixed interval, it's not hard to take them into account. When the host sends a CMD frame, generally there won't be anything else being sent (other than replies and ack) until the end of the CMD_COUNT window, unless some clients failed to reply. The basic idea is that games send multiplayer data at a generally steady rate and the timings are predictable.
I've been thinking about the problem and making another experiment, which seems more successful. If you're running into trouble: Howto/FAQ
0 kommentar(er)
