Инсталирайте Steam
вход
|
език
Опростен китайски (简体中文)
Традиционен китайски (繁體中文)
Японски (日本語)
Корейски (한국어)
Тайландски (ไทย)
Чешки (Čeština)
Датски (Dansk)
Немски (Deutsch)
Английски (English)
Испански — Испания (Español — España)
Испански — Латинска Америка (Español — Latinoamérica)
Гръцки (Ελληνικά)
Френски (Français)
Италиански (Italiano)
Индонезийски (Bahasa Indonesia)
Унгарски (Magyar)
Холандски (Nederlands)
Норвежки (Norsk)
Полски (Polski)
Португалски (Português)
Бразилски португалски (Português — Brasil)
Румънски (Română)
Руски (Русский)
Финландски (Suomi)
Шведски (Svenska)
Турски (Türkçe)
Виетнамски (Tiếng Việt)
Украински (Українська)
Докладване на проблем с превода
I have monitored the connection of all of us to our Teamspeak Server and there nobody has packet loss and a ping of 16ms
-> This Problem is definitly stamming from the battlebit connection.
We also went from a switch to everybody being connected to the router directly
SOLUTION -> 2 of us are using a VPN now it works xD
If you use the term when talking lag and packet loss, you have no idea what you are saying.
My suspicion is that battlebit’s easy anti-cheat implementation doesn’t play nice with a NAT when other people are using the same applications.
Either way, although it’s not exactly a common problem, it’s severe.
Maybe port forwarding.
This is literally your own fault because the netcode isn't designed to receive 1 packet and send 1 packet to be split amongst 4 separate machines.
Most protocols aren't going to account for that. The reason why "it works" when one of you is on wifi is because that machine on wifi is its own machine that is sending and receiving its own data. the other 3 are still having to fight over effectively the same packet and cobble together a dodgy looking package of data to the main server
just because it's low quality doesn't mean you can just lan up on it, you probably do fine in games with far fewer players in a lobby but remember this game is literally about connecting HUNDREDS of people at a time.
your splitter simply can't handle the network data being sent which is why your fix works and one person getting onto wifi makes it run better, because you're lowering the amount of data being sent through the splitter.
but as MS-14 said the other 3 will still be fighting over the packets.
this is why you don't lan party on games that have massive network usage because you're going to overload your little CS router lol.
I also found a solution: VPN.
3 people on LAN the rest run a VPN. No issue. Just... It sucks we have to run VPN to LAN this.
it happens in lots of areas where certain ISPs have monopolies on service, xfinity is a great example of subpar service like this in areas where only they provide connections.
mainly, the reason a VPN works is because you're working around their shoddy network servers rather than trying to connect to them in your local area.
and yes, this varies based on games because the network you're connecting to has to have a strong connection to the games servers.
if your ISP doesn't provide one for said game that is stable like it would other games, that's on your ISP again, not the game itself.
they short on expenses like this in all companies honestly but the ones that have monopolies are often the ones that have the worst service in these terms.
Friday night is family game night with my 3 kids, so 4 pc's all on hard wired 10gb lan and 5gb symmetrical fiber outline. We can play forza horizon, fortnite, fall guys, zero issues. sub 50 ping in most games. Battlebit? ping is "fine" if you believe the server ping which some people dont. but packet loss is abundant and game microstutters often with rubber banding. never happens when playing on the network by myself. Usually pops up once 3 computers are playing battlebit.