Stop blaming your aim—your rhythm is being stolen. This guide breaks down smoke edges and flash blindness into three testable windows: visibility slope, perception time, and the overlap that decides who sees first.
The worst part of a duel isn't missing your shots—it's having your rhythm stolen. Smoke edges and flash blindness are exactly where "feel" lies to you: you think there's still half a body at the smoke edge, you think the white screen is over, and then the moment you raise your crosshair, the enemy is already in your face. No mysticism here—just breaking these two things into three testable, reviewable windows.
1. The Smoke Edge Is Not a Line—It's a Visibility Slope
The smoke sphere is a volume on the client, and its edge decays gradually—it's not a hard cut. When you peek from the smoke edge, the enemy's outline fades in: first a bit of shoulder, then the barrel, then the head. The problem is that the server's visibility check and what you see on screen aren't perfectly synced—your screen is interpolating, the server is sampling.
So the first rule of smoke-edge duels: don't use "I see him" as your fire signal—use "he definitely sees me." The former is always half a beat late. The practical approach: angle your body so only a vertical sliver shows, letting the enemy's visibility slope slide past you instead of you walking into his slope.
Second rule: don't stand still at the smoke edge. The volume smoke's edge has slight perspective distortion when you move; standing still actually makes your outline clearer. A small left-right wiggle makes the enemy's first pre-aim miss—cheaper than any counter-strafe.
2. White Screen Duration Is "Perceived Duration," Not "Blind Duration"
The flash's white screen is a fading overlay on the client, but your eyes recover the ability to recognize outlines later than the overlay fully disappears. That is, the "usable window" of the white screen is shorter than the blind duration on the panel—the brief moment when you can actually see your crosshair and enemy color blocks is the duel window.
This leads to two practical inferences. First, back-flashing isn't just "turn around and done"—the angle you turn determines where your first glance lands upon recovery; turning back immediately after back-flashing means aiming your blurriest frame at the most dangerous angle. Second, the flash thrower must calculate "the teammate's recovery curve," not "how many seconds the enemy was blinded." Your peek timing should be the middle of your teammate's visual recovery, not the instant of the flash pop.
Also, mouse micro-adjustments during white screen are almost useless because you're filling in the picture from memory. The correct action is to maintain crosshair height and make small pre-aims, not big flicks.
3. Stacking the Two Windows into Duel Rhythm
The real rhythm is: smoke edge creates "visibility asymmetry," flash creates "perception time difference," and stacking them gives you that half-second of gun raise.
A reviewable example: the attacker waits at the smoke edge for the flash, and after it pops, doesn't peek immediately but waits until the white screen fades enough to see color blocks. At that moment, the defender has just recovered from the white screen, his first glance is a vertical sliver at the smoke edge, and his pre-aim is still in the smoke. Your first shot doesn't need to be accurate—just earlier than his.
Conversely, the defender has math to do: when holding a smoke edge, don't put your crosshair inside the smoke—put it half a body outside, waiting for the enemy's visibility slope to slide out first. When the flash comes, turn away first, don't rush to turn back, wait until the overlay fades to the middle, then turn back, letting the enemy's peek timing collide with your recovery midpoint.
Closing
The common point: neither is an "instant"—both are "processes." Break the process into windows, and you'll know whether you were early or late. Next review, don't just look at who shot first—look at who "saw clearly" first.