Skip to content

Spatial audio settings for Wwise 2025.1 - #33

Draft
phevosccp wants to merge 2 commits into
mainfrom
spatial-audio-settings-2025
Draft

phevosccp wants to merge 2 commits into
mainfrom
spatial-audio-settings-2025

Conversation

@phevosccp

@phevosccp phevosccp commented Nov 19, 2026 •

Copy link
Copy Markdown
Member

Description

This PR brings the spatial audio settings up to the Wwise 2025.1 SDK and changes the defaults to the ones tuned in the frontier client while working on the geometry manager.

Based on #32

Testing

  • Added test_spatial_audio_settings_exposure.py and a test that sightlines are not queried while acoustics is enabled.
  • Tested locally in a frontier client.

@phevosccp
phevosccp marked this pull request as draft November 19, 2026 11:04
Base automatically changed from geometry-manager to main November 19, 2026 12:04
Cherry-picked from 35c4b58 onto the geometry manager.

- Settings added to match AkSpatialAudioInitSettings of the 2025.1 SDK,
  emitter clustering included
- Settings Wwise can take while it runs are sent when they change
- New defaults: 12 primary rays, path validation spread over 8 frames
  under a 10% CPU limit, path length 30000, mesh transmission loss 1.0,
  no diffraction on boundary edges, geometry not solid
- Line of sight queries are skipped while acoustics is enabled
@phevosccp
phevosccp force-pushed the spatial-audio-settings-2025 branch from 1900e1d to f052518 Compare November 20, 2026 14:14
- 5 primary rays instead of 12: the Ray Tracing Engine Geometry Guide says
  as few as 5 still give good results, and rays set the ray tracing cost
- Load balancing spread of up to 9 frames instead of 8: the same guide says
  spreads under 10 should not noticeably affect quality

Over the same flight and geometry, CPU total went from 35.9% to 27.7% mean,
ray tracing from 17.2% to 12.1%, and no frame went over 50%.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant