A wall jump is not a jump with a wall next to it. It is a two-part action: the character pushes against a vertical surface, then launches away from it. The push is effort. The launch is direction. A sound that only covers one of those parts leaves the player without half the information.
The failure is easy to hear in playtests. A wall jump that only has the launch sounds floaty, because the character appears to leave the wall without having contacted it. A wall jump that only has the impact sounds stuck, because the character hits the wall but the escape is silent. The fix is not a louder single sound. It is two events, designed separately, layered with a short offset.
Split the Event: Impact First, Whoosh Second
The clearest documented example of a wall jump sound comes from an FMOD Studio project’s audio documentation. The wall jump Event is described as a variation of the jump Event, with an added track carrying a sound that starts before the jump sound. The stated purpose is to give the impression that “the avatar leans on the wall before jumping.” A second track adds a flanger so the two sounds harmonise[reference:0].
That structure is the whole design in miniature. The pre-jump sound is the impact — the push against the wall. The jump sound that follows is the launch — the movement away. The offset between them is short, on the order of a few tens of milliseconds, but it is enough for the ear to hear two events in sequence rather than one blended event.
A separate game’s audio requirements describe the wall jump as a “distinct thud impact sound” [reference:1]. That is the impact half, isolated. It is useful as a reference for what the push should sound like: short, low-mid, and percussive, with the character’s weight behind it. It is not useful as the whole wall jump, because it says nothing about the direction of the escape.
The jump and landing guide covers the standard jump as a single event; the wall jump case adds that the event is composite, and the two halves have different jobs.
Direction: The Whoosh Has to Point Away From the Wall
Direction is the harder half to get right, because it is not carried by pitch or by impact. It is carried by panning and by the spectral shape of the whoosh.
A documented complaint about a wall jump sound in a multiplayer parkour game describes the failure precisely. The wall jump sound consisted of an impact and a short whoosh. After an update, an additional whoosh was added that played late and “sounds louder in the right channel than the left”. The complaint is that this right-panned whoosh plays after every wall jump, regardless of which wall the player jumped from[reference:2].
The problem is not that the whoosh is panned. The problem is that it is panned unconditionally. A wall jump from a wall on the left should pan the launch to the right; a wall jump from a wall on the right should pan it to the left. A fixed pan in one direction tells the player the wrong thing half the time, and after a few jumps the player learns to ignore the whoosh entirely.
The fix is to drive the pan from the wall normal — the direction perpendicular to the wall surface, pointing away from it. In a 2D platformer, that is usually a simple sign: if the wall is on the player’s left, the normal points right, and the whoosh pans right. If the wall is on the player’s right, the normal points left, and the whoosh pans left. The pan is not a stylistic choice; it is a readout of the physics.
A second directional cue is the whoosh’s spectral movement. A whoosh that sweeps upward reads as “launched”; a whoosh that sweeps downward reads as “falling.” For a wall jump, the whoosh should sweep upward, because the character is leaving the wall in an upward arc. A downward sweep would conflict with the visual, even if the pan is correct.
The mono or stereo export framework covers the channel-count decision; the wall jump case adds that the whoosh needs to be a pannable mono source, not a pre-panned stereo file, so the direction can be set at runtime.
Effort: Roughness and Impact Carry the Push
Effort is the other half. A wall jump is a physical action against a solid surface, and the sound has to feel like the character is doing work, not just changing direction.
The perceptual link between timbre and exertion is documented. A study on musical instrument sounds found that sounds produced with extended techniques received significantly higher ratings on “raspy/grainy/rough” and “perceived exertion”, even when the techniques did not actually require more physical effort to produce[reference:3]. The listeners heard roughness and inferred effort. That inference is available to a sound designer: a rougher, noisier impact will read as more effortful than a clean, tonal one.
The practical translation for a wall jump impact is a short burst of filtered noise layered with a low-mid thud. The noise provides the roughness; the thud provides the weight. A pure tone at the same level would read as a bounce, not a push. The noise does not have to be loud; it has to be textured, with enough high-frequency content to be heard as contact rather than as a hum.
The synthesizer guide covers noise shaping in a different context; the wall jump point is that the impact’s roughness is the effort cue, and it should be designed before the whoosh, because the whoosh is the easier half.
Timing: The Gap Between Impact and Whoosh Is the Whole Read
The offset between the impact and the whoosh is not a cosmetic detail. It is what makes the two events read as a sequence rather than a single sound.
The documented FMOD example places the impact sound before the jump sound, with the stated purpose of creating the impression of leaning on the wall first[reference:4]. The offset is not specified in milliseconds, but the perceptual constraint is: the impact must arrive early enough to be heard as a separate event, and late enough that it does not sound like a pre-delay.
A working range is 10–30 ms between the onset of the impact and the onset of the whoosh. At the short end, the two fuse into a single “crunched” event. At the long end, the impact starts to sound like a separate action that happened before the jump. The exact value depends on the impact’s decay: a shorter impact needs a shorter gap, because a longer gap leaves a hole between the two sounds.
The attack-time guide covers the perceptual thresholds for onset; the wall jump case adds that the gap is a designed silence, not a scheduling artifact.
A Starting Configuration for the Pair
The table below gives a first-pass configuration for the two layers. The values are starting points, not a specification, and they should be adjusted against the character’s weight and the game’s visual language.
| Layer | Role | Starting point |
|---|---|---|
| Impact | Effort; the push against the wall | Short filtered-noise burst (10–20 ms attack) layered with a low-mid thud; duration 40–80 ms; mono, centred |
| Whoosh | Direction; the launch away from the wall | Upward-sweeping filtered noise; duration 80–150 ms; mono source, panned at runtime from the wall normal |
| Gap | Separates the two events | 10–30 ms between impact onset and whoosh onset |
The impact and whoosh can be authored as two separate files or as two layers inside one middleware Event. The separate files are easier to pan independently; the single Event is easier to keep in sync. The FMOD example uses a single Event with multiple tracks[reference:5], which is the more compact option when the middleware supports per-track panning.
What to Check in Play, Not in Solo
A wall jump is heard in motion, often in a sequence of jumps along a vertical surface. The checks that matter are the ones that catch a failure in that context.
- Jump from a left wall, then a right wall, without looking at the character. If you cannot tell which side you launched from by the sound alone, the pan is not following the wall normal.
- Chain three wall jumps in quick succession. If the sounds fuse into a continuous noise, the gap is too short or the whoosh is too long.
- Jump from a wall while the character is moving slowly. If the impact sounds disproportionately heavy for the speed, the effort cue is fixed rather than scaled. The impact can be volume-scaled or pitch-scaled with the character’s approach speed, so a slow push sounds lighter than a fast one.
- Mute the whoosh and listen to the impact alone. If the impact sounds like a bounce rather than a push, it is too tonal. If it sounds like a click, it is too short. The impact has to have enough noise and enough low-mid body to read as contact with a solid surface.
The context auditioning guide covers the general principle that solo listening is unreliable; the wall jump case adds that the direction cue is only testable when the player is actually moving between two walls.