[Flightgear-devel] Help with phantom aircraft error / loadWAVFromFile

[James T. <ja...@fl...>]

The A320 doesn’t have a bug. But FlightGear thinks it does, because sometimes, it *seems* to have a bug:

	https://gitlab.com/flightgear/aircraft-bugs/-/issues/50

The error (and log messages on the console / fgfs.log) says:

	Error:error-type-not-found from error-audio-fx-load::loadWAVFromFile: not found

That message **should** contain the file path that’s not found, but of course the A320 doesn’t actually have any missing WAV files. *And* the code in XMLSound checks the file paths at init time (when the sim starts up), but the error occurs at runtime.

The current assumption is that some other subsystem is creating a sound sample with an empty file name, but in a way that looks like it comes from the aircraft . But we can’t so far work out which subsystem that is. The places we have that generate audio (eg ATC / ATIS / morse ident) explicitly set a ‘this sample is from data, not a file’ flag inside SGSoundSample, and therefore won’t try to hit the ‘load from disk’ code path.

The annoying thing is, if I could reproduce the error, I could fix it very quickly, but for me, the error doesn’t occur *at all* (and the same for Josh). So the question for people who use the A320 (but it could probably be some other aircraft, because again, this is likely not something the A320 is doing directly), is do you get this error / see this message in the console, and if so, how might your setup differ to mine. Based on the Sentry reports, the A320 definitely triggers the error more frequently than other aircraft.

If you can trigger the message, and have a debug build, it’s trivial to add a breakpoint in loadWAVFromFile, and we could look at the sample information and probably work this out, of course.

As ever, please comment on the GitLab ticket, to keep the discussion as focused as possible.

Kind regards,
James