XSquawkBox 2.0 beta 4 hotfix 2 is up on the Downloads page.
(hotfix 1 has been released to address a build issue with portaudio that resulted in the macos 10.15 dependency creeping back in – it contains no other changes and should work on older macOS releases now).
(hotfix 2 has been released to address a build issue with opus that resulted in AVX optimisations always being present on macOS and possibly Linux as well)
This release incorporates a number of bugfixes as well as a reversion to the older portaudio sound driver. More importantly, macOS 10.14 and newer are supported again when used with X-Plane 11.41 (or newer).
Continue reading “XSquawkBox 2.0beta4 Released”
XSquawkBox 2.0 beta2 can be downloaded from the downloads page. The expiry date remains unchanged as 1 Dec 2019.
All users using 2.0 beta 1 should upgrade immediately.
Please read the beta1 release post if you have not already done so as it contains critical information for using XSB 2.0.
Beta 2 has the following fixes:
- macOS build should now be built with macOS 10.9 as the mandated minimum version. (we can’t do 10.8 anymore due to dependencies. sorry.)
- A logic inversion that prevented the text radio from working was identified and corrected.
- AFV-Native: The default device selection logic was reworked slightly to reduce the risk of not being able to start-up audio at all.
- xplanemp: The Asynchronous OBJ8 loader is now reenabled when it’s available.
Beta 2 has the following known issues:
- macOS build is still not signed.
- The manual is still missing.
Without further ado, I’ve released the beta 1 release of XSquawkBox 2.0. This is a time-limited release and will auto-expire on 1 December 2019.
As this is a beta release, back up your XSquawkBox installation before you upgrade. If you cannot deal with X-Plane potentially crashing, please do not upgrade yet. I should have a more polished and tested beta 2 release out sometime early/mid November.
Please read the warning on the download page about cryptographic components in XSquawkBox 2.0 before you download. This may pose a problem in countries where import licensing is required, or where government permission is required. We cannot advise you or provide any guaranties as to the legality of using XSquawkBox in your country. There are online resources which provide summaries as to national restrictions such as the Crypto Law Survey and the World map of Encryption Laws and Policies. If you have any doubt, please seek legal advice. Unfortunately we cannot support AFV without using cryptography at this time.
Also of note:
- There is no manual right now. If you are not familiar with the X-Plane command binding system for your version of X-Plane, do NOT upgrade as you need to manually bind all of the XSquawkBox controls that you want access to before you connect for the first time.
- There are bugs. Please read the readme file for details about the ones I know about.
- HF Aliasing is implemented, but I was unable to find a correctly mapped oceanic controller to test it with prior to release.
- There are bugs. Oh, I mentioned that already?
All of that said – the release should be quite workable. The bugs I know about are all pretty benign.
A quick cheatsheet so you know how to get started:
xsquawkbox/command/start_text_entry (“XSB: Start Text Entry” in X-Plane 11) to Enter and/or Space.
xsquawkbox/voice/ptt (“XSB: Radio Press-to-Talk” in X-Plane 11) to the joystick button and/or keyboard keys you want to use as your Radio PTT.
- Bind the other
xsquawkbox/ (“XSB:” prefixed in X-Plane 11) commands as you feel you need.
- Use the audio panel controls to select which radio and frequency both the text radio and voice radio work on.
- If your aircraft model doesn’t have a working audio panel, you can use
.tx ? to find out which radio is set to transmit, and use
.tx COM1 or
.tx COM2 to change the active radio to send.
- Similarly, if your aircraft model’s audio panel doesn’t have proper receive select controls you can use
.rx COM1 on and
.rx COM1 off (and similarly for COM2) to turn that audio source on and off.