How high do you expect the playerbase to rise?

[KnucklesX2]

The patch supposedly “saved the game” after 98% of players quit.

[Zogtar]

Might see a small spike, but the network issues aren't any better. I don't think we'll see much of a jump with that in mind.

[Riddick]

Because they are not supporting very well the latest Windows OS iteration, it will lead to the same numbers IMHO. They must provide a fix for people that are struggling to play online. A fix for myself was going back to 23H2, and at this point I have 100h+ on this game..

Either way, we need three basic features IMHO:
- Rage Quitters Penalty
- Crossplay
- Fix for 24H2

(optional):
- Ki sickness


I have played today with the latest patch for like 3 hours I think. Dude, the Z-Vanish wars are gone. All of the sudden my connections with others are much better, without any lag. People can't cheese the game much anymore and you get to cancel the annoying After ImageStrike.

This game went up and feels fresh.

P.S
Obviously. It should be there since October. But let's face it realistically. The game had to launch, because of Daima. Not because they want to right now.

[Zogtar]

TBH, the 24h2 thing is likely more Microsoft's fault. The .net distributals are wonky.

You could "manually" fix it, but it's lengthy and you'd have to manually uninstall every distributal, then re-install new ones.

That being said, I hear it's a painful process, and I don't absolutely know if that would fix the issue. dark-breed could answer better, but I don't think he hangs out here.

[Riddick]

Originally posted by Judge Caveman:

TBH, the 24h2 thing is likely more Microsoft's fault. The .net distributals are wonky.

You could "manually" fix it, but it's lengthy and you'd have to manually uninstall every distributal, then re-install new ones.

That being said, I hear it's a painful process, and I don't absolutely know if that would fix the issue. dark-breed could answer better, but I don't think he hangs out here.

My best guess is the new Networking changes MS done in 24H2. The .NET packages itself I doubt are the reason here.. as I was saying since 8th of October. The game came out right after 24H2 dropped and this caused issues, cuz Bamco wasn't prepared for such a update from MS.

[Zogtar]

Originally posted by Riddick:

Originally posted by Judge Caveman:

TBH, the 24h2 thing is likely more Microsoft's fault. The .net distributals are wonky.

You could "manually" fix it, but it's lengthy and you'd have to manually uninstall every distributal, then re-install new ones.

That being said, I hear it's a painful process, and I don't absolutely know if that would fix the issue. dark-breed could answer better, but I don't think he hangs out here.

My best guess is the new Networking changes MS done in 24H2. The .NET packages itself I doubt are the reason here.. as I was saying since 8th of October. The game came out right after 24H2 dropped and this caused issues, cuz Bamco wasn't prepared for such a update from MS.

Good points.

Honestly, even if the .net distributables "were part of" the issue on Windows 11, it still doesn't explain the issues W10 (myself) and Linux users are going through.

[KnucklesX2]

Not much effect,