Some sounds stop playing after changing cameras

Version: *1.0.84.0 *

Frequency: Consistently

Severity: Blocker

Bug description: Changing cameras is stopping some of the sounds from playing. We don’t recall this issue before 1.0.84.0 and does not happen on FS20 with the exact same soundpack.

We launch the aircraft on the ramp, start the battery (which has an associated “avionics sound”), change camera to external, and hop back into internal - and the sound is gone.

This seems to affect a handful of other “internal only” sounds (Alarms, GPWS Calls, etc).

The package is non-modular. Have tried various aircraft, all presenting the same issue.

I confirm the same behavior : external cam, internal cam, no more engine sound

Bump. Quite a big deal as sounds are not consistent in fs24.

Hello @vantech @bagolu

Can you please tell us which package demonstrate the issue so we can have a look?

Regards,
Sylvain

@FlyingRaccoon Miltech CH47:

  • Troop Jump alarm - load the aircraft C&D (Bilbao helicopter parking works best, only airport I’ve seen with heli parking), get in the cockpit by ctrl C, turn on Battery, set turn on alam, switch cameras.

C17 (1st party included with Premium Deluxe), any of these sounds are affected:

  • Stall Test
  • Bailout Alarm
  • Batt instrument noise
  • any of the warnings (flaps not configured, stall, etc.)

Issue persists on Dev Alpha 1.0.86.0

Hello @vantech

This is a 100% repro rate in your case?
I’ve followed your repro steps but so far, I always have the troop jump alarm, regardless of the camera I switch to, when I go back to the cockpit.
I can also always here the battery related background noise.

1 Like

It’s 100% repro on my end, and everyone on the team is experiencing the same. I can attach a video if required. Keep in mind I’m not sideloading the CH47, but instead I have a FS24 build that I can also provide.

C17, its pretty evident with the Stall or Fire tests:


Start either C&D or ready to fly, set either of these test, change cameras and sounds are gone. Its consistently replicable on my system and at least 3 other sim installs.

@FlyingRaccoon Any news? Will affect users across various aircraft if not fixed before release

Hello @vantech

I thought this was a backward compatibility issue and tested the 2020 package on 2024.
I checked the 2024 version and was able to replicate the problem. This is being investigated by the sound team.

Are these sounds positioned via node names by any chance? We suspect this has to do with the LOD selection and wwise losing the sound position when a node is unloaded/reloaded.
If so, positioning these sounds via XYZ positions rather than node names should be a good workaround.

Regards,
Sylvain

2 Likes

Glad you were able to confirm. It does seem that all the missing sounds are indeed positioned via node names, so your explanation does make sense.

However, it is far too late for us to modify the entire soundpack for the main aircraft affected, which is a 1st party aircraft going live tomorrow. We can’t push it through QA this fast, and it is quite a risky endeavour repositioning all these sounds…

Node placement of sounds is also widely used across many aircraft, so beware this affects many others out there.

Any ideas?

1 Like

The thing is, it’s quite difficult for our sound team to trace the cause of the issue without the Wwise source project.

They have other suggestions:

  • Check that this checkbox is disabled for your sounds:



    This is not needed in your case, and can cause this bug.

  • In the case of the CH47 troop alarm, the sound was not looping at all which can also be caused by an incorrect configuration on Wwise side

Ideally, if you can’t share a package with the Wwise project, creating a demo Wwise project with a dummy sound that replicates the problem could help us a lot.

Regards,
Sylvain

1 Like

We do not use that option.

I will pack the wwise up and share it via private share.

1 Like

Done, wwise sent

1 Like

Hello @vantech

Thank you.
This allowed us to confirm this is caused by sounds using node names for position, being incorrectly positioned after a model/LOD switch.
Position falls back to aircraft datum, and combined with attenuation, this explains why some sounds can still be heard but are quieter.

I’ll update this post as soon as we have a fix in the pipes.

Regards,
Sylvain

3 Likes

@FlyingRaccoon Is there a planned ETA for this fix? We are preparing the first batch of updates and would like to plan accordingly.

Hello @vantech

No ETA unfortunately
It’s worth going for the workaround I think, if you plan an update soon.

Regards,
Sylvain

This is quite unfortunate. This is a major issue with multiple aircraft and completely breaks the intended experience of this particular project.

The workaround may be a solution, though incredibly time consuming given the number of sounds that need to be repositioned across several aircraft.

1 Like