How To: Gaming
THE HOW TO CO. — EDITION 10
How To: Gaming
THE HOW TO CO. — EDITION 10
Lag, crashes and missing frames all feel like bad luck. They are not. Every one of them has a cause with a name and a first move you can make tonight.
◆ HOW TO USE THIS PAGE
Read the left column and nothing else. Stop at the sentence that sounds like your night, then read across.
THE UNDERWORKS — THE MACHINE LEVEL BENEATH THE GATE
THE ONE RULE
Everyone in a bad mood does the opposite: six settings, a driver, a reinstall and a restart, all at once. Sometimes it works, and you have learned nothing, so you will be back here in a month doing all six again.
A fix you cannot name is not a fix. It is a coincidence with a good week.
What it feels like, what it actually is, and the first thing to try. Work down the left edge. The codes are there so you can tell somebody else which row you are on.
Everything here is about when your inputs arrive, not how pretty the picture is.
“Everyone snaps back to where they were a second ago.”
You are watching the server correct you. Your inputs landed late enough that it had already decided what happened without them.
Get off wireless before you touch anything else. A cable removes the single largest source of arrival-time jitter in most homes.
“It is fine all day and unplayable after dinner.”
Congestion, either inside your walls or on the street outside them. The line is shared, and you have chosen the busiest hour on it.
Find out what else is uploading. A backup, a sync or a download eats the same narrow lane your inputs are queued in.
“My ping number looks low but the game still feels late.”
The average is not what hurts. Variance is. Steady-and-slow feels playable; fast-but-erratic never does, because you cannot learn a timing that moves.
Stop reading the single figure and look for the spikes. You want a graph over a few minutes, not a number in a corner.
“Everyone in voice says I sound underwater.”
Voice is riding the same upstream as your inputs, and upstream is usually the thin half of a home connection.
Lower voice quality before you lower anything visual, and close whatever is uploading. Your microphone is competing with your own aim.
“One person in the group is always laggy and the rest of us are fine.”
The match is being hosted somewhere specific, and the distance to that somewhere is not the same for everybody in it.
Check which region the lobby actually picked before anyone starts changing settings. Half of these arguments end there.
A crash that happens the same way twice is the good kind. It can be cornered.
“It only dies in the same room, every time.”
Repeatable location means a specific thing is being loaded or drawn there. That is not a random fault, it is an address.
Change one graphics setting, walk back in, repeat. The setting that stops it tells you which subsystem is failing.
“It closes with no message at all.”
Silent exits usually mean the process was killed from outside rather than failing from inside: memory pressure, a driver reset, or heat.
Read the system log at the timestamp. The game did not write a note, but the operating system almost always did.
“It runs for an hour and then goes, never at the start.”
Time-to-failure is evidence. A long fuse points at something accumulating rather than something broken: heat, or memory that is never given back.
Watch temperature while you play. If it climbs to a ceiling and sits there just before the crash, you have a cooling problem, not a software one.
“It started the day after an update.”
Something moved underneath the game. The most recent change is the cheapest suspect to interrogate, and usually the guilty one.
Undo the single most recent change, not all of them at once. A fix you cannot attribute has taught you nothing for next time.
“It only crashes on launch. Once it is running it is perfect.”
Launch is when files get verified and when every overlay in the background injects itself. Startup crashes usually implicate the layer around the game.
Turn off every overlay, capture tool and companion app, launch clean, then add them back one at a time until it breaks again.
Smoothness and responsiveness are two different measurements. Most of this band is telling them apart.
“The picture stutters but the frame counter says it is fine.”
A healthy average is hiding brief stalls. What you feel is the worst frame in the second, and the counter is showing you the mean one.
Judge by the low end — the figure usually labelled one-percent low — and cap your frame rate under your worst sustained number so delivery is even.
“I turned the settings down and it got worse.”
Below a certain point you are giving away image quality for frames you already had. The bottleneck was never the part you were turning down.
Find which component is actually saturated before you touch a slider. If the graphics chip is sitting idle, no graphics setting will move anything.
“Smooth on my own, terrible the moment there is a crowd.”
Crowds are a processor problem, not a drawing problem. More things to simulate, not more pixels to paint.
Cut what the simulation has to track: view distance, crowd density, shadow-casting lights. Resolution will do nothing for you here.
“It was fine last month and nothing has changed.”
Almost nothing degrades on its own except dust, dried thermal paste and free disk space. A slow decline is usually physical.
Clean the intakes and check free space on the drive the game lives on before you blame a patch you did not read.
“It runs beautifully and the aim still feels heavy.”
A long render queue buys smoothness with delay. You are being shown more frames than you are being allowed to influence.
Shorten the queue — the option is usually named something like low-latency mode — and switch off post-processing that has to buffer a frame to work.
◆ IF TWO ROWS BOTH SOUND RIGHT, START WITH THE ONE HIGHER UP THE TABLE.
◆ WHEN THE TABLE RUNS OUT
Two hours down here and nothing has moved? Then it is not on your side of the wall. Some faults are somebody else’s to fix, and knowing that is a result too.
◆ DID IT WORK?
If you changed a setting and also changed where you were standing, you learned nothing. Same place, same route, same time of night.
An average is built to hide exactly the thing you are complaining about. Whatever tool you use, read the bottom of the range.
One good run is weather. A change only counts once it has survived a bad night, a full lobby and a busy hour.
◆ THREE PATHS OUT OF THE UNDERWORKS
Where your inputs go, what slows them down on the way, and how to prove which half of the journey is at fault.
ENTER →
Reading the note the machine left you. Logs, timestamps, and the discipline of changing one thing at a time.
ENTER →
Finding the part that is actually saturated, and the difference between a game that looks smooth and one that answers you.
ENTER →GUIDES BEING WRITTEN FOR THIS CHAPTER
“Nobody actually wants a diagnosis. They want it to stop. The trouble is that a fix you cannot name will not still be fixed next month.”