16
General Discussion / Re: VRC Window Behavior
« on: May 30, 2018, 04:17:09 PM »
Thanks David, I think that answers my question.
K
K
Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
17
General Discussion / VRC Window Behavior
« on: May 29, 2018, 08:16:27 PM »
Hello all,
Was building a VRC profile for a position and it was coming along nicely. Then when I ran out of room on my left monitor I put the next window on the main monitor. This next window does not behave like the previous VRC windows where they come to foreground when selected, and return to background when another VRC window is selected which covers it. This next VRC window remains on top of my first VRC window at all times.
Does anyone know if this is built into VRC or is this a bug? I did not see any settings related to window behavior so I was just wondering if anyone had any insight on that.
Thanks.
K
Was building a VRC profile for a position and it was coming along nicely. Then when I ran out of room on my left monitor I put the next window on the main monitor. This next window does not behave like the previous VRC windows where they come to foreground when selected, and return to background when another VRC window is selected which covers it. This next VRC window remains on top of my first VRC window at all times.
Does anyone know if this is built into VRC or is this a bug? I did not see any settings related to window behavior so I was just wondering if anyone had any insight on that.
Thanks.
K
18
News / Re: Daniel Hawton VATUSA 6 announces retirement
« on: May 24, 2018, 01:57:04 PM »
You have improved VATUSA immensely and we are all the better for it. Thanks for all that you have done for this community.
K
K
19
The Control Room Floor / Re: There are two types of controllers...
« on: May 22, 2018, 12:40:02 PM »Just a suggestion..... some of the choices in the thread seem to be to be on either end of the spectrum (too verbose or strictly 7110.65). That strikes me as a false choice, at least some of the time.
What I often consider is deploying phraseology that may reveal which flavor of pilot I might be dealing with. So.... for the original example Shane gave in his original post, I might try: "DAL2168 Heavy, Minneapolis ground, runway 30L, taxi via A; runway 17 available on request". So far as I know, this is compliant with 7110.65 (or pretty darn near it!).
A pilot in the "less experienced" category, will either ignore it or possibly ask a question (sometimes in chat to avoid being embarrassed by asking) affording a learning opportunity. A "hardcore realism" pilot can take the hint and make the request, which would lead to a 7110.65-compliant exchange about the amended routing etc. which an experienced pilot will be grateful for as well as it increases immersion.
I deploy this strategy in other circumstances as well. For instance, in low traffic situations, I know Portland Departure in real-world often gives direct to the fix on the SID that precedes the transition (e.g. "direct MINNE" for the MINNE5, or "direct CHISM" for the CASCD2). For new VATSIM pilots, giving them this as they climb out can result in confusion, or (worse) accepting the short cut but not actually flying it. So, again, I may say (or ask Tower to say before h/o) "DAL2168 Heavy, runway 16L, cleared for takeoff, [expect direct CHISM, or direct CHISM available on request with Departure]." See what sort of reaction I get and deal accordingly.
I find this strikes a decent balance between the various interests and considerations discussed in this thread. I've received a reasonable amount of feedback both from experienced and new pilots alike that makes me believe this approach is appreciated by both types from a "customer service" perspective as well.
Frank
Very good points Frank. I would agree that what you described seems to be a nice bit of compromise, but still efficiently so.
+1
K
20
The Control Room Floor / Re: There are two types of controllers...
« on: May 21, 2018, 12:12:08 PM »Conceding this is a volunteer network but regardless we should do our best to do as good of a job when we are online as we can. Whether you are flying or whether we are controlling. Yes there has to be some give and take and while we are not running a grocery store the word customer service comes into play when a controller does a good job and does everything that he is trained to do to mitigate an aircraft's departure and arrival to an airport.
On the flip side, I think the word customer service should apply to pilots as well. I think that pilots should strive to become better pilots. Learning their airplane, learning procedures. learning how to properly program their FMC are all parts of this. The issue at hand is there is nothing that requires them to learn these things.
A fair point.
K
21
The Control Room Floor / Re: There are two types of controllers...
« on: May 20, 2018, 03:19:46 PM »We are volunteers for the pilots plain and simple.
From my point of view, I don't volunteer my time to the pilots, I volunteer it to my ATC hobby. If you want to view it that way, by all means, but I don't. Others have also attempted to imply that opinions similar to yours are the only lens by which to view the network through. I reject that completely.
Again, if you want to view what you do as "servicing the pilots", go ahead and do that, but that's not how I view it and others shouldn't attempt to foist their more accommodating/servicing view of things onto others as if their way is the only way to view things.
##########################################################################
Discussing what I wrote above, is still totally off topic from what Shane originally posted. I'll just go ahead and say, yes, I would rather have the shorter and concise phraseology over more words. I don't think that means I "don't give a darn about the pilots" either. I think it just means I like to do things a little more by the book than you do Cole, and you know what? In the grand scheme of things, that is probably just fine. You can have your version, and I can have mine.
Also, quoting you here,
Quote
it's simply a service they use because it is enjoyable. The moment the service becomes unenjoyable, they will be onto the next bigger brighter service.
I don't think any part about using concise phraseology or performing the duties that, under normal circumstances, a controller would perform on the network, constitutes an "unenjoyable" experience on the network. However, even if it did I have no control and nor do other controllers, over what or when or if pilots decide to fly. If they decide the network is not for them, that is their prerogative, not mine.
*********************************************DISCLAIMER:
This obviously does not mean I don't want them to fly on the network. I would be more than happy for as many pilots as practical fly on the network if that is what they so desire.
K
22
The Control Room Floor / Re: There are two types of controllers...
« on: May 20, 2018, 12:25:29 PM »
We are providing a service. ATC exists to serve pilots, not the other way around :-)
i've heard multiple times where a pilot may request runway 17 but if 30L is the norm than that request would be denied even if traffic permitted. If traffic permits and a pilot wants a opposite direction approach or departure why not grant it?
These two quotes right here are prime examples of the pilot bias that has been growing within the division over my 12 years on the network and why senior controllers are leaving in droves.
These quotes completely ignore the fact that the controller has put hours of study into basic theory, procedures, and technique for no pay. They have done so out of a desire to learn Air Traffic Control and be able to practice that skill on VATSIM. A controller derives his enjoyment from working his airspace efficiently and providing a realistic simulation of procedures followed by pilots and air traffic controllers everyday around the world.
In layman's terms, a controller want's to work his airspace the way it is supposed to be worked! That's what is fun for them.
So yes, I'm going to use proper phraseology when I control. No, I'm not going to give you your choice of runway immediately nor acquiesce to your ridiculous deviation request right off the bat regardless of if I have 1 airplane or 100 airplanes. I'm going to assign per my SOP and if that doesn't work, we will find a mutually beneficial way of getting you from A to B and I'll use my best judgement if we need to deviate from Plan A and find a way that works.
I'm going to be the Air Traffic Controller, You're going to be the pilot. (We're not Air Traffic Suggesters)
I'm going to move you as expeditiously through the NAS as I can. You're going to follow my instruction unless it causes a safety issue or is not possible, then it's your responsibility to say unable and we find another way.
I'm going to enjoy providing Air Traffic Services to pilots on VATSIM. You're going to enjoy flying on VATSIM with ATC.
I won't control if it's not enjoyable. You won't fly with ATC if it's not enjoyable.
I can't provide ATS unless you fly. You can't have ATS unless I control.
See, it's a two way street. We're in this together and we both need to derive enjoyment from it for the network to survive.
+1M
I couldn't have said it better myself.
23
The Control Room Floor / Re: Which ARTCC to join?
« on: May 09, 2018, 10:58:35 PM »In my experience, every ARTCC has its own culture. It is difficult to judge an ARTCC's culture until you actually go there and experience it for yourself. Some ARTCCs are very different than others and the only way is to experience them. Don't like where you are? You can transfer to another ARTCC 1 time every 90 days, so you have that option available to you.
K
And you could always informally hang out before you commit to 3 months with them.
Of course.
K
24
The Control Room Floor / Re: Which ARTCC to join?
« on: May 09, 2018, 10:35:08 AM »
In my experience, every ARTCC has its own culture. It is difficult to judge an ARTCC's culture until you actually go there and experience it for yourself. Some ARTCCs are very different than others and the only way is to experience them. Don't like where you are? You can transfer to another ARTCC 1 time every 90 days, so you have that option available to you.
K
K
25
The Classroom (Controller Tips) / Re: The Nature of Air Traffic Control
« on: May 02, 2018, 03:07:58 PM »Furthermore, there is one very important aspect we cannot forget...teamwork. No matter what the culture at your ARTCC may be, you're only as good as the controller next to you. Instead of berating a guy for not giving you enough room between successive departures, take a second to educate and turn the experience into a teachable moment.
Well said.
K
26
The Control Room Floor / Re: Entering airspace of En-route controllers
« on: May 02, 2018, 02:47:16 PM »Quote
If the network were to require pilot training, the network would die.
That assertion is unfounded and baseless. We establish a minimum competency for controllers and yet we do still receive new or returning controllers who rise through the student ratings all the time. The same can be established for pilots. I'm not advocating for the level of competency we require for controllers, but something really basic to establish competency of pilots who do indeed want to fly in a somewhat realistic fashion is an achievable thing. You won't see me advocating something like "all pilots should have to have all 5 pilot ratings before flying on the network." However, I would support something along the lines of, "all pilots should be able to pass the P1 test before flying on the network." I've taken the P1 exam, it's really basic stuff every VATSIM pilot should know.
Quote
But how can you not see controlling as a customer service activity? Controllers don't exist without pilots. On the other hand, the reciprocal isn't true.
Because they're not my customers. They volunteer to fly in my airspace. I acknowledge the symbiotic relationship of pilots and controllers but do not view that as me being beholden to them. They volunteer their hobby to me, and I volunteer my hobby to them. That's it. No customer service activity required.
K
27
The Control Room Floor / Re: Entering airspace of En-route controllers
« on: May 02, 2018, 05:17:04 AM »I just don't understand the "it's the pilots responsibility, end of story" mentality.
Pilots aren't required to undergo training. Pilots aren't required to know what any of the VATSIM tracking tools are. Expecting them to know where enroute airspace is may be easier than others, but it's a joint responsibility. It's a game and our job to provide a customer service -- we work for the pilots. If you're doing ATC, you should want to do that, and if you want to do that, you should be willing to send a contact-me.
And if you want to talk sub-enroute airspace, those boundaries are not documented anywhere for a pilot, so expecting them to know where your approach airspace starts is an unrealistic expectation.
I don't know about others, but I really don't view my controlling as a "customer service -- we work for the pilots" type of thing whatsoever. I view it more along the lines of "I am online covering this location, come fly if you want... or fly in other locations, that's fine too." I'm happy to have pilots fly where I control, but I don't do it to service them. I do it because I enjoy controlling. The same reason they all fly on the network: because they like to fly, not in order to give me traffic.
I don't agree with your assertion that "you should want to do that". It's not about whether I want to do it or not really. The fact is I DO do it every time I'm online. Speaking strictly for myself, what I am saying is that I prefer if pilots be aware of who is and isn't online and where they are in relation to that. I do it all the time when I am flying, and it has yet to prove difficult for me. I agree with what Dhruv said above, 50NM or leaving the flight levels is good enough for contacting an approach controller.
Also, "Pilots aren't required to undergo training." No, but maybe they should be. There is a rather large disparity between what pilots are required to know and what controllers are required to know on this network.
K
28
The Control Room Floor / Re: Entering airspace of En-route controllers
« on: April 30, 2018, 03:29:38 PM »Josh -- just to jump on the bandwagon, yes, it's the pilot's responsibility, as per the Code of Conduct. Many controllers will send a Contact-Me but that's a courtesy and shouldn't be relied upon as an expectation.
+1
29
The Control Room Floor / Re: Entering airspace of En-route controllers
« on: April 30, 2018, 03:13:22 AM »
When I am on center, I much prefer the pilot to call in even if I am busy. As long as they give a VOR or Airport they are close to, then I can find them quickly. "AAL123 with you FL320..." Doesn't help me much if you're coming from Unicom. If you are coming from another center or approach controller, I know you're coming before you get to me, so in that circumstance the aforementioned is acceptable.
As a pilot I also usually try and be aware of if there are other centers on close by using vattastic. If someone comes online, I will usually take the initiative to check in with them.
K
As a pilot I also usually try and be aware of if there are other centers on close by using vattastic. If someone comes online, I will usually take the initiative to check in with them.
K
30
General Discussion / Re: Keep Port Open
« on: April 14, 2018, 12:49:17 AM »This boils down to the fact that NAT sucks. It is a hack that was implemented to stretch the lifetime of the IPv4 address space. Most of the time, it works great, but things like this show its flaws.
Hope this helps someone understand
Super interesting post.