Cross play OFF for PC players / we know it's possible!!!

1. “If the console hop caused it, PS-only and Xbox-only would have the same issues.”

No, that’s not how routing works.
PS-only players all use the same routing path, so the server sees consistent packet timing from everyone.
Crossplay mixes direct PC routes with PSN/XBL While I have no idea how an XBOX user feels, I do know it's better without consoles on PC.

2. “A small authentication hop can’t create unpredictable in-match desync.”

It can when that “small hop” decides your relay path, NAT behavior, packet encapsulation, and transit provider before you ever hit EA’s server.
PSN and XBL do not simply “verify the session” — they impose the entire connection method.
If your initial path forces relayed UDP or bad NAT traversal, you get jitter and packet reshaping.
Jitter = desync.
You're oversimplifying something you don’t understand.

3. “PC-only lobbies don’t prove anything.”

Yes, they do, they isolate the variable.
Remove PSN/XBL routing and suddenly hit-reg and desync improve across the board.
If disabling the console routing layer instantly improves gameplay, then guess what the cause is?
Hint: not the players.

4. “You’re mixing up pre-game routing with in-game netcode.”

No. You are.
The routing path negotiated during the handshake doesn’t vanish when the match loads.
That route persists for the entire session.
Platforms don’t renegotiate fresh network paths at round start, that would  probably drop the connection.
If the handshake forces a garbage path, you’re stuck with a garbage path the whole match.
The platform handshake absolutely affects the gameplay loop because it defines the path your packets take during gameplay.

Also, as you can see ppl dont want to play with low skill aim assist players, but that's another story. We should ask for input based lobbies since controller with AA can be aslo used on PC, thing I'm sure EA wont bother to implement.

“If the console hop caused it, PS-only and Xbox-only would have the same issues.”

No, that’s not how routing works.
PS-only players all use the same routing path, so the server sees consistent packet timing from everyone.
Crossplay mixes direct PC routes with PSN/XBL While I have no idea how an XBOX user feels, I do know it's better without consoles on PC.

“A small authentication hop can’t create unpredictable in-match desync.”

It can when that “small hop” decides your relay path, NAT behavior, packet encapsulation, and transit provider before you ever hit EA’s server.
PSN and XBL do not simply “verify the session” — they impose the entire connection method.
If your initial path forces relayed UDP or bad NAT traversal, you get jitter and packet reshaping.
Jitter = desync.
You're oversimplifying something you don’t understand.

“PC-only lobbies don’t prove anything.”

Yes, they do, they isolate the variable.
Remove PSN/XBL routing and suddenly hit-reg and desync improve across the board.
If disabling the console routing layer instantly improves gameplay, then guess what the cause is?
Hint: not the players.

“You’re mixing up pre-game routing with in-game netcode.”

No. You are.
The routing path negotiated during the handshake doesn’t vanish when the match loads.
That route persists for the entire session.
Platforms don’t renegotiate fresh network paths at round start, that would  probably drop the connection.
If the handshake forces a garbage path, you’re stuck with a garbage path the whole match.
The platform handshake absolutely affects the gameplay loop because it defines the path your packets take during gameplay.

Also, as you can see ppl dont want to play with low skill aim assist players, but that's another story. We should ask for input based lobbies since controller with AA can be aslo used on PC, thing I'm sure EA wont bother to implement.

You’re repeating the same point but still jumping to the wrong conclusion from it. Yes the route negotiated during the handshake persists for the session. No one argued otherwise. The disagreement is about what that actually means.

A persistent route doesn’t mean the platform hop is the cause of in-match desync. Battlefield uses dedicated EA servers. Once the connection is established, gameplay packets travel directly between the client and the EA server. PSN and Xbox Live are not in the middle of the gameplay loop rewriting or shaping packets for a third-party dedicated-server title.

A persistent bad route can affect anyone, PC or console, depending on ISP quality, NAT setup, congestion or physical distance. That is just normal Internet routing, not “console routing” as a unique problem. And if your logic were correct, PS-only and Xbox-only matches would have the same extreme desync every game because those players all go through the same platform layer. They don’t. That already shows the platform hop isn’t the root cause.
And to be clear, I never said or implied the routing path “vanishes.” You added that yourself. My point was about what actually causes in-match desync, not whether the route persists, which it obviously does.

And again, the “PC-only is smoother” argument doesn’t prove anything because those lobbies are created through a config exploit. It isn’t a hidden feature or a tweak, it’s an unsupported file modification that forces the game into a matchmaking state EA never intended, and yes, that makes it a breach of their rules. Those lobbies also use a smaller population, different server assignment, different MMR distribution and bot fill. That doesn’t isolate a variable, it creates an abnormal environment and the side effects get mistaken as evidence.

For the input-based matchmaking and crossplay toggle part, I have already said in multiple posts across the forums that PC should have a proper crossplay toggle and input-based lobbies for all. I agree with that. It is just separate from blaming PSN or Xbox Live routing for severe in-match desync, which is not supported by how Battlefield’s server model or netcode work.

If you have something factual that disproves any of this I’m open to it, but the argument needs evidence, not assumptions or insults.

You keep repeating “PSN/XBL aren’t in the gameplay loop” as if that magically means their routing can’t affect gameplay. 
If the platform handshake sticks you on a relayed or restrictive route, you get jitter, packet arrival variance, and worse timing, and yes, that affects reconciliation on EA’s server.

And your own argument contradicts itself.
You said earlier that  “console-only players are reporting the same desync and hit-reg issues.” (read your 1st reply, your words not mine)
So clearly consoles ARE affected, yet now you suddenly claim PS-only/Xbox-only matches are magically fine, and that proves the platform layer isn’t involved.
You can’t have it both ways.

“Bad routes can happen to anyone” doesn’t refute anything — it actually reinforces the point.
PC connects directly to EA.
PS/Xbox connections go through platform-controlled traversal.
Mix those paths and you get inconsistent timing, I can have good games with consoles in the lobby and really terrible with bad hit reg. Turn off crossplay never had an issue.
Same-platform matches avoid that because they all follow the same routing profile. (talking mostly about PSN here, don't know about Xbox)
This is basic packet-timing logic, not a philosophy debate.

And stop pretending the crossplay config toggle “proves nothing.”
Flipping a value from 1 to 0 doesn’t alter physics, routing, or server code.
It simply removes the crossplay with consoles, and the game instantly feels smoother.
That is isolating a variable whether you like it or not. Also ppl have open tickets with EA support and it's OK to do it. Open one yourself and prove me wrong.

At this point you’re ignoring every technical fact and spamming walls of text to derail the thread.
It’s pointless debating you any further, so I’m done.
Please stop flooding the thread, you’re hijacking the original topic.

Hello :) Where  is the part I contradicted myself ?  I don't think I've contradicted  myself at all. You’re arguing against things I never said.
Saying console-only players also report desync doesn’t mean I claimed their matches are “magically fine” it means the issue isn’t caused only by mixing platforms. You added that part, not me.
I said the same problems occur even without crossplay, meaning the root cause is not crossplay routing.
And repeating that PSN/XBL aren’t in the gameplay loop isn’t “magic,” it’s literally how Battlefield’s dedicated servers work. You’re mixing handshake routing with in-match traffic.
So no there’s no contradiction on my end.

Hi, I'm 100% with you my friend and suggest to just ignore the iLuckyBrad. This dude just replying on every topic about crossplay on PC and keep saying that he want to see what will be the next thing that PC players will "cry". Like really, we are all talking about QoL option, and he is starting responding that (yeah yeah pc players need that) and then saying (problem is not in the crossplay - problem is cheaters, PC players, and other stuff, but crossplay off option won't change nothing).
And my thought about problem - someday (I hope) they will add crossplay off option, but I doubt it will be very soon, and by that time I'm personally will drop this game after completing 1st season battle pass. 

Console never wanted to play with PC and PC never wanted to play with Console. 

But they didn't listen. 

Pc users spend $1000,s on building a gaming pc and yet console players spend **bleep** all on a console then whine about how pc players cheat . Myself am tired of playing against console players and yet I am forced too. At the end of the day console players with their aim assist crap will turn pc players like myself away from EA . EA wakey wakey ... put the option to turn off crossplay on PC . The option that is not so called EA approved does not work . At first it did . Now as soon as I log in  the line GstGameplay.CrossPlayEnable 0 gets overridden and the same crap of been forced to play kids that cannot afford a pc is back  .  Good Bye EA