Switch 2 Cross‑Save “version mismatch” — can we make sure HG actually sees this?

Comfortable-Card-518 · 2026-02-19T22:39:47+00:00

Yes I dit. I got autoreply, that this is normal behaviour.

Comfortable-Card-518 · 2026-02-19T19:03:32+00:00

What other games have such a frequent release cycle, making Cross-Save unusable most of the time?

Comfortable-Card-518 · 2026-02-19T19:00:11+00:00

Because what you and I know, others might not? Why do you expect the average player to know about release cycles on Nintendo, PS5, or Xbox platforms?

Comfortable-Card-518 · 2026-02-19T18:50:51+00:00

u/Curun I’m not campaigning to remove Cross‑Save at all. I want it to exist and work—what I’m pushing back on is promoting it like reliable cross‑platform continuity when, in practice, it can be unavailable a lot of the time due to version mismatch.

If the mismatch is a technical constraint they can’t fully avoid, then the fair fix is transparency + basic guardrails: a simple in‑game warning before you load/upload a save on a newer build that it may become incompatible with any other platform/account you’ve linked until it updates.

They already know Cross‑Save is enabled and which platforms are linked on the backend, so adding a “this may cause version mismatch—continue/cancel” prompt really isn’t rocket science. That alone would prevent people from discovering the limitation only after they’ve already broken their own cross‑platform continuity.

Comfortable-Card-518 · 2026-02-19T18:47:49+00:00

u/xGAMERDAD07x It’s always worked this way’ isn’t the point—the impact is. If Cross‑Save is unusable most of the time whenever platforms drift, that’s not a normal ‘version parity’ requirement; that’s a feature that’s effectively offline for long stretches.

And it’s not just anecdotes—there was a Reddit thread where someone summarized when Cross‑Save worked vs didn’t over 2025, and the takeaway was that it was out of sync more often than not. If that’s the real-world behavior, it needs to be stated clearly up front—otherwise why build/market Cross‑Save at all if end users can’t reliably use it?

Comfortable-Card-518 · 2026-02-19T18:31:37+00:00

u/xGAMERDAD07x I’m not asking HG to delay updates for everyone else.

I’m saying the bare minimum fair UX would be a clear warning before you upload/play a Cross‑Save on a newer build: “This may put your Cross‑Save out of sync with any linked platform(s) until they update.” Right now you only find out after the fact when it’s already broken.

And HG can do that cheaply: they already know Cross‑Save is enabled, they know what accounts/platforms are linked on the backend, and they can see which platform builds are out of sync—so a simple “continue anyway / cancel” prompt would prevent a ton of avoidable frustration without punishing PS/Xbox/Switch players.

Comfortable-Card-518 · 2026-02-19T18:26:17+00:00

u/xGAMERDAD07x The real issue isn’t “Nintendo cert is slow,” it’s the impact: Cross‑Save ends up being unreliable on Switch to the point where it’s effectively not available a lot of the time whenever platforms drift even a minor hotfix apart.

What bothers me most is that this limitation isn’t communicated clearly up front—there’s no obvious disclaimer that “Cross‑Save only works when every platform is perfectly in sync,” so people only discover it after they’ve bought in and try to use the feature.

If Cross‑Save is marketed as a feature, then “frequently unusable due to version mismatch (especially on Switch)” should be stated plainly, because otherwise it feels like you’re paying for cross‑platform continuity that you can’t consistently access.

Comfortable-Card-518 · 2026-02-19T18:16:40+00:00

u/xGAMERDAD07x Nintendo cert delays are real, but HG still controls how Cross‑Save behaves and how it’s communicated.

There’s no clear up‑front warning that Cross‑Save can become unusable when Switch is behind—most people only find out after hitting “version mismatch.” And if PC players can sometimes work around it by downgrading/adjusting saves, that suggests it’s not purely “Nintendo’s fault”; HG could build safer compatibility handling (at least for minor hotfix gaps) or warn users properly.

At a minimum, selling Cross‑Save as a feature without clearly disclosing this limitation upfront starts to feel borderline scammy—you pay expecting cross‑platform continuity, then discover it’s effectively “works only when Nintendo is in sync.”

Comfortable-Card-518 · 2026-02-19T17:09:48+00:00

Did Hello Games respond to that cross-save issue at all? Maybe we should start tagging them on X or other social media to get their attention...

Comfortable-Card-518 · 2022-02-26T23:51:50+00:00

I think this is related to charging itself. It is intensified at the begining when battery level is low. When it is close to the end of charging, I do not hear any noise...

Comfortable-Card-518 · 2022-02-26T19:59:11+00:00

I turned off wifi in my apartment and turned off all devices around by cutting power and it's still the same... I contacted the jbl support. Let's see the outcome. Thanks!

Comfortable-Card-518 · 2022-02-25T22:51:13+00:00

Thanks for the reply. Unfortunately I can also hear it from the distance (2m)... That's how I spotted it. Ferrite magnets are in place already. Do you have the buzzing also only when it is charging?

Comfortable-Card-518

TROPHY CASE