Nemisindo
Menu

Unreal Engine

Nemisindo for Unreal Engine

Find the Nemisindo product information that matches your Unreal Engine audio workflow.

This hub covers the durable workflow behind Nemisindo’s Unreal Engine products: choose a sound lifecycle, connect the parameters that matter to gameplay, and place the result in the project mix. The exact installation path and editor or API names depend on the product edition installed in the project, so use its supplied package documentation for those details.

Before opening a product workflow

Confirm which Nemisindo product and edition the project already contains. Add the generator to an object or sound graph whose lifetime you control, begin at a conservative level, and verify one default sound before connecting live game data. This makes it easier to separate an integration problem from an unexpected parameter value.

When the default sound works, connect one gameplay value at a time. Test the inactive state as well as the loudest or fastest expected state, then add attenuation, spatial behaviour, and environmental processing appropriate to the scene.

Action Pack

Nemisindo Action Pack for Unreal Engine, Unity, VST and Wwise.

Use Action Pack when an event or changing game state should shape an action sound instead of selecting another fixed recording.

Working pattern

  1. Choose the sound lifecycle

    Decide whether the sound should continue while an object is active or occur once in response to an event. Start and stop sustained generators with the object that owns them; trigger event sounds at the point the gameplay event occurs.

  2. Bind meaningful parameters

    Connect model parameters to values that already describe the action, such as speed, force, position, or elapsed time. Keep the generator inactive when it is not needed, and update only the values that should be heard changing.

  3. Place the result in the scene

    Set level, spatial behaviour, and environmental processing as part of the same Unreal audio mix used by the rest of the project. Audition both the nearest and most distant expected listening positions.

The exact component names, editor locations, and callable functions depend on the Action Pack edition installed in the project.

Product overview

Adaptive Footsteps

Nemisindo's Adaptive Footsteps plugin features a dynamic sound effect model capable of generating footsteps in real time, completely procedurally.

Adaptive Footsteps is designed around a step event plus the movement and material context that should shape that step.

Working pattern

  1. Choose where step timing comes from

    Use character animation or gameplay contact events when each footfall must line up with motion. If the installed edition provides an automatic cadence mode, reserve it for movement whose timing can be derived from pace.

  2. Set the walking context first

    Resolve the current surface and the intended footwear, firmness, and movement values before producing the step. Update those values when the character state changes instead of rebuilding the sound system for every contact.

  3. Test material transitions

    Check the transition between neighbouring surfaces as well as each surface in isolation. A step at a boundary should use the material resolved for that contact and should not leave the previous surface state behind.

  4. Follow the character in the mix

    Keep the sound attached to the character's audible position and test attenuation and environmental processing during walking, running, stairs, and stops.

Adaptive Footsteps has appeared in more than one Unreal workflow. Follow the documentation included with the installed edition for its current node, component, pin, and function names.

Product overview

Nature Pack

Storms, Caves, Waterfalls... We brought our nature-inspired models to Unreal Engine.

Nature Pack provides Droplets, Fire, Rain, Water, Waves, and Wind as responsive sources for ambience and changing environmental conditions.

Working pattern

  1. Assign one job to each layer

    Decide which source represents the scene-wide bed and which sources belong to specific emitters or weather events. Begin with one layer, establish its range, and add other layers only when they contribute distinct information.

  2. Drive change from the environment

    Map model parameters to the environmental values the project already owns, such as weather intensity, exposure, proximity, or flow. Smooth abrupt gameplay changes when an instant sonic jump would be distracting.

  3. Match the source lifecycle to the scene

    Activate long-running generators only while their scene or system is relevant, and stop them when leaving that context. Test repeated entry and exit so an old ambience layer cannot continue underneath a new one.

  4. Check space and perspective

    Decide whether a source is a broad ambience or a positioned emitter before applying spatial behaviour and environmental processing. Audition the complete mix from the player positions the scene supports.

Use the package documentation supplied with the installed Nature Pack for current setup paths, component names, and callable functions.

Product overview