Martin Loxbo (811805) Posted April 12, 2019 Report Share Posted April 12, 2019 From what I've been able to tell, in COOPANS the Map_3 colour is used to display airways, but "beacons" such as fixes and navaids use the brighter Beacon colour. By the way, is it possible to set it up so that fixes/navaids/airports as displayed through the Maps menu are toggled on/off at startup? Link to comment Share on other sites More sharing options...
Juha Holopainen Posted April 13, 2019 Author Report Share Posted April 13, 2019 The state of the auto-generated maps in the MISC folder can not be directly set at startup, as the sector file based maps haven't been generated when the settings files are read. However, a workaround exists. For example defining [_] Setup_LoadMap=MISC\FIXES ALL + L in the settings file loads that map whenever any callsign containing the underscore character is used. That's almost as good as the map loading automatically on startup. Other more specific callsign-based settings can of course also be used. 1 Link to comment Share on other sites More sharing options...
Juha Holopainen Posted April 13, 2019 Author Report Share Posted April 13, 2019 The Ground Radar plugin has a small update as well: Ground Radar plugin 1.2.1 This should fix some plugin window scrollbar issues and a couple of safety nets which erroneously required the radar track to be correlated even when the normal "non-pro" mode was used. The safety nets should now get the same information about the tracks that is displayed to the controller. The plugin update system will notify about the update as well, but it may be more convenient to use the link above as the plugin's message box does not contain a link, just a text displaying the download location. 2 Link to comment Share on other sites More sharing options...
Martin Loxbo (811805) Posted April 13, 2019 Report Share Posted April 13, 2019 That's great! Has there been any updates to the cargo callsigns? I've added NPT and GTI myself as they were not on the list. Link to comment Share on other sites More sharing options...
Juha Holopainen Posted April 13, 2019 Author Report Share Posted April 13, 2019 (edited) Yes, the cargo callsigns data file has been updated. However, creating and updating the file has been a manual process so it is in no way a comprehensive list, just a bit better than nothing at all. Suggestions of changes are welcome, but only currently active real operators please in order to avoid conflicts. edit: the plugin package is now updated with a new cargo callsigns data file containing the two callsigns above and a number of others Edited April 14, 2019 by Juha Holopainen 1 Link to comment Share on other sites More sharing options...
Max Kuhla (1157125) Posted April 15, 2019 Report Share Posted April 15, 2019 (edited) @Juha Holopainen Having problems with the Datalink PDC/DCL when manning ESOS_CTR. I receive the request, the yellow "REQ" disappears after half a second and I can not send the clearence. When opening "DEP CLEARENCE-Window" it only shows as the normal window without the datalink/rtf option. Only happens when manning ESOS, on regional sectors it works just fine. Any ideas? I tried sending clearence to myself using the Hoppie MSFS-Client, the system sends the "REQUEST BEING PROCESSED STANDBY"-Message, but then everything happens as above Edited April 15, 2019 by Max August Larsson Kuhla Spelling and adding clarification Link to comment Share on other sites More sharing options...
Martin Tornberg (1069087) Posted April 15, 2019 Report Share Posted April 15, 2019 It has worked for me previously but not since the hoppie acars problem this weekend. Link to comment Share on other sites More sharing options...
Max Kuhla (1157125) Posted April 15, 2019 Report Share Posted April 15, 2019 I've had problems before the Hoppie-Abuse-Closedown also unfortunately Link to comment Share on other sites More sharing options...
Juha Holopainen Posted April 15, 2019 Author Report Share Posted April 15, 2019 Which plugin version has the issues? If more than one, any idea which version was the last one where it worked properly? The latest beta had some changes in this area so I may have broken something there. I’ll have a look at the code, but I won’t be able to do so until sometime next week. Hopefully it’s something simple as troubleshooting the datalink system is a bit tricky. Link to comment Share on other sites More sharing options...
Max Kuhla (1157125) Posted April 15, 2019 Report Share Posted April 15, 2019 (edited) Working fine on other positions, only having problems when manning ESOS_CTR/ESOS_1_CTR with logon ESOS 2.2.1b5 (Having same problems on version b4) EDIT: After reasoning and testing with some other controllers getting it to work on other positions, maybe the problem is me running ES r19, I'll check tomorrow if it works with an older beta version (Should not make a difference right? But I'll try anyways) Edited April 15, 2019 by Max August Larsson Kuhla Link to comment Share on other sites More sharing options...
Martin Stockzell (1294494) Posted April 17, 2019 Report Share Posted April 17, 2019 Got some error messages after updating: I'm guessing it has something to do with this new ring that Petter and Martin created around "Bällsta" to allow 3Nm sep, since the ring doesnt show. As soon as I press reload though, everything is fine with the settings. MSAW still yellow and creates an alert Link to comment Share on other sites More sharing options...
Juha Holopainen Posted April 17, 2019 Author Report Share Posted April 17, 2019 MSAW “no data” being yellow is as intended for a situation where the MSAW system is selected on in the plugin, but there is no data in the data file, or the file does not exist. It’s just pointing out that you are never going to get an MSAW alert in this situation. For the other issue, since the Maps data file doesn’t report any issues, the maps are probably defined ok. Why the settings file then has an issue with activating the map, at this point I don’t know, since apparently all the other maps set to activate in the settings file activate just fine? (the displayed error message means that the requested map doesn’t exist) 1 Link to comment Share on other sites More sharing options...
Max Kuhla (1157125) Posted April 17, 2019 Report Share Posted April 17, 2019 Found the cause and solution to my DCL-Problem! Running several instances of ES with the Topsky-plugin and several DEP-Lists caused problems. Only using having DEP-List open on the main instance seemed to solve this issue. Any posibility to make it usable on several instances? Link to comment Share on other sites More sharing options...
Martin Loxbo (811805) Posted April 17, 2019 Report Share Posted April 17, 2019 3 hours ago, Juha Holopainen said: For the other issue, since the Maps data file doesn’t report any issues, the maps are probably defined ok. Why the settings file then has an issue with activating the map, at this point I don’t know, since apparently all the other maps set to activate in the settings file activate just fine? (the displayed error message means that the requested map doesn’t exist) It shows up with "bad data" on ES startup, but after reloading the settings either by clicking the button in the Plugin Status menu, or by logging on at an active position, the "bad data" message is gone, and the ring displays. @Martin Stockzell MSAW is not active in Sweden (as in real life). I suppose we can de-activate it by default to avoid the yellow error message, or what do you say @Petter Jakobsson? 1 Link to comment Share on other sites More sharing options...
Martin Stockzell (1294494) Posted April 18, 2019 Report Share Posted April 18, 2019 8 hours ago, Martin Loxbo said: It shows up with "bad data" on ES startup, but after reloading the settings either by clicking the button in the Plugin Status menu, or by logging on at an active position, the "bad data" message is gone, and the ring displays. @Martin Stockzell MSAW is not active in Sweden (as in real life). I suppose we can de-activate it by default to avoid the yellow error message, or what do you say @Petter Jakobsson? Ah good to know regarding the settings thing. At least I know that I havn't mucked anything in the settings file myself Since a reload did fix the error, however MSAW still gave my an alert. But then I know that it's safe to update! Link to comment Share on other sites More sharing options...
Juha Holopainen Posted May 3, 2019 Author Report Share Posted May 3, 2019 (edited) Another update to TopSky: TopSky 2.2.1 beta 6 Changes from beta 5 include: Fixes in the datalink code. It is now possible to have DEP lists open on multiple instances and still have the DCL/PDC functionality working. The message timers are available only on the primary instance however so the indications will not start blinking shortly before timeout occurs on the proxy instances. A message formatting issue arising in certain conditions causing the clearance message to get rejected by the Hoppie server is also fixed. Map activation using settings fixed Specific colors added to auto-generated maps NAT Track Messages Window and related auto-generated maps added Edited October 12, 2019 by Juha Holopainen link removed, newer version available 1 1 Link to comment Share on other sites More sharing options...
Martin Stockzell (1294494) Posted May 4, 2019 Report Share Posted May 4, 2019 Oh nice. Now the message about the plugin settings aren't there anymore. Thanks @Juha Holopainen! Link to comment Share on other sites More sharing options...
Nikolas Goerlitz (1373921) Posted May 9, 2019 Report Share Posted May 9, 2019 Sorry for being so useless, guess I didn´t rtfm . Can anyone tell me whether or not I can change the color of an airway with COOPANS=0? Kind Regards Link to comment Share on other sites More sharing options...
Martin Loxbo (811805) Posted May 9, 2019 Report Share Posted May 9, 2019 Airway colours are in the symbology settings in ES itself. Link to comment Share on other sites More sharing options...
Fraser Cooper (1303570) Posted August 26, 2019 Report Share Posted August 26, 2019 Hello all, I am having an issue with the plugin. It seems in the download, there is only a .ddl plugin and a excel spreadsheet. However, when I load the plugin there is not data in the plugin status. http://prntscr.com/oxkyfv http://prntscr.com/oxkyyi Any help would be appreciated. Fraser Link to comment Share on other sites More sharing options...
Martin Stockzell (1294494) Posted August 26, 2019 Report Share Posted August 26, 2019 33 minutes ago, Fraser Cooper said: Hello all, I am having an issue with the plugin. It seems in the download, there is only a .ddl plugin and a excel spreadsheet. However, when I load the plugin there is not data in the plugin status. http://prntscr.com/oxkyfv http://prntscr.com/oxkyyi Any help would be appreciated. Fraser Regarding the MSAW I think the problem is the same I had before. Just add MSAW=0 or something similar to TopSkySettings.txt and it shouldnt nag about it. Check the discussion above. Link to comment Share on other sites More sharing options...
Juha Holopainen Posted October 1, 2019 Author Report Share Posted October 1, 2019 (edited) New beta versions are available: TopSky 2.2.1 beta 7 Ground Radar plugin 1.2.2 beta 1 There are no major changes to either plugin in terms of features. The TopSky plugin has an RDF function which at this point will be short-lived as it will cease to work when the new voice codec is taken into use in two weeks time. Whether it can be re-coded after that, remains to be seen. The Ground Radar plugin contains a number of bug fixes related to having more than one ASR with the same airport open, and an added comms type ("r" or "t") flag in the track labels. The main reason for the new versions is changing to a newer development environment (VS2019 from VS2010 for anyone that cares...) causing a number of changes in the code. This may have introduced unwanted behaviour so I thought best to release new beta versions without much to brag about in terms of new features. MAESTRO plugin 1.0 beta 3 A feasibility study of an arrival manager plugin. Still not sure if it has the potential to be more helpful than distracting when it's actually needed (i.e. big events). As you can imagine, online testing in heavy traffic has been almost non-existent, but it hasn't been completely useless in logfile playbacks. The included settings file contains some example settings for a couple of airports (putting System_Version=1 as a global setting at the top is recommended if you plan on using that version so you get the correct GUI also before setting an airport). For those of you running an earlier beta, the settings files have changed (no more airports data file, it's all in the settings) so it's probably best to remove the earlier files. And for heaven's sake, do not keep a file named "MAESTRO_data.txt" in the same folder with the plugin dll for any reason as the plugin will overwrite it without warning! There's big warning box in the manual about this but now you've been warned here as well... If the plugin(s) fail to load, you're likely missing the necessary runtime files. On this page, download the Visual Studio 2015,2017,2019 "x86" runtimes to fix it. Edited October 30, 2019 by Juha Holopainen links removed, newer versions available 3 Link to comment Share on other sites More sharing options...
Patrick Weineis (1244867) Posted October 1, 2019 Report Share Posted October 1, 2019 Topsky not able to move the radar menu any more also last checkbox look like its below the fields confirm not faulty on your side? Link to comment Share on other sites More sharing options...
Juha Holopainen Posted October 1, 2019 Author Report Share Posted October 1, 2019 I suppose they are examples of the unwanted behavior. Should be easy to fix, I’ll get it done by tomorrow. Link to comment Share on other sites More sharing options...
Juha Holopainen Posted October 2, 2019 Author Report Share Posted October 2, 2019 The radar menu issues are now fixed, please re-download the plugin. The only changed file in the package is TopSky.dll with timestamp today at 5.12UTC 1 Link to comment Share on other sites More sharing options...
Recommended Posts