Im saying crew lock shouldnt be a thing unless the player leaves right after (return to hangar), and to answer your question, i dont use cable because the rooter is too far from my laptop, though its only an issue when im on vacation.
Not saying it is, saying that getting disconnected because of your wifi should have lighter punishments, like if it wants to reconnect you, which is a thing but i rarely get the option when im on vacation(for no reason whatsoever).
Generally speaking, people can lack equipment like me when im on vacation… Not that easy to brawl when you dont have equipment for it, plus other people want to use their phones. Though thankfully im back home rn and being able to play.
Thing is you can’t actually determine the connection type and whether or not it’s intentionally ‘bad’ to let you pick and choose what to drop out on.
I don’t understand what you mean by this.
A cable can reach further than the wifi can so…
They already do. I’ve been able to rejoin a game after completely rebooting my PC and restarting WT.
WIFI is not the problem. The bandwidth requirements for WT isn’t that high. All you are transmitting is a bunch of telemetry numbers that is easy unless you are on an antique dialup connection. The only time WiFi is the problem is if you have a large demand on the local endpoint. Like you are trying to watch cat videos at the same time or you have a bunch of other people trying to on your router. And even then, a human can’t tell the difference between 50 and 150 ms. The connection has to drop out for literal seconds before the client will lose the beat and start flying tanks and crashing planes.
What kills ppl is ping rate, the time to send receive updates. Almost always (regardless of what some ppl think) somewhere else, either the ISP being sloppy, or Gaijin’s servers getting bogged down or having other issues. Or simply that your bits have to go half-way round the whirled and back. Any wifi connection will be faster than most ppl’s throughput all the way to the Snail.
I don’t think i’ve ever seen it. and i have had a few PC crashes, game crashes and disconnects over the past 2 years.
To actually force that to come up, all you need to do is close the WT process quick, and fire it back up and you’ll get that same prompt.
@kafros69 If anything, try a different wifi band (b/g/n), check the channel your wifi actually uses isn’t clogged by others, or even just change it anyway to see if other interference around you is causing it.
Move your accesspoint, and move your laptop to get a better signal.
Don’t game on the laptop whilst it’s not plugged in as windows will try and powermanage on you which will cut down on the wifi accuracy/strength to try and make the laptop last longer.
Whilst Exocetta is giving a whole heap of information about how wifi works, it’s not actually accurate, as it all boils down to the point that wifi isn’t a constant connection, and it does have issues which these are symptoms of.
IOW you don’t know how TCP/IP works. lol
TCP/IP has absolutely nothing to do with WIFI, and your stating that makes it clear you’re just trying to sound smart, and technobabble away to make out that it’s Gaijins issue…
Shut up.
Stop ur’ killin’ me.
No, you should stop. You did this in another thread which was talking about technical things, and the fact was you were wrong in that thread too, and you did the same…
Over complicating it, and making out you knew anything about networking in the slightest.
The connection method has absolute jack squat to do with the transport layer.
Ironic as always.
Stop trying to derail the thread.
Face it, you’re outclassed and my post showed a lot more info than your baseless and ignorant throwout.
And OFC someone is going to be able to pick up a ping difference between 50 and 150 ms… I know which server I’m playing on at all times, hence why I just set one set… It’s VERY noticible.
Ok Mr. Pot.
No seriously… If you don’t understand that the transport layer is different and irrelevant to the actual connection method, then you have no place to say you know anything about it…
U’r the one who brought that up. And it proves your opinion that WiFi is the root of all evil false. Its an insignificant difference compared to all other sources of latency.
Most household wifi routers cant do dual band nor priority packet queuing over the wifi resulting in significant outages in connection due to either disturbances or other users sending requests simultaneously.
So your previous explanation, however well formulated and “technically” correct; applies mostly to wired connections or high end routers with PQ or WFQ and other more advanced funcions. A majority of wifi users will actually have issues with their connection solely due to it being wireless.
Nope… I actually mentioned that whilst you’d given out a heap of information, it wasn’t accurate and later elaborated to it being technobabble, because all you’re doing is trying to sound like you know something, where you’re actually incorrect…
I’m a retired network technician, and I know my craft.
Hence why I always say gaming on wifi is a hard pass, and whilst there are ways to improve it, it’ll never be stable, as it’s based on packet radio methods and thus is prone to actually having trouble.
It proved nothing because it was clear you didn’t know networking vs the connection method, as TCP/IP has nothing to do with that connection.
Things have moved on from twisted pair ya’ know…