One of the libraries used in the new voice support uses the posix monotonic time functions which are not available in macOS prior to 10.12.
Given that the macOS upgrades are free, macOS 10.12 supports systems up to 10 years old, and it represents an unreasonable support burden to fix this issue, I will be discontinuing support for macOS 10.11 and earlier, and the documentation will be updated in the next release to reflect this change.
Please do not report any issues related to macOS versions prior to 10.12
Update: The hotfix is now available for download.
I’ve just tracked down the cause for a crash on some macOS systems which is related to the opus audio codec.
This bug affects all macOS systems that use CPUs that do not support AVX. AVX was introduced in 2011, so all mac systems from before 2011 will not currently work because of this issue. Mac systems from after 2011 that use an older CPU (such as the 2012 MacPro hex-core) also will not work.
The crash will be characterised by X-Plane crashing when a connection is made, or the audio setup dialogue being displayed. The macOS crashlog will indicate “
Exception Type: EXC_BAD_INSTRUCTION (SIGILL)” with the crashed thread crashing in
silk_VAD_Init + 4
Unfortunately, the opus team accidentally force-enabled AVX optimisations in their build tooling for opus, and so if the library is built on any AVX-capable mac, the result uses AVX, irrespective as to any options we set to inhibit that support.
I’ve patched the XSquawkBox libopus to disable this and as long as this doesn’t break the Linux build (the same options get used there), this update will be published as hotfix 2.
If you are using an old Mac – please hold off further bug reports until beta 4 hotfix 2 is published.
There’s a few consistent issues I’m seeing which I do not need further reports on:
- macOS: crash on startup – there’s a bug in portaudio or in how AFV-Native uses portaudio causing this and the last update changed it from being intermittent to being reliable. I will be chasing this one up in the next week or so.
- Windows: plugin not loading (module not found) – In the changes to the build tooling, it seems I accidentally reset the plugin to being built against the Dynamically linked C runtime by accident. You likely need to install the “Microsoft Visual C++ Redistributable for Visual Studio 2019” for x64. I will try to fix this for the next release so this is no longer a consideration, or the correct runtime installer is included in the download.
For everbody else, I will respond to legitimate bug reports as able, but bear in mind the full instructions on the submission page – the form is for bug reports only – I can make no leeway for people not obeying the bug submission instructions.
- If you’re not submitting a bug, your submission will be deleted without response.
- If you do not submit the Log.txt, or edit/filter it prior to submission, your submission will be deleted without response.