Just a quick note before I get more bug reports:
XSquawkBox is NOT supported (at all) with X-Plane’s Virtual Reality Headset features at this time. If it works for you, that’s great, but if it doesn’t, please don’t file bug reports or try to contact me – I will test it and address bugs when I have some time and the VR support is closer to complete/stable.
If you want to help with VR Support, libxplanemp needs some love to use the new XPLMInstance API (as recommended by Ben recently).
Because of the changes desirable for VR support, the full deprecation of legacy CSL may be coming sooner than I thought. If you are still using X-CSL or other legacy CSL sets, you may want to consider switching to a newer model set.
The 1.3.3 build is currently in progress and once final packaging and validity checks are done, I’ll be releasing it to the site.
In the past 24 hours I’ve managed to confirm and correct two bugs in beta1 which will be fixed in a new beta release I expect to have ready this weekend.
The first bug is fairly serious – it turns out that the pop-up list widget hasn’t been working properly with X-Plane 11 – any pop-up lists that had an action associated with an item being selected (such as in the Audio Setup dialog) weren’t having their action triggered. A fix for this will be in 1.3.3b2.
The second bug is just annoying – The search and filter for the airline entry box had a bug where if the combined number of matches from an airline codes search and an airline name search exceeded 50, it would not allow you to select anything other than “No airline”. This has now been fixed in 1.3.3b2 so if you have only a few matches on code, and a lot of matches on partial airline name, you can still choose one of the matches on code, and vice versa.