Jump to content

Daniel Roesen

Members
  • Content Count

    34
  • Joined

  • Last visited

Community Reputation

1 Neutral

Recent Profile Visitors

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

  1. This was certainly not picking on you, we have just recently resectorized/changed sector names and station IDs due to real world changes, after your update release. As far as I understood Jonas is working to get stuff on GitHub set up for actual new release and also having the client pull sectorization data right from GitHub - so we can update directly on GitHub and get updates "live".
  2. I have observed the same problem with the same pilot (well, callsign) as well.
  3. EDMM is e.g. broadly broken/outdated, even in the update Quotescoop data set. 🙂
  4. While Qutescoop is also the tool I use, it's still unable (like all the other tools I'm aware of) to remotely accurately display the complex sectorization structures we sometimes have in some vACCs. VATSIM lacks a central official sectorization database as "single source of truth" together with the required ruleset about which station covers which sector (in dependence of other stations (not) online) for all the tools out there to use, and a tool that's able to display the sitation in 3D, not just 2D. At least able to "think" 3D and state the right controller derrived from the active sect
  5. Hi, when a forum user subscribes to thread updates by email, that notification email is sent as MIME content-type "multipart/alternative" with a plaintext and a HTML version. The HTML version is "OK" (if you think HTML for email bodies is OK...), but the plaintext version that contains only a link to the new post in the thread has a broken link: The problem is that the parameter separator "&" is being HTML-encoded as "&" which is just plain wrong for an URL. Removing the bogus "amp;" makes the link work correctly. I guess you cannot directly do something about i
  6. The problem is not moving to ICAO format (quite the opposite - FINALLY), but doing so grossly uncoordinated without any public announcement with a reasonable pre-warning time. That gave a lot (most, almost all?) of developers zero chance to prepare their software for that change. And we now have to live with the fallout: etc. That was unnecessary. It's not that it was all too urgent now to rush this out in hush-hush mode... or am I missing something? "The real system"? Which one? The world is more than "the USA", even if VATSIM continues to ignore that little d
  7. BTW, I've found a page describing the underlying functionality, and how to prevent auto-repair for the demo configs... by separating them out into another "Feature" definition. Hope that helps: https://www.advancedinstaller.com/user-guide/qa-self-healing.html
  8. As a new EuroScope user, I wanted to remove all the demo config cruft in %home%\Documents\EuroScope to have a clean slate, and stumbled over the same behaviour. The mistake seems that those demo configs are declared being part of the "software installation" when Gergely creates the MSI package, so considered "vital" by the windows MSI installer self-repair functionality. The EuroScope start menu link is not directly pointing to the .EXE file but to a virtual application registration (that's via registry as far as I found out - not a windows admin/dev), and that makes clicking the start me
  9. This has changed, it's "super": http://www.faa.gov/airports_airtraffic/air_traffic/publications/at_notices/media/N7110.464.pdf EDIT: sorry to resurrect this thread, but "for the archives"... Best regards, Daniel
  10. If you are cleared onto the STAR (either by filing it or by being [Mod - Happy Thoughts]igned by ATC enroute) you may not fly farther than this point, unless comms failure happens. It's the limit of your clearance. Best regards, Daniel
  11. There are slight differences in definition, my usage of QNE was more colloquial indeed: I was following this "common usage". Best regards, Daniel
  12. Actually, it's QNH 1014 which starts the FL60 regime, not 1013. Bites me everytime. Thinking is prolly: "yeah, at 1013 QNH=QNE, but if QNH changes to 1012, all my aircraft on 5000ft and FL60 had 1000ft separation, now suddenly don't anymore". I guess the 1 hPa is kind of a "buffer". But in general, Martin's perfectly right. Altitude = "x feet on local QNH", flight level = "x feet on 1013/29.92". If the controller sends you to an altitude, dial in the QNH/altimeter he gives you. If he sends you to a flight level, use QNE (standard 1013hPa/29.92"). Best regards, Daniel
  13. Sorry Antonio and thanks for getting back to me. Was burried in other stuff to handle and will write the email when I'm finished controlling EDMM_N_CTR. Again thanks for your help! Best regards, Daniel
  14. Thank you Antonio! Will send you an email within the next few hours with the details. Best regards, Daniel
  15. Hi, can anyone refer me the names and email addresses of the persons to contact at Peru FIR (SPIM) and La Paz FIR (SLLF) to kindly request ATC coverage in SPIM/SLLF for a World Tour fly-out/enroute? On our inbound leg to SPIM I've mailed (for SPIM) Luís García (Events & PR) Roberto J. Duboc (FIR-Chief) without any reply. Are they still in charge? As the VATSAM homepage is down, I have no contacts for SLLF. Can anyone help out? Best regards, Daniel (VACC-SAG World Tour 2006 ATC coordinator)
×
×
  • Create New...