>>68995
>>69024
Clock syncing is exactly what they have done with the integrated mGBA though. Running a full clock sync locally over TCP wouldnt be that much different. Problem is the protocol itself is the same as it was half a decade ago, which the mGBA devs seemed to be planning to improve on. Clock syncing by itself does not solve any latency issues, what it does is prevent desyncs and link cable disconnects. But with the integrated mGBA solution you now have 5*4 points of failure where things can desync instead of 4 while also having much higher system requirements. I've no doubt it is smoother when it works though.
>comparing low bandwidth sync and latency issues to the abomination that is Stadia
Stadia has to recieve an input over the network and pipe that to a game, record video of the game, make a video encode small enough for streaming without looking like complete shit, transmit the video over the network and have that video decoded by the client before the player sees the result of a keypress.
mGBA/Dolphin over TCP would be mGBA gets input locally, mGBA sends data to Dolphin, mGBA recieves reply from Dolphin, player sees result. Barring desyncs and high latency, thats it. Not as fast as transmitting inputs one-way like normal Dolphin netplay, but nowhere near Stadia. If anything it's comparable to normal m