Jump to content

Dustin Rider

Members
  • Content Count

    44
  • Joined

  • Last visited

  • Days Won

    1

Dustin Rider last won the day on March 2

Dustin Rider had the most liked content!

Community Reputation

13 Good

Recent Profile Visitors

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

  1. Well I'll be. Thank you for posting the solution here because that would be a challenging solution to find on ones own.
  2. There is a discussion in this thread regarding this topic.
  3. I agree with the general sentiment of the thread in that this is such a small issue that there really is no reason to divert resources to it. As Robert said above, pilots call various ATC facilities by the wrong name, even after being told the name of the facility by the transferring controller. There are plenty of resources already available to pilots to figure out the proper callsign, from the controller's info to my personal favorite, the charts.
  4. A lot of payware aircraft have transmitter and receiver selection functionality that most pilot clients respond to. To put it a different way, are you sure that you have a transmitter selected in the aircraft itself? Usually somewhere on the center pedestal there should be a small audio selection panel where you would select where the aircraft mic is to be routed: COM 1, COM 2, PA, etc. Make sure you have either COM 1 or 2 selected.
  5. From the looks of that screenshot, you don't have a transmitter selected in the comm panel of your aircraft. To select a transmitter, you'll need to click one of those black square buttons above the respective volume knob. Once you do that, you should see "MIC" lit up on the button and the associated frequency lit up on xPilot.
  6. The best solution I've found so far is to make sure you are running vPilot as an administrator. I think there must be some permission that is only granted in this mode that allows vPilot to look for a keypress when it's not in focus.
  7. This is a great question, and the relatively short answer is no: don't file departure and arrival runways in your flight plan. For one thing, it clutters up the route string of your flight strip, and for another, it can be made irrelevant the second the wind shifts and favors a different runway--especially if you're on a four-hour transcontinental flight. At towered airports, ATC will assign you a departure or an arrival runway and approach, all of which is covered in the ATIS, if one is available for your departure and destination airports. At non-towered airports, ATC expects that the p
  8. Well, yes and no. You could lose the ability to use voice communication, but we have text as a backup. Even if all of your radios go dark in the cockpit, you should still be able to send and receive messages through your pilot client. Simulating radio failure on VATSIM is sort of pointless, though, since the whole idea of the network is to work with human controllers.
  9. The short answer is no. The elongated answer is for departures or arrivals to towered fields, you are supposed to call the facility having jurisdiction over the airport. If you departed BJC up north, for example, you would call BJC tower, or Denver approach, or Denver center. However, since CO4 is non-towered, so long as you remain outside the Class C airspace, you can maintain VFR and operate as desired. Fun fact: Look at KFNL. Notice how the airport is blue (denoting a towered airfield) but lies within a Class E surface area. There is a portable tower in operation at that airport
  10. Our individual experience notwithstanding, what I'm saying here is that from my point of view as a controller, if you are on my frequency, on a discrete beacon code, and declare an emergency because you're number 2 engine just had an uncontained failure, there is nothing to be gained by squawking 7700 because I already know where you are. The only things I really need to know are your intentions and what type of assistance is needed. There are other things, like fuel and souls, but those can be obtained when time permits. To be clear, I'm not saying don't do it, I'm saying under most circ
  11. No, it's not really necessary in the real world, either under the circumstances in my previous post. I worked at a center and all I had to do was call for the sup, let them know what was going on and what the pilot's intentions were, and they'd coordinate the rest. Controller-to-controller coordination is a matter of a phone call, which is even easier if I have a D-side. If someone I'm already working declares an emergency and changes their discrete beacon code to 7700, it pops up on everyone's scope, which places an obligation to surrounding controllers and facilities to call me and ask if I
  12. If you're declaring an emergency while in communication with ATC and have already been radar identified, there really is no need to squawk 7700. The controller already knows who and where you are and will effect coordination with other facilities as needed. That code was designed to facilitate expeditious identification of an aircraft in distress when they call out of nowhere. I've had a handful of pilots declare (or ask if they can declare) an emergency and I'll accommodate if I can, which is most of the time.
  13. Most of the time I give it a few minutes to see if they were disconnected due to a brief internet or network issue and might be back. Since vERAM keeps the datablock until I drop track, if the plane comes back online, it should auto-acquire again and I can re-establish radar contact. However, more often than not, once the aircraft disappears it's usually for good and I just drop the track anyway, since I can only assume they CTD, had to disconnect for some reason, or had more significant internet interruptions. The only thing that's helpful from my perspective is that if you have to inten
  14. The only thing I can think of is to double check your audio device settings in vPilot (or whichever pilot client you're using). Make sure you have the proper output device selected on the pilot client. For example, on mine, my flight sim sounds are going to my external speakers and I use an Mpow headset for voice comms. Make sure you have the volume turned up on whichever device you're using for ATC comms--check the device itself for volume control and you might have to go into the Windows audio mixer and select the intended device and adjust volume. Lastly, as one of the first commenters on t
  15. Ah, mistakes are the most effective way of learning in my opinion, and I've learned a lot on this network.
×
×
  • Create New...