Quick answer: Drop the CinemachineImpulseListener Amplitude Gain to ~0.3, set the Impulse Source Distance Range so far events don’t shake the camera, and use Impulse Channels to keep cinematic cameras quiet during gameplay impacts.

Tap a button, the camera leaves the screen. Cinemachine Impulse’s defaults compound: source amplitude 1, listener gain 1, raw shake curve. The result is a 7-on-the-Richter shake from a footstep.

The Symptom

Camera shake fires off correctly but the magnitude is way more than intended. Or the same impulse shakes some cameras and not others when you wanted the opposite. Or the rumble bleeds into a cinematic capture.

What Causes This

Cinemachine Impulse has three configurable points:

  1. Impulse Source — emits the shake at an amplitude/duration.
  2. Distance falloff — reduces amplitude based on listener distance.
  3. Impulse Listener — on a vcam, multiplies received amplitude by Gain.

Defaults to all 1.0 means a unit-amplitude source produces a unit-amplitude shake at the listener. That’s the upper bound of what most games want; tune down.

The Fix

Step 1: Listener Amplitude Gain. Select the CinemachineCamera. Find CinemachineImpulseListener — if absent, add it. Drop Amplitude Gain to 0.3 (subtle) or 0.5 (medium).

CinemachineImpulseListener:
  Channel Mask:    Default
  Amplitude Gain:  0.3
  Frequency Gain:  1.0
  Use 2D Distance: true     // for top-down or 2D

Step 2: Source distance falloff.

CinemachineImpulseSource:
  Default Velocity: (0, 0, -1)
  Impulse Type:     Uniform
  Channel:          Default
  Amplitude:        1.0
  Frequency:        0.2
  Distance Range:   5 – 30
  Falloff Curve:    Smooth

Inside 5m: full amplitude. Past 30m: zero. Between: smooth falloff. An explosion at the edge of view doesn’t rock the camera.

Step 3: Channels for filtering. If your cinematic camera should not respond to gameplay impacts:

Trigger Source from Code

public class Punch : MonoBehaviour
{
    public CinemachineImpulseSource src;

    public void DoPunch()
    {
        src.GenerateImpulseWithVelocity(new Vector3(0, -1, 0) * 2f);
    }
}

The 2f multiplier lets you scale per-event without changing the asset defaults.

Verifying

Trigger the impulse in PIE. The shake should be felt but not cinematic. If it’s still over-the-top, lower listener gain. If you can’t feel it at all from a distance, raise Distance Range max.

Understanding the issue

This bug class falls into a pattern that's worth understanding beyond the specific case. In Unity Engine, the underlying behavior is shaped by how the engine layers its abstractions - the public API you call, the runtime systems that respond, and the platform-specific implementations underneath. A bug at any layer can produce symptoms that look like they originate at a different layer. Triaging effectively means recognizing which layer the symptom belongs to, even when the gameplay code is what's visible.

The specific bug described above is the kind that surfaces during integration rather than unit testing. It depends on a combination of factors: the asset configuration, the runtime state, the platform's specific behavior. In isolation, each piece looks correct; in combination, the bug emerges. This is why thorough integration testing - playing the actual game in realistic conditions - catches things that automated tests miss.

Why this happens

This bug class disproportionately affects late-stage development. The work to surface it is interactive testing in realistic conditions, which only really happens after the gameplay is in place and assets are populated. Catching it early requires deliberate testing of conditions that look unimportant.

At the engine level, the behavior comes from a deliberate design decision in Unity. The engine team chose a particular trade-off - usually performance versus convenience, or generality versus specificity - and that trade-off has consequences when you push against it. Understanding the trade-off is what turns 'this bug is mysterious' into 'this bug is the expected consequence of this design'.

Verifying the fix

After applying the fix, the verification step has three parts: confirm the original repro is resolved, confirm no obvious regressions in adjacent functionality, and (for shipping titles) deploy to a small player cohort first and watch the crash and report rates. Each step catches something the others miss.

Reproducibility is the prerequisite for verification. If you can't reliably reproduce the bug pre-fix, you can't reliably verify it post-fix. Spend time getting a clean reproduction before you write any fix code. The fix is fast once you understand the reproduction; the reproduction is the slow part.

Variations to watch for

Related bug classes often share the same root cause. If you find yourself fixing this issue, look for cousins: similar symptoms in adjacent systems, the same data flow but a different value, or the same fix pattern in another module. The catalog of 'we've seen this before' becomes valuable institutional knowledge.

Adjacent bugs often share a root cause. After fixing the case you've found, spend an hour searching the codebase for similar patterns. What's the same call with different arguments? The same data flow with a different entity type? The same lifecycle issue in a sibling system? Each match is a candidate for the same fix, or a related fix that prevents future bugs of the same class.

In production

In shipping builds, this issue may interact with other production-only behavior. Stripping, encryption, asset bundling, and platform-specific code paths can each modify the symptoms. When players report a related issue, capture build SHA, platform, and any feature flags - those three fields cover most of the production-only variations.

When triaging a similar issue in production, prioritize gathering data over hypothesizing causes. A player report describes a symptom; what you need is a build SHA, a session timestamp, and ideally a screen recording or session replay. With those, the bug becomes tractable. Without them, you're guessing at hypothetical reproductions that may not match what the player actually hit.

Performance considerations

Performance implications matter when this bug class scales with player count or asset count. A bug that fires once per session is annoying; a bug that fires once per frame compounds. After fixing, profile the affected code path under realistic load. The fix that's correct for one entity may be too slow for ten thousand.

Diagnostic approach

Diagnosing this class of bug benefits from a structured approach: confirm the symptom, isolate the variables, hypothesize the cause, and verify the hypothesis before writing fix code. Skipping the isolation step is the most common mistake; without it, fixes often address symptoms while the underlying cause continues to produce other variations.

For Unity-specific diagnostics, the editor's profiler is the canonical starting point. Capture a representative frame with the symptom present; compare against a frame without the symptom; the diff often points directly at the cause. If the symptom is non-deterministic, capture multiple frames and look for the pattern - the cause is usually a state transition or a specific input value rather than a continuous effect.

Tooling and ecosystem

Third-party plugins often provide better diagnostics for their own behavior than the engine does. If the affected code is in a plugin, check the plugin's documentation for debug modes, verbose logging, or inspector tools - these can save hours of investigation when they exist.

Within Unity, the relevant diagnostic surfaces include the standard frame debugger, memory profiler, and engine-specific debug overlays. Each one shows a different facet of what's happening. The frame debugger reveals draw call ordering and state transitions; the memory profiler shows allocation patterns; the debug overlay reveals per-system state. Bugs that resist one tool usually surrender to another - the trick is knowing which tool to reach for first.

Edge cases and pitfalls

Boundary conditions deserve specific testing attention. What happens when the input is zero, maximum, negative, or NaN? What happens at the start of a session vs hours in? What happens at the boundary between two systems handling the same data? These are where bugs hide and where regression tests are most valuable.

When writing a regression test for this fix, focus on the boundary conditions that surfaced the original bug. Tests that exercise the happy path catch obvious regressions; tests that exercise the boundary catch the subtler regressions that look like new bugs but are really the original returning. The latter are the tests that earn their keep over the long life of the project.

Team communication

Document the fix and its rationale in the commit message or attached engineering doc. Future engineers will encounter related issues; the rationale tells them whether your fix is reusable or specific to the case at hand. Without rationale, the fix gets reverted or copied incorrectly.

If this fix touches a system several engineers work in, a short writeup in the team's engineering channel helps. Not a full design doc - a paragraph explaining what was wrong, what's fixed, and what to watch for. Future engineers encountering similar symptoms will search for the fix; making it findable is a small investment that pays back later.

“Listener gain trims. Distance falloff localizes. Channels separate gameplay from cinematic. Shake feels right.”

Related Issues

For Cinemachine blends, see Cinemachine blend. For LookAt jumps, see LookAt jumps.

Listener gain. Distance range. Channels. Shake feels right.