Jump to content

Lenny Colton

  • Content Count

  • Joined

  • Last visited

Community Reputation

3 Neutral

About Lenny Colton

  • Birthday May 10

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Yep - you can definitely do this. For some holds, we're always happy to waive the speed limits on request - especially for distance-based holds. This would include TIMBA (within reason) for me, at least. However, there are some time-based holds which are too close together for us to do that. You may also find that the speed limit prevents you from entering another controller's airspace. TL;DR - Never be afraid to ask, but please don't be surprised if the answer is no.
  2. As a controller, I would just like to say: please PLEASE do not use the published initial approach procedures (in the UK) unless specifically issued with a transition or similar. It really makes things difficult for us when more aircraft enter the approach sector than expected! Holding procedures to be followed are those on the STAR chart. If you reach the end of your STAR (WILLO/TIMBA in this case - though this applies to all UK airports) and have not received further instructions, you should hold as published, until advised. We generally remind you to hold, but you should still hold in
  3. My apologies, I hoped that they would aid the description. 🙂
  4. LTC_S_CTR is basically the LON_S_CTR lower sector (FL215 and below, though some areas towards the edge of LON_S_CTR are not part of LTC_S_CTR. Headline airports: Heathrow, Gatwick, Solent (Southampton and Bournemouth) and Thames (City, Biggin, and Southend). LTC_N_CTR is a much smaller sector, covering the rest of the London TMA (the part which falls beneath LON_C_CTR) at FL215 and below. Headline airports: Essex (Stansted, Luton, and Cambridge) LTC_E_CTR (East - NE of London) and LTC_C_CTR (Midlands - NW of London) are not routinely opened on VATSIM but both fall under LON_C_CTR. An
  5. Is the (REST?) API for this freely accessible?
  6. 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?
  7. 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).
  8. 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?)
  9. 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
  10. Just to confirm, have you installed both the x86 and x64 packages?
  11. 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
  12. 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.
  13. 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.
  14. Version 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
  15. 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.
  • Create New...