Jump to content

Steve Biddle

  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral
  1. This information is in the user manual. You can find it here: https://xsb2-manual.readthedocs.io/en/latest/getting-started.html#configuring-xsquawkbox Cheers, Steve B.
  2. The problem is not with XSB. The plugin is doing what it is designed to do. I was getting warnings as well, but never any disconnects. And, was getting 45-60 FPS when I would get the warning. I logged a data file and went for a flight on the network, which I received a warning about an hour into the flight. After the flight I reviewed my data file and found that my frame rate was going from 49 to 19 for a few seconds and then it would recover. Hence never a disconnect. My problem was caused by a wireless headset that would hit my CPU every hour or so for whatever reason. Changed to a wire
  3. Yes. 1.3.3 lacks ACCONFIG support (which provides ground-level correction & aircraft configuration sharing) & lacks native AFV support. The entire XSB 1.x series will stop working on the network once 2.0 is stable. Given that a lot of the issues have been dealt with (although it looks like another macOS build issue has crept in), and the next release after beta5 will be stable, now is a good time to switch. Thanks for the heads up Mr. Collins. Appreciate all the time and effort that you have invested to make this happen! Regards, Steve B.
  4. Hello, Question. I am still using version 1.3.3 with no problems. Is it recommended to update to the latest client? I like the idea that if it's not broke, don't fix it. Thank you. Best regards, Steve B.
  • Create New...