Releases: vACDM/vacdm-plugin
v1.3.2
v1.3.1
fixes:
- ECFMP MDI not displaying
- EXOT color being black, while it should be TAG_COLOR_DEFAULT
v1.3.0
major refactor
significant changes to the previous version (1.2.2) are:
-
Single thread managing updates, aircraft and airports
each airport is not running on a separate thread anymore. Instead there is one thread which manages all updates, aircrafts and airports. This was the primary reason for performance bottlenecks which increased with the amount of active airports. -
Euroscope data updates are now being handled asynchronously
This prevents minor stutters every time vACDM obtains a copy of the aircraft data as Euroscope does not thread plugins. This also prevents panning on RadarScreens being interrupted. -
Active airports are now being determined using the left column of checkboxes in the RunwaySelectionDialog
Combined with single thread fixes long loading times on plugin startup if a lot of runway configurations are set as default -
Airport name is not required to be ICAO only anymore
The airport name specified in the Euroscope data may now include more than just the ICAO (e.g. the full airport name). The ICAO is determined by finding the first four letter uppercase word in the airport name. -
Update rate is now configurable using “.vacdm updaterate value” or in the config file (vacdm.txt)
“.vacdm updaterate value” sets the update rate for the session, the default value which should be applied on plugin startup has to be configured in the config file (vacdm.txt)
value must be between 1 and 10 currently, default is still 5 like in the previous versions -
adds ".vacdm LOG ON/OFF/DEBUG" command to enable/disable logging and create DEBUG (i.e. detailed) logs
-
removed ".vacdm URL url" command, URL can be changed in the config file and then loaded using ".vacdm RELOAD"
if you are upgrading to v1.3.0, verify that Euroscope binds the TagItems correctly. It was reported that TagItems shifted after upgrading (i.e. column showing TSAT suddenly show AORT). This is a Euroscope bug, it only happens once. You can prevent this from happening on subsequent loads / when people are loading your published package, by saving the column definitions.
