I fixed Communication error

[Riddick]

Lads.. I did it.

I am (was) a victim of random communication errors during battles. I solved it.

The solution for me was downgrading Win11 from 24H2 to 23H2.

The 24H2 release got barely before DBSZ and seems like Bandai didn't take this into account, and literally Windows itself screwed the game over.

I did it all, like BIOS update, reinstalling Windows (24H2), Ethernet, DNS setting up, port-forwaring.. nothing worked till I went back to 23H2.

I played roughly 50 online matches without a single interruption since then.

[RangeHIT]

i can't play online i try everything
bios
... etc

[Riddick]

What's your Windows version?

Originally posted by RangeHIT:

i can't play online i try everything
bios
... etc

[RangeHIT]

Originally posted by Riddick:

What's your Windows version?

Originally posted by RangeHIT:

i can't play online i try everything
bios
... etc

Win 11 32h2
22631.4249

[MasterVanCaster]

I have windows 11 23h2, still don't work

[Riddick]

Well, all I could recommend is do a PC format? You should check your winver.exe and show us the version you are on of your OS.

As I've said, I did it all. BIOS update (which I knew from the beginning was pointless), port-forwarded Steam ports (if you forwarded 80 & 443 you are an idiot), did all the possible fixes I could.. and it was 24H2 itself.

If you haven't noticed, the 24H2 implements new changes in regards of networking in Windows (for example, it prompts you every time now when an APP wants to access you network etc.) There must have been changes that Microsoft did, and Sparking! Zero got release, and some of us updated our operating systems.

It isn't Bandai's fault tbf, but it is their fault for not releasing a fix after 8 days (since Early Access). It's unacceptable.

[Riddick]

OTOH, I am wondering still why Nvidia hasn't release a Game Ready Driver for Sparking! Zero, and the game itself is not even recognized by the Nvidia App (nor the Geforce Experience).

That's strange too.

[Roland]

Originally posted by Riddick:

OTOH, I am wondering still why Nvidia hasn't release a Game Ready Driver for Sparking! Zero, and the game itself is not even recognized by the Nvidia App (nor the Geforce Experience).

That's strange too.

No it's not, lots of games are like that. EDF 5 and 6 are great examples.

And you didn't fix anything, you've just been lucky so far.

For starters, if Windows had anything to do with it, you wouldn't see it happening on consoles as well.

And people have had the issues on 23H2 and 22H2. (and if you're wondering what people are still doing on 22H2 2 years later, me too, but that's another conversation)

There isn't ♥♥♥♥ the user can do except send support tickets to Bamco until they fix it.

Don't feel too bad for falling for a placebo though; one guy thought he fixed it by updating his bios, which makes no ♥♥♥♥♥♥♥ sense at all since everyone has different motherboards at different update statuses.

Judging by the fact that it often coincides with people joining and leaving lobbies (at least in casuals) it appears to be some kind of packet handling issue. In the one lobby last night I was able to make the comm error happen every single time I used Fierce Combination on this GT Goku player, then he changed characters and it was fine and we were able to finish our match. It felt sus af for a bit, like they were lag switchin or something, until they switched characters and took the loss without it happening.

[Riddick]

Originally posted by Roland:

Originally posted by Riddick:

OTOH, I am wondering still why Nvidia hasn't release a Game Ready Driver for Sparking! Zero, and the game itself is not even recognized by the Nvidia App (nor the Geforce Experience).

That's strange too.

No it's not, lots of games are like that. EDF 5 and 6 are great examples.

And you didn't fix anything, you've just been lucky so far.

For starters, if Windows had anything to do with it, you wouldn't see it happening on consoles as well.

And people have had the issues on 23H2 and 22H2. (and if you're wondering what people are still doing on 22H2 2 years later, me too, but that's another conversation)

There isn't ♥♥♥♥ the user can do except send support tickets to Bamco until they fix it.

Don't feel too bad for falling for a placebo though; one guy thought he fixed it by updating his bios, which makes no ♥♥♥♥♥♥♥ sense at all since everyone has different motherboards at different update statuses.

Judging by the fact that it often coincides with people joining and leaving lobbies (at least in casuals) it appears to be some kind of packet handling issue. In the one lobby last night I was able to make the comm error happen every single time I used Fierce Combination on this GT Goku player, then he changed characters and it was fine and we were able to finish our match. It felt sus af for a bit, like they were lag switchin or something, until they switched characters and took the loss without it happening.

This is my reply to someone else, from the other topic who said pretty much the same "what about consoles then?"

I'm not talking about consoles. I am talking about PC game port.

I don't know the situation people are experiencing in their own home environment with their networking status. That would be the first troubleshooting idea that comes to my mind in regards of consoles (obviously, don't be an idiot and don't port-forward 80 & 443 ports). You could try as a console owner to port-forward Steam mandatory ports (which even Bandai themselves mentioned). I personally don't have any ports forwarded (the UPnP is OFF also).

My network is perfectly fine, I live on my own, so I don't have my sister next room streaming 8K video which eats up my bandwidth.

I knew from the beginning that issue must be either in the game itself or somewhere with my current set-up (because it's a P2P architecture). So I dig and dig, and said to myself that I recently updated to 24H2 (which had new networking protocols, Wifi 7 and stuff) which Microsoft could clearly affect Sparking! Zero game, cuz Bandai wasn't ready for it (they develop games on the latest, stable OS versions).

So, I went back to 23H2, and BAM, all of the sudden I run the game flawlessly.

[Riddick]

Obviously, 8 days later (since Early Access) Bandai not acknowledging the issue is unacceptable.

[Roland]

Originally posted by Riddick:

Well, all I could recommend is do a PC format?

Jesus ♥♥♥♥ I hope no one listens to this.
-signed a guy who has been building and repairing Windows PCs for 23 years.

That will just be a painful waste of time and you will be enraged when you find out it fixed nothing.

OP stop giving PC advice if you don't know what you're doing please; you're literally just going to piss people off and waste their time. Like no disrespect, but it's obvious you don't know what your'e doing here.

[Riddick]

Originally posted by Roland:

Originally posted by Riddick:

Well, all I could recommend is do a PC format?

Jesus ♥♥♥♥ I hope no one listens to this.
-signed a guy who has been building and repairing Windows PCs for 23 years.

That will just be a painful waste of time and you will be enraged when you find out it fixed nothing.

OP stop giving PC advice if you don't know what you're doing please; you're literally just going to piss people off and waste their time. Like no disrespect, but it's obvious you don't know what your'e doing here.

Literally did a test today, and yesterday with different operating systems (Win11 24H2 and 23H2) and 23H2 doesn't cause comm issues.

If your 23 years old experience doesn't tell you to try it on VM, then you should go back and learn some more.

We don't have knowledge access to what happened to Win11 24H2 itself, but I can assure you that the latest changes (like Wifi 7 support, enhanced privacy controls etc.) could easily affect a game, that came out in the same week as the OS release.

Waste some time for some actual tests and come back later, cuz I did. If you won't be able to find Win11 23H2 x64 EN *.iso file easily, then contact me, I'll send it to you (cuz MS official website releases latest iterations of OS' only)

[Riddick]

Oh, just another source for people getting their communication error fixed:

https://www.reddit.com/r/SparkingZero/comments/1g2p412/fix_communication_error_disconnection_mid_match/

And just FYI, it is obvious that Bandai should address the issue with 24H2, but it takes long, so it's better than nothing at this point.

[Roland]

Originally posted by Riddick:

Originally posted by Roland:

No it's not, lots of games are like that. EDF 5 and 6 are great examples.

And you didn't fix anything, you've just been lucky so far.

For starters, if Windows had anything to do with it, you wouldn't see it happening on consoles as well.

And people have had the issues on 23H2 and 22H2. (and if you're wondering what people are still doing on 22H2 2 years later, me too, but that's another conversation)

There isn't ♥♥♥♥ the user can do except send support tickets to Bamco until they fix it.

Don't feel too bad for falling for a placebo though; one guy thought he fixed it by updating his bios, which makes no ♥♥♥♥♥♥♥ sense at all since everyone has different motherboards at different update statuses.

Judging by the fact that it often coincides with people joining and leaving lobbies (at least in casuals) it appears to be some kind of packet handling issue. In the one lobby last night I was able to make the comm error happen every single time I used Fierce Combination on this GT Goku player, then he changed characters and it was fine and we were able to finish our match. It felt sus af for a bit, like they were lag switchin or something, until they switched characters and took the loss without it happening.

This is my reply to someone else, from the other topic who said pretty much the same "what about consoles then?"

I'm not talking about consoles. I am talking about PC game port.

I don't know the situation people are experiencing in their own home environment with their networking status. That would be the first troubleshooting idea that comes to my mind in regards of consoles (obviously, don't be an idiot and don't port-forward 80 & 443 ports). You could try as a console owner to port-forward Steam mandatory ports (which even Bandai themselves mentioned). I personally don't have any ports forwarded (the UPnP is OFF also).

My network is perfectly fine, I live on my own, so I don't have my sister next room streaming 8K video which eats up my bandwidth.

I knew from the beginning that issue must be either in the game itself or somewhere with my current set-up (because it's a P2P architecture). So I dig and dig, and said to myself that I recently updated to 24H2 (which had new networking protocols, Wifi 7 and stuff) which Microsoft could clearly affect Sparking! Zero game, cuz Bandai wasn't ready for it (they develop games on the latest, stable OS versions).

So, I went back to 23H2, and BAM, all of the sudden I run the game flawlessly.

Dawg for starters, Xbox runs on a modified version of WIndows 10. This is part of why people say consoles are basically locked down PCs these days.

You're right you're not talking about consoles, YOU'RE TALKING ABOUT THE GAME WHICH IS THE COMMON DENOMINATOR.

And again, you have people in this thread telling you they are on 23H2 and it still happens, just accept you were wrong and move on with your life. I'm not going to sit here and argue with someone who clearly doesn't know what they are talking about

To further expound you don't know what you are doing; you almost never need to format a ♥♥♥♥♥♥♥ PC. You've got DISM, SFC, and Windows Reset feature, all to avoid that exact scenario. Stop giving bad PC advice if you don't know wtf you are doing, you're just going to make people waste their time and get angrier.

[BluntWrap]

Originally posted by Roland:

Originally posted by Riddick:

Well, all I could recommend is do a PC format?

Jesus ♥♥♥♥ I hope no one listens to this.
-signed a guy who has been building and repairing Windows PCs for 23 years.

That will just be a painful waste of time and you will be enraged when you find out it fixed nothing.

OP stop giving PC advice if you don't know what you're doing please; you're literally just going to piss people off and waste their time. Like no disrespect, but it's obvious you don't know what your'e doing here.

I been trying to tell him home cooked dont work.

[Roland]

Originally posted by BluntWrap:

Originally posted by Roland:

Jesus ♥♥♥♥ I hope no one listens to this.
-signed a guy who has been building and repairing Windows PCs for 23 years.

That will just be a painful waste of time and you will be enraged when you find out it fixed nothing.

OP stop giving PC advice if you don't know what you're doing please; you're literally just going to piss people off and waste their time. Like no disrespect, but it's obvious you don't know what your'e doing here.

I been trying to tell him home cooked dont work.

Exactly. Everyone needs to be sending support tickets to Bamco, not wasting their time on ♥♥♥♥ that won't make Bamco fix the real problem. (which I seriously suspect is some kind of packet handling issue)