Skip to content

Releases: vNAAATS/vatsim-NAAATS

[BETA]1.3b Hotfix 2

28 Sep 12:22
Compare
Choose a tag to compare

vNAAATS Plugin version hotfix v1.3b2:

Website: https://vnaaats.net/
Sector package (plugin fully installed): http://files.aero-nav.com/EXCXO

Bug fixes:

  • [ROUTE PARSING] Fixed a faulty line of source causing a crash when the route is instantiated in some uncommon cases.

Thank you for using vNAAATS! Feedback is always welcome. Join the vNAAATS discord here, or email info@vnaaats.net.

[BETA]1.3b Hotfix 1

26 Sep 11:49
Compare
Choose a tag to compare

vNAAATS Plugin version hotfix v1.3b1:

Website: https://vnaaats.net/
Sector package (plugin fully installed): http://files.aero-nav.com/EXCXO

Bug fixes:

  • [ROUTE PARSING] Fixed a bug where routes that contained only named waypoints would crash the client.
  • [ROUTE PARSING] Fixed a bug relating to expired NAT tracks that caused vNAAATS not to recognise the route, resulting in a crash.

Thank you for using vNAAATS! Feedback is always welcome. Join the vNAAATS discord here, or email info@vnaaats.net.

[OPEN BETA] Version 1.3b

23 Sep 15:34
Compare
Choose a tag to compare

vNAAATS Plugin version release v1.3b:

Website: https://vnaaats.net/
Sector package (plugin fully installed): http://files.aero-nav.com/EXCXO

Additions/modifications:

  • [General] Mach and FL now submitted into FSD if the OCA controller has the aircraft assumed, and received from FSD if not assumed.
  • [General] Cursor position detection mechanic updated to detect and calculate from actual monitor size.
  • [General] Added a version checker.
  • [General] Asynchronous vNAAATS network data posting to keep all clients up to date (by tracking controller). Data also fetched every 5 seconds.
  • [Flight Plan Window] Completely revamped data entry mechanics. If no clearance, route and destination are auto-filled into the data panel based on the aircraft's initial flight plan. The separate Man Entry panel has been removed.
  • [Flight Plan Window] Route will always be displayed in a north-oriented, W->E direction, regardless of direction of flight (from the real-life system).
  • [Flight Plan Window] Callsign will be displayed in yellow if the aircraft's oceanic clearance hasn't been marked as Read Back (ReadBk button).
  • [Flight Plan Window] Window now re-instantiates with new aircraft flight plan when selecting another aircraft without having to re-open FPWindow.
  • [Tag] Selected aircraft is now depicted with a rectangle border around the tag.
  • [Tag] Aircraft that have yet to have their clearance submitted to the vNAAATS network are highlighted with a purple callsign andtag border.
  • [Tag] Changed Mach to ground speed (N number). Mach approximation too inaccurate to be of any usefulness.
  • [Menu Bar] Added AUTO TAG button - resets tag labels to their default positions.
  • [Styling] Bitmap font added back again removing the need to have it installed locally.
  • [Debug] Further exception handling throughout the codebase and brief in-client debug logger. More verbose logs are stored in the .log file in the plugin directory.
  • [vNAAATS Network] Support added for new API properties throughout the plugin.
  • [vNAAATS Network] Ability added to remotely configure the plugin NAT track source for major events such as CTP.
  • [vNAAATS Network] API endpoints updated to reflect the new API URL.
  • Minor GUI additions, styling improvements and BTS enhancements.

NEW TOOL: Flight Data Display (FDD)
The FDD serves to provide both oceanic and domestic authorities with automatic, real-time-updating electronic strips for cleared oceanic aircraft. It displays aircraft by track as well as random routings and provides much of the information located inside the client, with the additional display of any natTrak clearance information they may have received.
The tool is available at https://vnaaats.net/fdd. No authentication is required. Please note the following:

  • Custom sorting and filtering of the strips is at the top of the priority list, along with displaying pending natTrak clearances independently of submitted vNAAATS data.
  • Data is read only for now.
  • Scaling for smaller screen sizes and different screen distributions is not yet complete. The FDD works best with a 1920x1080, 16:9 monitor. Please use your browser's zoom function in the meantime if required.
  • The plugin author welcomes your feedback as always.

Bug fixes:

  • Huge overall performance and stability improvements.
  • [General] Fixed crash when closing Euroscope.
  • [General] Fixed crash related to asynced route calculations.
  • [General] Fixed flight-plan window closing randomly without user input.
  • [Graphical Data Display] Fixed visibility issue for CZQO, where westbound aircraft appear too late.
  • [Flight Plan Window] Fixed reversed display of lat/long points.
  • [Flight Plan Window] Fixed release button.
  • [Menu Bar] Addressed (and hopefully fixed) a graphical glitch which surfaced sporadically after interacting with a drop-down menu (please report if it persists).
  • [Routing] Fixed half-lat/lon points not being recognised.
  • [Track Info Window] Resized window to make room for longer NAT track routes.
  • [Other] Fixed SCO_WD_CTR not displaying correctly
  • Optimised various components and fixed other smaller bug throughout the codebase.

Known issues:

  • The Track Control mechanic is still work-in-progress and may therefore not function correctly.
  • NAT tracks may show with entry/exit waypoints defaulting to 0.0, 0.0. Please report the names of any waypoints for which this occurs and we will add them to the database.
  • An internal code ("AIRCRAFT") used by vNAAATS to determine some routing situations may appear in the flight plan window route box and cause a syntax error. This can easily be fixed by removing the code from the route.

Thank you for using vNAAATS! As always, feedback is welcome. Join the vNAAATS discord here:, or contact Andrew via his email: a.ogden@vatcan.ca.

Release Version 1.2

13 Aug 15:39
Compare
Choose a tag to compare

Various changes and additions including QDM tool, stability, client networking, logging and general clean up.

https://files.aero-nav.com/EXCXO

Release Version 1

14 Nov 23:49
Compare
Choose a tag to compare

Released for CTP.

Download the font file from here and the sector package from GNG. The DLL is packaged within it.

https://files.aero-nav.com/EXCXO

Version 4: Open Beta. EXPECT BUGS

12 Nov 12:45
Compare
Choose a tag to compare
Pre-release

Expect bugs in this release. Most should be in the flight plan window. Let me know about any message sending concerns over discord or my email: a.ogden@vatcan.ca.

Installation:

  • https://ganderoceanic.com/atcresources <- Go to this link to download the sector files
  • Install the font file
  • Load Euroscope. The plugin should automatically load. If it doesn't, open the plugins menu and load it manually with this DLL.

It is VERY important you use the Gander Oceanic sector files, not a custom set up.

World Flight Release

04 Nov 11:34
Compare
Choose a tag to compare
World Flight Release Pre-release
Pre-release

WF Release.

Beta Version 3.1

31 Oct 04:23
Compare
Choose a tag to compare
Beta Version 3.1 Pre-release
Pre-release

Conflict list implemented, inbound list coordinates parsed into NN/WW and sensitivity lowered on STCA (won't yell at you unless there actually is a conflict).

Conflict list shows the two aircraft in conflict and either W or C plus their distance in time. Example: W7 means the planes are in Warning status at 7 minutes apart. C3 means that the planes are in a critical conflict status at 3 minutes apart.
Warning triggers between 8 minutes and 5 minutes inclusive. Critical triggers under 5 minutes.

Beta Version 3

30 Oct 22:51
bca18c1
Compare
Choose a tag to compare
Beta Version 3 Pre-release
Pre-release

Route drawing has been rewritten with support for multiple route drawing at once and Concordes.

This version also includes the new flight plan window interface panels, which are currently non-functional.

Please use this version at your own risk as always. Message me on Discord if any bugs are discovered. I am especially interested to see if there are any bugs with the PIV tool and Concorde routes when they have specified a legacy track in the flight plan (like NATSM, NATSN).

Other included things are anti-aliasing on all line drawing and a small performance bump overall.

Beta Version 2

15 Oct 08:51
Compare
Choose a tag to compare
Beta Version 2 Pre-release
Pre-release

Changelog:

  • Only internal changes. A tiny performance boost.

Bugs I have become aware of:

  • Concorde routes not properly accounted for, may experience a crash when trying to draw a Concorde route.

A quick reminder that the vNAAATS.ttf font needs to be installed. Enjoy!