XSquawkBox, a X-Plane 11 plugin that is being used to connect to VATSIM network, has been updated to 2.0 version.

The update adds many features and fixes. First of all, the developer notes that you have to update, as the old version of XSquawkBox will not have an ability to connect to the network. The update fixes a cosmetic bug where XSB OBSs would register themselves as servicing 99.998 MHz instead of 199.998, there were also made some fixes to the AFV service to the XSquawkBox. You can see more in the changelog below.

Changelog

  • Fixed a cosmetic bug where XSB OBSs would register themselves as servicing 99.998MHz instead of VATSIM’s standard 199.998MHz.
  • We now mangle the malformed x.x20 and x.x70 frequencies to their correct form (x.x25 and x.x75) when displayed, and normalise all frequency usage correctly for the respective service. Hopefully this ends the confusion over what to tune, and radios not working as expected.
  • We also now normalise the HF Alias list to ensure we match frequencies correctly due to the discovery that not only did our behaviour not match the expected one for .x25/.x75 aliases, but the actual alias list itself contained inconsistencies.
  • Make sure that command-entered frequencies (// and ///) are rounded to valid channels.
  • Verbosely report when we’re connecting and disconnecting from VATSIM AFV (Voice) as AFV service issues causing silent failures have been confusing end-users.
  • AFV-Native: Disable Nagle (where possible) on HTTP connections per the insistence of the AFV team. This is expected to be zero net change as curl buffers HTTP requests properly, but will eliminate any edge-cases where the AFV servers delayed ACK can cause a short (200ms) delay in finishing a HTTP POST.

You can see more on XSquawkBox website here.

Read also: JetSet Designs Releases Quad Cities International Airport for XP12

This article was brought to you by:

Mr. Publisher badgeCaptain badge4 Years in the team badgeTeacher badgeReviewer badgeMr. Popular badge

Related posts