You answered your own question. MS and PS are just authentication handshakes, no different from steam. Client > server communication is the same for PC and console once its beyond the authentication handshake where steam/psn/xbl have no involvement anymore which means crossplay clearly has nothing to do with desync because desync is simply a packet loss where the server side has to use lag compensation to guess what the lost packet did similar to how rollback works in fighting games. The obvious difference is console players are more likely to be on wifi, which *gasp* means more jitter and more packet drops. I run across desync against PC users too and I guarantee its some dude on a laptop using wifi.
Desync is something every FPS game has to deal with. Back in the day it was rubber banding (and BF3 had horrible rubber banding issues, especially in metro). Today they just cut frames and calculate everything instantly to keep things running smoother. Would you rather go back to the rubber banding days or desync for lag compensation? Blaming it on crossplay is just ignorant.
It's not just wifi, it's also that consoles have slow CPU's and network stacks compared to PC's. I mean a console has a CPU comparable to a PC from 15 years ago, so any processing stumbles through the whole system manifests itself across the whole play session.
Cross-play is an idiotic idea for a first person shooter, especially when it's FORCED on PC players.
What are you on about? lmao.
Both the PS5 and Xbox rock 1gig NICs and both of them have custom SoC's based on Zen2 CPU's. No, they're not flagship CPU's, but they are not 15 year old chips. They're modern chips lol.
