Jump to content

Martijn Rammeloo

Members
  • Content Count

    158
  • Joined

  • Last visited

Community Reputation

13 Good

2 Followers

Recent Profile Visitors

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

  1. Please note that one control position can have multiple transceivers, each with its own lat/lon.
  2. Next time, I suggest you send a PM to the controller in question. Or contact him via text on the frequency.
  3. At least at EHAM, a flight plan is mandatory. And from a VATSIM perspective: I prefer pilots filing one, so that I can read what they want, instead of listening to their life-stories on a busy freq.
  4. I pick one based on my guess about the pilot's proficiency.
  5. Of course you are. However, you may expect a longer waiting time and/or delays. For example at EHAM, we use tools to prioritize booked traffic. Martijn
  6. A good set of aliases can take care of > 95% of all situations. Depending on your TAG setup, TAG manipulation also is a powerful tool. Experience and maintaining proficiency take care of the rest. Martijn
  7. Since the newer (post-AfV) betas, this no longer works, unfortunately.
  8. I hardly recognize this, although I am only aware of the situation in Western Europe. Events are always adequately staffed.
  9. 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
  10. Just out of curiosity: why do you need it? Martijn
  11. Normally, TWR will notice that something out of the ordinary is going on, and act accordingly. However, it never hurts to inform him/her.
  12. 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
  13. 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.
×
×
  • Create New...