Introduction to Environmental Audio Occlusion and Obstruction

Game audio is a critical component of immersion, and realistic sound propagation can make or break a player’s sense of presence. Environmental audio occlusion and obstruction simulate how sound behaves when it encounters obstacles, adding depth and spatial awareness to gameplay. In FMOD, implementing these effects requires a combination of engine-level raycasting and FMOD’s built-in spatial audio features. This expanded guide walks through the theory, setup, and practical implementation of occlusion and obstruction using FMOD, providing actionable steps for both Unity and Unreal Engine workflows.

Properly executed, occlusion and obstruction allow players to locate enemies through walls, gauge the size of a space, and feel connected to the game world. Without them, audio feels flat and disconnected. By the end of this article, you’ll have a production-ready pipeline for adding environmental audio filtering to your FMOD-powered game.

Understanding Occlusion vs. Obstruction

Before diving into implementation, it’s essential to distinguish between occlusion and obstruction, as they affect sound differently and require separate handling in code and FMOD Studio.

Occlusion

Occlusion occurs when a solid object completely blocks the direct line of sight between a sound source and the listener. The sound must diffract around the object or travel through it, resulting in significant volume reduction and a low-pass filtering effect. For example, a gunshot fired in an adjacent concrete room will sound muffled and distant. In FMOD, occlusion is typically modeled by attenuating volume and applying a low-pass filter to remove high frequencies.

Obstruction

Obstruction describes partial blocking of the sound path. The direct path is not fully cut off, but the sound must pass through a semitransparent material or around an edge. This causes moderate volume reduction and frequency attenuation. A player talking through a thin wooden door is a classic example of obstruction. The voice remains intelligible but sounds slightly dampened. In practice, obstruction often uses a milder low-pass filter and less extreme volume reduction than occlusion.

Both effects rely on the geometry and material properties of the environment. A key principle is that occlusion and obstruction are continuous values rather than binary states. The amount of blocking should scale smoothly based on the number, thickness, and material of obstacles.

Setting Up FMOD for Spatial Audio

FMOD provides a robust 3D audio pipeline that can be extended with custom occlusion/obstruction logic. The first step is to properly configure your FMOD project and event structure.

Creating a 3D Event in FMOD Studio

Open FMOD Studio and create a new event. Under the 3D tab, ensure the event is set to 3D rather than 2D. This enables spatialization, distance attenuation, and Doppler effects. Inside the event, add two parameters: Occlusion and Obstruction. These will be driven by game code at runtime. Set their ranges from 0.0 (no blocking) to 1.0 (full blocking). In the event timeline, map these parameters to volume and low-pass filter automation. For occlusion, you might set the volume to drop to -40 dB and the low-pass frequency to 400 Hz. For obstruction, a milder drop to -15 dB and low-pass to 2000 Hz works well.

Integrating FMOD with Your Game Engine

After updating the FMOD Studio project, bank builds must be regenerated. In Unity, import the FMOD Unity Integration package. In Unreal, enable the FMOD Studio plugin. Both engines provide C# or C++ APIs to control FMOD at runtime. Ensure your listener and all sound-emitting objects use FMOD’s RuntimeManager to create and manage events. Unity developers can use FMODUnity.RuntimeManager; Unreal developers use UFMODAudioComponent or direct calls to FMOD::Studio::EventInstance.

Implementing Raycasting for Obstacle Detection

Raycasting is the most common and efficient method to detect obstacles between the sound source and the listener. The basic approach casts a ray from the listener position to the sound source position. If the ray hits a collider, obstacles exist. The occlusion/obstruction values are derived from the number of hits, hit distances, and material properties.

Basic Single-Ray Implementation

In Unity, a simple Physics.Linecast or Physics.Raycast can detect if the line of sight is blocked. The following C# snippet demonstrates how to set the occlusion parameter on an FMOD event instance based on a single ray hit:

// In a MonoBehaviour attached to the sound source
private RaycastHit hit;
private EventInstance eventInstance;

void Update() {
    Vector3 listenerPos = AudioListener.transform.position;
    Vector3 sourcePos = transform.position;
    Vector3 direction = sourcePos - listenerPos;
    float distance = direction.magnitude;

    float occlusion = 0f;
    if (Physics.Raycast(listenerPos, direction.normalized, out hit, distance)) {
        // Assume full occlusion if any obstruction exists
        occlusion = 1f;
        // Apply low-pass and volume based on hit material
        // (see material properties section)
    }
    eventInstance.setParameterByName("Occlusion", occlusion);
}

While this works, a single ray is unreliable—it may miss edges or give a binary result. For realistic behavior, you need multiple rays or a volumetric approach.

Multiple Raycasts for Smoother Occlusion

Instead of one ray, cast several rays from points around the sound source (e.g., a small sphere). Each ray contributes to an average occlusion value. For instance, cast 8 rays in a hemispherical pattern around the sound source. Count how many rays are blocked and weight them by distance from the source. This produces a fractional occlusion value between 0 and 1. Below is an enlarged version of the logic:

int rayCount = 8;
float totalOcclusion = 0f;
float radius = 0.5f; // sphere around source
Vector3 sourcePos = transform.position;
Vector3 listenerPos = AudioListener.transform.position;

for (int i = 0; i < rayCount; i++) {
    // Generate random direction on sphere
    Vector3 offset = Random.onUnitSphere * radius;
    Vector3 rayStart = sourcePos + offset;
    Vector3 rayDir = (listenerPos - rayStart).normalized;
    float rayDistance = Vector3.Distance(rayStart, listenerPos);

    if (Physics.Raycast(rayStart, rayDir, out RaycastHit hit, rayDistance)) {
        totalOcclusion += 1f;
    }
}
float occlusionFactor = totalOcclusion / rayCount;
eventInstance.setParameterByName("Occlusion", occlusionFactor);

This method smooths the transition as the sound source moves behind objects. You can further refine by not counting rays that hit very thin objects or by using raycast layers to ignore the source itself and the listener collider.

Material Properties and Frequency Filtering

Different materials absorb or reflect sound differently. A drywall wall dampens less than a solid concrete pillar. To account for material, assign physics materials to your colliders with occlusion properties. In Unity, you can use a custom script that reads a Material or PhysicMaterial and maps it to a value. For example, a PhysicMaterial could have a Sound Absorption float property. When raycasting, retrieve the hit collider’s material and use its absorption value to scale the occlusion parameter. For obstruction, you might also modulate the low-pass cutoff frequency curve. FMOD’s setParameterByName can be called multiple times per frame to update both parameters:

float absorption = GetAbsorptionFromMaterial(hit.collider.sharedMaterial);
float occlusion = absorption * occlusionFactor;
float obstruction = absorption * occlusionFactor * 0.5f; // milder effect
eventInstance.setParameterByName("Occlusion", occlusion);
eventInstance.setParameterByName("Obstruction", obstruction);

This approach allows dynamic environments where materials change (e.g., a wall breaking).

Applying FMOD’s Built-in Features

FMOD provides several built-in mechanisms to apply occlusion and obstruction beyond custom parameters. Using the EventInstance methods correctly is crucial.

set3DAttributes and Spatial Blending

Every 3D event must have its 3D attributes updated each frame. Call eventInstance.set3DAttributes with the listener and source positions. This enables FMOD’s native spatialization, including distance attenuation and panning. Occlusion and obstruction are applied on top of this. Ensure your event’s attenuation curve is set to something sensible in FMOD Studio—start with a default “Logarithmic” curve and adjust based on your game scale.

Using FMOD’s Environmental Reverb

FMOD includes an Environmental Reverb effect that can be automated alongside occlusion. When a sound is heavily occluded, you might want the reverb to become more prominent to simulate sound coming through a wall. In FMOD Studio, add a Reverb effect to the event’s mixer group. Create a third parameter called ReverbMix. Script side, when occlusion is high, increase reverb mix. This creates a convincing auditory illusion of sound traveling through a barrier. For example, a distant explosion behind a building will have a strong low-end thud with lots of reverb, while direct line-of-sight explosions are crisp and dry.

Parameter Curves and Automation

Back in FMOD Studio, the parameters you drive from code must be mapped to actual audio properties. Select the event’s Track (e.g., the audio clip timeline). Click on the volume envelope and choose Add Automation → Parameter → Occlusion. Now the volume will follow the occlusion value. Do the same for a low-pass filter (an effect added to the track’s signal chain). Set the filter cutoff to map from 22000 Hz (no occlusion) down to, say, 400 Hz (full occlusion). For obstruction, use a less aggressive curve, perhaps only going down to 2000 Hz and reducing volume by -10 dB at most. These curves can be edited by right-clicking the automation line and adding points.

Advanced Techniques

For larger projects, basic raycasting may not suffice. Consider these advanced methods to improve accuracy and performance.

Volumetric Occlusion with Portal Systems

In games with complex geometry, such as indoor/outdoor transitions, consider implementing a portal or cell-based system. Precompute which rooms are connected and treat doorways as acoustic portals. When a sound source is behind a portal, the occlusion factor is determined by the number of portals between source and listener. This avoids per-frame raycasting and works well for static geometry. FMOD’s setParameterByName still applies, but the occlusion value is derived from a room graph.

Reverb Zones and Audio Shapes

Another approach is to define audio trigger zones with different reverb presets. As the listener moves through zones, the reverb of the sound source changes. Combined with raycast occlusion, this produces natural transitions. For instance, a source inside a cathedral will have long reverb tail, while a source outside will have short reverb. Use FMOD’s Reverb effect on a bus and control its mix via a global parameter set by the player’s zone.

Performance Considerations

Raycasting every frame for every sound source can be expensive. Optimize by:

  • Limiting raycasts to sounds within a maximum distance (e.g., 50 meters).
  • Using a cooldown timer (e.g., recalculate every 0.1 seconds).
  • Batching raycast requests via Physics.RaycastNonAlloc.
  • Only applying occlusion to important sounds (e.g., enemies, not ambient birds).

Also ensure your FMOD parameters are not updated every frame if the occlusion value hasn’t changed much—use a threshold comparison.

Practical Tips and Best Practices

  • Use multiple raycasts around the sound source to avoid thin edges causing binary results. A 5-8 ray array provides a good balance.
  • Adjust attenuation curves to match environmental materials. For example, a wooden wall should dampen sound more than a curtain. Create a lookup table with material-to-absorption ratios.
  • Combine occlusion with reverb effects for enhanced spatial perception. Heavily occluded sounds often have more reverb; direct sounds have less.
  • Test in various environments to calibrate parameters for different materials and geometries. Use a test level with simple cubes and different physics materials to verify behavior.
  • Use FMOD’s Live Update to monitor parameter values in real-time. In Unity, connect via FMOD Studio Live Update. This allows you to see occlusion values adjust as you move the listener.
  • Don’t forget the listener itself. If a listener is underwater, that affects all sound. Implement a global occlusion modifier that combines with per-source occlusion.
  • Consider a smooth interpolation for occlusion parameter updates. Instead of setting the parameter directly each frame, lerp toward the target value to avoid abrupt changes.

Testing and Tuning in Game

Once implemented, testing is crucial. Walk the listener through various environments and listen for unnatural transitions. Common pitfalls include:

  • Occlusion dropping to zero instantly when the source is just behind a pillar.
  • Too much low-pass filtering making sounds inaudible.
  • Reverb not matching the expected acoustics.

Use FMOD’s built-in 3D Audio Visualizer in Studio to see listener and source positions. Alternatively, you can draw debug rays in the game engine to visualize raycasts. In Unity, use Debug.DrawLine to show blocked vs. clear rays. Record the parameter values using FMOD’s profiling tools. Tweak the automation curves until occlusion/obstruction feels natural without becoming a gameplay nuisance (e.g., players should still hear footsteps through walls, just muffled).

Conclusion

Implementing environmental audio occlusion and obstruction in FMOD transforms a flat soundscape into a living, reactive audio world. By combining game engine raycasting with FMOD’s parameter automation and reverb, you can simulate realistic sound propagation that responds to geometry and materials. Start with a simple single-ray setup, then expand to multiple rays and material-aware filtering. Use the advanced techniques of portal systems or reverb zones for larger, more complex environments. Remember to test exhaustively and tune the parameter curves in FMOD Studio. The result will be a more immersive game where players can truly “hear” the space around them.

For further reading, consult the official FMOD Documentation, the Unity Physics.Raycast reference, and the Unreal Engine Line Trace Guide. Additional resources on audio occlusion include the Game Developer article on occlusion/obstruction and a Wwise occlusion white paper (techniques are transferable).