Search Unity

Audio Bug: AudioSources ignore "Bypass Reverb Zones" in 2017.1

Discussion in 'Audio & Video' started by ReaktorDave, Jul 14, 2017.

  1. ReaktorDave

    ReaktorDave

    Joined:
    May 8, 2014
    Posts:
    139
    Since Unity 2017.1, AudioSources ignore the setting "Bypass Reverb Zone" and possibly others too.
    1. Create and open a blank project
    2. Create a GO with an AudioSource, load an audio clip (long or activate loop), set "Bypass Reverb Zone" to true and set the AudioSource to "Play on Awake"
    3. To the same position as the AudioSource GO place another GO with a reverb zone, preset "Generic" should suffice
    4. Start the scene and you will hear the audio clip plus reverb though it shouldn't be affected by the reverb zone.

    This used to work in Unity 5.x, likely a regression. This may also affect the other settings "Bypass Listener Effects" as well as "Bypass Effects", but I didn't test that.
     
  2. jamesdevstory

    jamesdevstory

    Joined:
    May 16, 2016
    Posts:
    1
    I have also experienced this issue since upgrading to 2017.1f3.
     
  3. r618

    r618

    Joined:
    Jan 19, 2009
    Posts:
    1,305
    @ReaktorDave @jamestc If possible, submit a bugreport
    Being it written just here is also almost as good as non existant ]
     
  4. ReaktorDave

    ReaktorDave

    Joined:
    May 8, 2014
    Posts:
    139
  5. Huknar

    Huknar

    Joined:
    Mar 6, 2015
    Posts:
    40
    This issue is beyond frustrating. Can we please get a backport fix for this? Goodness knows what 2017.2 breaks. This is a pretty major issue with the audio system.
     
    ArachnidAnimal likes this.
  6. ArachnidAnimal

    ArachnidAnimal

    Joined:
    Mar 3, 2015
    Posts:
    1,835
    All this time I thought I was doing something wrong to cause this problem. Turns out it is a bug. Just also wonder why Unity waited until 2017.2 to patch this issue. We shouldn't be expected to download a major update to Unity just to receive a fix for an issue like this.
    Does anyone know if this is fixed in 2017.2?
     
  7. ReaktorDave

    ReaktorDave

    Joined:
    May 8, 2014
    Posts:
    139
    Yes, it is fixed in 2017.2 and higher.
     
    ArachnidAnimal likes this.