Jump to content

Lenny Colton

Members
  • Content Count

    31
  • Joined

  • Last visited

Everything posted by Lenny Colton

  1. Is the (REST?) API for this freely accessible?
  2. Would it be possible for data regarding all of the frequencies tuned by an aircraft to be added to the Status API? I've noticed that the AFV Map already has access to this data, so am I missing something?
  3. I'm also having this issue. Whenever the return will include the user's current connection, the API returns error 500. The main time I encounter this problem is when I attempt to pull all of a user's stats in one go. A workaround is to specifically request a position which the user is not currently connected to, which works fine. However, there is no way to see what someone is currently connected as (except through the status API, which does not sort/filter by CID).
  4. Solved. It turns out that putting a colon in my sector file name wasn't wise. Since the servers use a colon-delimited data format, my sector file was reading as entries (instead of just 1), meaning that the response had 1 too many entries, which caused an error. The server's way of handling that particular error appears to be booting me off without an error message (or maybe there was just an unhandled exception, logged server-side only?)
  5. I started experiencing an issue when connecting to VATSIM, today. Running v3.2a(r22), when I attempted to connect to VATSIM, EuroScope connected, then immediately disconnected (in the fashion it does when attempting to log in with a duplicate callsign or invalid login details). However, the only server message was the standard "Welcome to VATSIM", with no error or other information given. Likewise, EuroScope's internal message box did not contain any information and no errors appeared. Nothing changed between my last successful connection (EGKK_F_APP, last night) and this one. I initially
  6. Just to confirm, have you installed both the x86 and x64 packages?
  7. Can you just verify that you have the Visual Studio 2015, 2017, 2019 redistributable (x86/x64) installed? It can be found here: https://support.microsoft.com/en-gb/help/2977003/the-latest-supported-visual-c-downloads
  8. Yep, the airports.txt is open for contributions. Bear in mind that due to how VATGlasses is designed, any new airports need to be added to the end, rather than put into numbering gaps. I'll take a look at the character set issues and get back to you. Sounds more like an issue with the parser than with VATGlasses, itself.
  9. Version 1.2 of the Euroscope Sector File Parser has now been released and is available through the GitHub repository. Changelog: Fixed bug which could cause crashes in locales which do not use the “full stop” (.) as the decimal separator. A big thank you to @Adrian Bjerke for reporting the issue and working with me for several weeks as I tried to solve the errors which he was experiencing.
  10. Version 1.2.0.1 has now been released and is available at the website. This version contains major bug fixes. Changelog: Removed unnecessary requirement for users to be running Windows 10 Build 10240 or higher. Any computer running Windows 7 or higher is now supported. Fixed bug which could cause crashes in locales which do not use the “full stop” (.) as the decimal separator. Thank you to @Torben Andersen and @Andrew Crowley 1326167 for reporting that Windows prevented their systems from running VATGlasses. (Fix 1) A big thank you also to @Adrian Bjerke for reporti
  11. Hi Torben, I found the offending setting, which unnecessarily set the minimum OS to Windows 10 build 10240. The next release will contain a fix to allow Windows 7 and 8.1 users to run VATGlasses.
  12. Aha! I have an idea of what may be happening. Just to confirm, do you use a comma (,) or a full stop/period (.) as the decimal separator, in Norway? For example, would the result of 21 divided by 2 be 10,5 or 10.5?
  13. Hi Torben, What version of VATGlasses have you got installed? Do you get any error messages when you try to run it?
  14. The data file updater in 1.1.1.0 had some issues which caused it to crash on every use. Could you please retry with 1.2.0.0?
  15. Version 1.2.0.0 has now been released and is available at the website. This version contains major bug fixes and new features. Changelog: New Features: Implemented advanced sector filtering, based on altitude and owning (logon) callsign. Implemented advanced pilot filtering based on altitude and departure/arrival airport. Alterations: Changed search/filter buttons to image buttons. Altered behaviour when attempting to open multiple instances of a single dialogue box. Removed silent crash behaviou
  16. Hi Adrian, That error appears to be different to the previous one. The error message given means that the system couldn't find the airports.txt file. Usually this is just a spelling/typing error. Could you please check the file path and try again? A crash during the "Loading Files" phase suggests that file was corrupted or not found, especially since the Locale change had no effect. Could you please post a screenshot of your AppData\VATGlasses\data folder? I'm going to set the next version of VATGlasses to display error messages during loading, rather than close silently when an
  17. Version 1.1.1.0 has now been released and is available at the website. This version contains minor bug fixes and improvements. Changelog: Fixed bug which could prevent sectors from displaying on click.. Changed data file parser to remove whitespace from the start/end of Sector names/descriptions and Controller voice callsigns. This refers to the in-built parser which loads VATGlasses files, not the sector file parser. Fixed bug which could cause crashes on the next automatic reload after the reload button was pressed. Implemented software-enforced m
  18. Hi Adrian, I've identified (and hopefully fixed) a few possible causes of your issue in previous releases, but something might not be right. Can you confirm what language/dialect/keyboard layout your computer is running? Does the issue resolve if you set your computer to English (UK) with the UK keyboard layout? Can you also confirm that your C:\Users\<username>\AppData\Roaming\VATGlasses\data folder looks similar to this one (the presence of "currentrunways" and various "fav" files doesn't matter)? With regards to the parser, I recently pushed an update to GitHub, due a f
  19. Hi Adrian, That error suggests that one of your airport entries has a corrupted latitude or longitude value. You can use one .sct/.ese combo for the whole package, so long as it contains all of the data. With regards to VATGlasses not starting, which version are you running? Have you updated the data files since you first installed?
  20. Hi Adrian, For the airport file path, you can use the airports.txt file from either the master branch of the repository or the latest data release (as pushed to VATGlasses clients). In terms of the FIR code; whilst the FIR ICAO code is generally the most sensible option, you can technically use any identifying string (though I haven't tested how VATGlasses would respond to a spacebar or other special characters). The FIR code is generally the best idea, as it's short and unique, but if it works better to use ENOR, that should work fine. The same can be said for creating 4 separate fi
  21. Aaaaand it broke within 5 minutes... Version 1.1.0.1 has now been released and is available at the website. This version contains a major bug fix. Changelog: Moved all data files to appdata folder. Fixed bug which prevented data files from being updated after initial download.
  22. Version 1.1.0.0 has now been released and is available at the website. This version contains a major bug fix and new features. Changelog: Removed VATSIM Status API version check. Added option minimise to system tray. Double-click tray icon to restore window. Added top-down airport control support. Updated airports.txt file format.
  23. Welp, that broke quickly...Version 1.0.1.0 has now been released and is available at the website. This version contains minor bug fixes.Changelog: Fixed bug where Filter button appearance did not change between light and dark mode. Fixed bug where settings were not saved after the program was closed. Moved all current runway/favourites files to %AppData%\VATGlasses Fixed issue where these files could not be written as the user had read-only access to C:\Program Files (x86)\VATGlasses.
  24. Version 1.0.0.0 has now been released and is available at the website. This version contains major bug fixes and new features. Changelog: Fixed dark mode on search results panel. Added detailed search filters. Fixed bug which caused crashing on start if “data” directory deleted. Introduced installer package. VATGl[Mod - Happy Thoughts]es is now distributed through an installer file. Simply run the installer file to install/update your copy of VATGl[Mod - Happy Thoughts]es. On first run, the data file updater will offer a new data file package. You must allow this to
  25. Version 0.5.3.0 has now been released and is available at the website. This version contains minor bug fixes and major new features. Changelog: Added Dark Theme Added Zoom Mode Control Fixed Zoom In/Out Buttons Softened FIR Boundary/Label Colours
×
×
  • Create New...