Jump to content

Martijn Rammeloo

Members
  • Content Count

    149
  • Joined

  • Last visited

Community Reputation

6 Neutral

2 Followers

Recent Profile Visitors

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

  1. I hardly recognize this, although I am only aware of the situation in Western Europe. Events are always adequately staffed.
  2. Right click on the next controller's callsign in the TAG. Also (at least at Dutch VACC), the frequency will replace the next controller's callsign in the TAG automatically 10 miles (ish...) prior to COP. It will only change back into the callsign when the next controller has accepted the TAG. Martijn
  3. Just out of curiosity: why do you need it? Martijn
  4. Normally, TWR will notice that something out of the ordinary is going on, and act accordingly. However, it never hurts to inform him/her.
  5. Hi Ross, I see your point, but missing both a pilot call and a coordination message at the same times causes more damage in my opinion. That is my use-case after all: when an APP controller wants to talk to me on a CTR position, it MUST be important and urgent. If coordination would take longer (hardly ever...) I could simply press the mute-button again. I think that the '15 seconds solutions' is a great idea. That would prevent users forgetting to unmute. So, if a pilot doesn't get a response, he can be assured that there is a real reason for it. Suggestion: a small scale t
  6. I am aware of the risks, but to be honest, at times when I need this feature, a 10-15 second silence would raise enough suspicion to check if there's something wrong with the audio. Some time ago, I experimented with a Virtual Audio Cable in order to achieve the same result. Although it worked OK, the setup was a hassle: plugging my headset in a different USB port forced me to do the setup again. A left/right solution would be good for me as well, but routing audio to my speakers would make my wife less-than-happy :-). Until then, a simple mute button would be the quickest solution.
  7. I think it would be a great feature to have a mute-button in the AvF client. As a controller, I 'sometimes' need to coordinate via Discord, and muting pilots for a short time would make this process a lot easier. Martijn
  8. So do I. Parsing the JSON has been working for ages (in PHP), but all of a sudden json_decode returns a string instead of an array. Update 1530Z: It seems as if the data is encoded twice on the VATSIM side. Because, if I decode it twice, everything works fine again. $total_results = json_decode($string, true); // $string is the curl return $total_results = json_decode($total_results, true); // <- This line was not needed until yesterday @Nestor Perez Martijn
  9. Hi Néstor, According to the Q4 Tech Blog, the 'JSON-URL' will become: https://data.vatsim.net/v3/vatsim-data.json Is it OK to hard-code this URL in applications, or do we still need to parse the status URL, as per your message above? If so, would it be possible to replace/add the status information in a JSON format, instead of a text file? Parsing a text file seems a bit outdated 🙂 Kind regards, Martijn
  10. This is a typical 'VATSIM-ism'. In this case, I would simply ask TWR asap if it is OK to use 25R for landing. I cannot imagine strong objections. Any - somewhat experienced - controller knows that the first few minutes after connecting are 'clean-up time'. Forcing pilots to make any last-minute changes hardly ever helps expediting this process . In my experience, almost everything is possible as long as you talk to each other. Cheers, Martijn
  11. @Andrew Ogden: I hope you check the pilot's CID (and destination), and not only the callsign. During outbound events at EHAM, a script checks whether a flight is booked or not, in order to prioritize slots. And sometimes, we notice that none-booked flights try to 'hijack' event callsigns. In vain, obviously :-)
  12. Hi Bruno, No, unfortunately not. In the post you are quoting, I try to explain why. Kind regards, Martijn
×
×
  • Create New...