Known Issues and Limitations

This is a list of all known issues and reporting requirements for any related issues.

I can’t find the options to set PTT or access text commands.

You haven’t read the user’s manual.

I’m getting disconnected for Time Dilation but my framerate is good / I’m getting simulation rate warnings

There are no known issues with the detector itself.  Please see About the XSquawkBox/VATSIM X-Plane Simulation Rate Enforcement for more details on how the detector works and why it is highly unlikely that these determinations are in error.

If you believe the determination is in error, you must enable disk logging of your “Frame rate” and “Latitude, longitude, and altitude” and include the complete, unmodified data.txt from a session that experiences the classification you wish to challenge, in addition to all other standard reporting requirements.  Please see “Data Input and Output from X-Plane” from the X-Plane manual (or for X-Plane 10).  As the data.txt can be quite large, it is recommended to zip it and the log.txt file, upload them to dropbox, onedrive or similar cloud file service that supports file sharing, and include a sharing link in the bug report.

Please note that the developer will not respond to these cases unless a clear error can be determined from the provided data.

“The server … could not be resolved”

Upgrade to the latest release and try again before reporting any issues.  If you’re trying to connect to localhost, use the IP address (127.0.0.1) rather than the name.

Aircraft Lights (Legacy CSL)

Aircraft Lights for legacy CSL are not getting an overhaul.  The fix is to use OBJ8 CSLs instead.

Legacy CSL support is deprecated (despite the fact we still ship XSB2 with some legacy CSL models) and full support for Legacy CSLs will be dropped in XSB3.

If you want better lights, upgrade your CSL set.  If you’re an artist, make OBJ8 CSLs!

No bug reports related to the aesthetics of Legacy CSL rendered aircraft will be accepted.

Model Matching

Model Matching actually works fine, but there’s a massive pile of edge cases we can do nothing about which make it look worse than it actually is:

  • We cannot compensate for people who insist on using invalid ICAO Equipment Codes, which has been the main source of problems where a viable match is possible.  Frequent offenders here include:
    • fictional equipment codes for model variants – we support visual variants via livery codes, not via equipment.  ICAO usually only assigns a single equipment code for all variants unless the variation produces a significant change in the aircraft’s performance).  Examples of this sort of error include using B73Hand B73J for winglet equipped 737-800s, instead of the correct designator B738.
    • Using completely incorrect codes for new models not in the old (shipping) Equipment lists.  e.g:  using the invalid code A380 instead of the official code A388 for the Airbus A380-800, the invalid code B787 instead of the official code B788 for the Boeing 787-800, etc.
  • We cannot compensate for model sets that use non-generic liveries in the no-airline slot.  Bluebell CSL does this.  Model sets that do this will make all aircraft that do not match a livery in the CSL set look like a specific airline.  XSB has no awareness of when this is happening.
  • We cannot compensate for people changing their aircraft type without reconnecting (aircraft type can only set once in most clients – on connection – and changing whilst connected isn’t enough to affect a change of type for the clients).  This is mostly a bug in FSInn and similar vintage clients.  Most modern clients will not let users behave in a way that exacerbates it.
  • We cannot improve related-type matching without user contributions to the related type table.
  • We can’t magically match types for which there is no related type or a CSL available – if you want a new airline’s livery to appear and it isn’t already available, somebody needs to produce it.

Model matching issue reports must include a log with full model matching debug enabled and at least one “.debug csl” output.