Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
So as a self-described "network guru" etc, etc - can you outline precisely in which situations this will cause a problem?
Would they best be described as "completely conjectural, hypothetical, and without any real precedent or reason to believe they will crop up"?
Who said the issue was with "bottle-necking"?
I already pointed out that if the issue was mere packet-loss, latency, or excessive bandwidth consumption (unlikely on a 30 megabit private connection which is nowhere close to full utilisation) it would've been measurable via diagnostics.
Well, I'm all ears if you can explain what sort of router problem would manifest in poor hitreg; but no mearuable latency, packetloss, packet-shaping or exhaustion of bandwidth; ditto for internet connection problem.
Also why this problem would coincide with an upgrade to Windows 10, despite the router being identical and there being no measurable change to my ISP's service over the same period; and coincidentally resolve itself after making the above changes.
Frivolous? Quite possibly. It may be a placebo (one that immediately and directly coincided with a quantifiable and recorded 10% increase in my Sniping accuracy in Overwatch profile's statistics). How would one tell without getting a sizeable control group and measuring their responses?
May make your network conditions worse? Eh, that's also a possibility; but one that also applies to misconfiguring your router's QOS if its interface is less-than-clear, or even just trying out different drivers for your network adaptor.
But again, if it has made my network conditions worse, it hasn't done so in a way that has increased my ping to any given server, hasn't caused any sort of packet loss, hasn't impacted my bandwidth throughput on speedtest.net, or had any impact on my ability to stream or receive streaming data - or on my in-game accuracy.
And this after three months of it being configured thus. What issues do you expect to crop up that can't be fixed by simply going into safemode and using a command prompt to reset the Win10 default congestion manager; or simply replacing the registery key in question with any value of your choosing?
And if you don't, as per my situation and thus this topic?
What if your "hitbox registration wierdness" (which includes video-documented evidence of 20ms latency, 0% PL network conditions, and easy perfectly aligned headshots missing immobile targets) directly corresponds to upgrading to Windows 10; and - apparently - was only resolved immediately following the above fix?
Or a bad one if, as you concede, the change is merely benign but frivolous.
Eh, we're not using Macs - flirting with disaster is what recreational PC use is all about. Might as well ♥♥♥♥ your pants every time someone suggests overclocking as a way to improve frame-rates.
want to learn more about qos?
http://www.tldp.org/HOWTO/Traffic-Control-HOWTO/
also see
http://www.netfilter.org/
for more about packets and how they work.
what you are failing to realize is that messing with settings that you dont know what they do specifically is a dumb idea in general. furthermore editting your registry without registry experience (ie msce classes and or classes that deal with registry editting) or knowing specifically what you are doing is a TERRIBLE idea. furthermore than that repropagating things like settings tampering and registry editting without you yourself knowing specifically what they do and claiming them as a "fix" is a complete disservice to the board.
The settings enable chimney offload, whose functionality is described here:
https://support.microsoft.com/en-gb/kb/951037
And set the congestion manager to be handled via the CTCP algorithm, whose purpose is described here:
https://www.microsoft.com/en-us/research/project/the-compound-tcp-for-high-speed-and-long-distance-networks/
And I learnt far more "messing around with settings that I don't know what they do specifically" over the last 30 years of using computers than I did for the two years of formal academic study in computing. Because after "messing around with them" I then discovered what they did or did not do.
If all I did was sit on my hands in paranoid doubt, I'd've learned precisely nothing.
If I'd spent the time going through the brain-dead Microsoft Certification process; I'd be the one having to ask my MSCE acquaintances for advice, instead of the one they turn to when their "microsoft certified" procedures come up blank.
The registery fix in question actually originated on Microsoft.com as it happens; although admittedly not from anyone whose credentials could be confirmed.
However, registery editing is trivial to anyone with a degree of common sense; and I'm surprised anyone who thinks they are a "linux guru" would find it to be even remotely daunting - given how much root-access faffing around in terminal even the most user-friendly distros require in order to maintain even basic functionality.
Well thank ♥♥♥♥ the board police are here to teach their granny how to suck eggs...
either way reading about what something is rather than just flipping switches is much better and not subjective to some dunning krueger suffering pleb's subjective opinion.
sorry i still say to NOT do this and am now unsubscribing from this futile debate.
but fwiw windows 10 adds a ♥♥♥♥ ton of call home packets, unless you turn them off. also csgo constantly and by constantly i mean every second it is open is broadcast requesting for listening servers to connect to. there are a ♥♥♥♥ ton of background network packets that go on, and many ways to control them. learn a little about the simpler networks like that before you go all netsh modify settings and parsing code to the registry, and dear god dont post that ♥♥♥♥ on the board for people who for sure dont understand it (forgoing your made up or not understanding of things) to go and try it
This coming from the "guru" who's brought nothing to the table apart from paranoia, idle speculation, and a lot of pretention.
Oh, and an arbitrary link to a particularly unhelpful Linux-orientated guide to QOS scheduling.
Did *I* say the issue was 'buffer-bloat' or lag? I specifically said that the issue had nothing to do with ping, and thus the factor that most people would describe as "lag".
I'm curious as to how someone would get Microsoft certification if they can't even read; although not THAT sceptical, because most MSCE people I've had to work with neither listen to the problem at hand - nor have the deductive reasoning to analyse a problem that isn't one commonly found on the flow-chart-solutions they're spoonfed.
Not in the field of computing, where pretty much everything you might learn in an academic setting is obsolete from the get-go.
As a "programming guru", I'm surprised you've not found yourself at least once being formally taught a language that was on the way out, if not completely moribund, by the time the course rolls around.
Even when it comes to *routers* you're so insistent people piss about with, I've had some with half-assed Engrish firmwares that have accidentally inverted what their tickboxes do! Trial-and-error would've been the only way of correcting the misconception that "reading about it" would have caused.
This is ignoring the fact that most software is poorly (misleadingly if not downright incorrectly) documented, and often glitchy or counter-intuitive.
Boo-hoo...
You assume that these possibilities haven't been discounted...
But thanks for avoiding any opportunity to be helpful - by providing a step-by-step user-friendly method for diagnosing this as a cause and politely suggesting people eliminate that as a possibility*before* moving onto other options.
You think I "made up" the links I provided from Microsoft.com? Surely that would require I have at least some form of authority conferred by MS?
And if someone had posted the above to the board themselves, it would've saved me a modest amount of time pissing about with all manner of other diagnostics and solutions and drawing a blank before I hit on something that (coincidentally or not) has fixed the issue I was having.
But congrats on being a ♥♥♥♥ for several days in a row, thereby ensuring that a topic archived for posterity so that anyone doing a deep-search for the issue might get some inspiration, is floating at the top of the board again.
http://steamcommunity.com/app/730/discussions/0/359547436751656858/#c359547436754157183
Guys if you are having the error The specified file is not a registry script.You can only import binary registry files from within the registry editor you have to add ' Windows Registry Editor Version 5.00 ' without quotes to the very top of the registry file, for example i will use the reg script our friend here made
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Nsi\{eb004a03-9b1a-11d4-9123-0050047759bc}\0]
"0200"=hex:00,00,00,00,01,00,00,07,00,00,00,00,00,00,00,00,1e,00,00,00,00,00,\
00,00,00,00,00,00,02,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,ff,\
00,ff,00,ff,ff,00,00,00,00,00,00,00,00,ff,ff,ff,ff,00,00,00,00,00,00,00,00,\
ff,ff,00,00,ff,ff,ff,ff,00,00,00,00,00,00,00,00
"1700"=hex:00,00,00,00,01,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,\
00,00,00,00,00,00,02,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,\
00,ff,00,ff,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,\
ff,00,00,00,ff,ff,ff,ff,00,00,00,00,00,00,00,00