volumeScale of AudioSource.PlayOneShot is not clamped to 1 when volumeScale is set higher than 1

Unity: Audio Authoring

Fixed

6.0.X

6000.0.3f1

2023.3.X

2022.3.X

2022.3.30f1

2021.3.X

2021.3.39f1

Won't Fix

2023.2.X

Updated the documentation for `AudioSource.PlayOneShot()`.

Cancelling this 2023.2 tech release issue since the support for this release has come to end of life. Cancelling this 2023.2 port case does not affect any LTS or Unity 6 Beta/Preview that remain open.

How to reproduce:
1. Open the attached project "playoneshotvolumescale.zip"
2. Enter Play Mode

Expected results: volumeScale of AudioSource.PlayOneShot is clamped to 1
Actual results: volumeScale of AudioSource.PlayOneShot is not clamped to 1

Reproducible with: 2021.3.35f1, 2022.3.20f1, 2023.2.10f1, 2023.3.0b7

Reproducible on: Windows 11 22H2
Not reproducible on: No other environment tested

Prioritise and Follow this issue

Have a workaround or additional info about this issue?

Issues you vote on will appear here

volumeScale of AudioSource.PlayOneShot is not clamped to 1 when volumeScale is set higher than 1

Unity: Audio Authoring

Statuses

Fixed

Won't Fix

Resolution Notes

2023.3.XFixedUpdated the documentation for `AudioSource.PlayOneShot()`.

2023.2.XWon't FixCancelling this 2023.2 tech release issue since the support for this release has come to end of life. Cancelling this 2023.2 port case does not affect any LTS or Unity 6 Beta/Preview that remain open.

Description

Prioritise and Follow this issue

Have a workaround or additional info about this issue?

volumeScale of AudioSource.PlayOneShot is not clamped to 1 when volumeScale is set higher than 1

Unity: Audio Authoring

Statuses

Fixed

Won't Fix

Resolution Notes

2023.3.XFixedUpdated the documentation for `AudioSource.PlayOneShot()`.

2023.2.XWon't FixCancelling this 2023.2 tech release issue since the support for this release has come to end of life. Cancelling this 2023.2 port case does not affect any LTS or Unity 6 Beta/Preview that remain open.

Description

Prioritise and Follow this issue

Have a workaround or additional info about this issue?