Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 02/05/21 in all areas

  1. Using /t/ does not indicate whether or not you are a bad pilot, neither does MSFS. Pilot competency is a whole other topic, which has already been solved by other networks that have a paywall barrier to filter out straight up you know, bad bad, pilots or just people who are new and unexperienced with subjects. For the case of VATSIM, it is a free platform and therefore the burden of crappy (as in rude, incompetent, and "you don't tell me what to do) and unexperienced/casual pilots will remain and be a part of VATSIM for as long as it exists. /t/ on the other hand affects efficiency no matter what. It is not the pilots fault, nor the fault of how good the pilot is. It is in regards to the workload of a controller, and the inconvenience it sets for other's convenience. By restricting /t/, no pilot is being stripped of his her or its right (we are inclusive here ladies and gentlemen, if a Rhino wants to be a pilot it can.) It is just changing the standard as to what people can chose when it comes to options on voice communications. They still don't have to talk, /r will remain. There is nothing stopping any pilot from using /r other than: A: they have a prejudice on VATSIM where they believe they will ruin everyone's day by not knowing the phraseology like they've been a pilot for 40 years/are not experienced enough. B: They are physically and mentally incapable of using their ears to listen to an audio message, and then interpret that message to which the point where they can reply to it and follow the directions given. If option A is the case, then this is what I would like to see eliminated. ATC communications are based off voice, not text, and to the minimum receive only will help reduce the amount of those annoying "pssh" text message noises that turn your ATC simulation experience into a "ughh I have to deal with this text pilot now while I'm busy working everyone else." If we as a network do not provide the option to use text only, people will not sink into the "text only first, then voice." They will go straight to voice! (or receive, depending on how confident they are,) which will only benefit the experience of all parties involved. Now, if someone falls under B, there is an exception. I will more than gladly spend the effort into writing a on point grammar clearance via text to a pilot who genuinely has no other option. I do not think this group should be excluded from the network, and under the many plans and ideas suggested in this thread, that won't happen. The issue lies more in allowing people to see text-only as an opportunity for themselves, when really its hurting everyone. Its hurting them by, well, turning them into text pilots, and its hurting everyone else by having to deal with them.
    2 points
  2. DME = Distance Measuring Equipment. Associated to a VOR or ILS station.
    1 point
  3. You are correct for the first one. "Descend FLXXX level by [WAYPOINT]" means be at this level when you are passing [WAYPOINT]. If you are told "Descend FLXXX level abeam [WAYPOINT]" this will mean that you are on a heading, but the controller wants you to be at that level when you sort of reach the waypoint while flying the heading (you can still see the waypoint on the navigation display and eyeball the descend via that or use a formula to calculate your descend rate depending on the distance to the waypoint. If you are given, for example, "Speed 160kts until 4 DME" means to maintain this speed until you pass the 4 mile mark on the ILS. Edit: Trevor beat me to it.
    1 point
  4. The first instruction was "when ready, descend FL120 to be level by TNT" So yes, at your TOD point descend be level 120 at or just before that point (not descend now and be level 40 miles before as some people do! 🙄😂 ) His second instruction was: "speed 180 until 10DME" it then sounds like he wasn't sure whether it was read back correctly hence why he asked you "just confirm it's 10DME, 1 0 DME"
    1 point
  5. Passwords used to be numeric only until a point when VATSIM decided to change passwords to be more secure. While this change initially only affected new members, now, whenever a VATSIM member self-reactivates their account, or chooses to use the "forgotten password" function, their old password is changed to a new one, following the security standard VATSIM has implemented after above described change. New VATSIM passwords consist of numbers, as well as upper and lower case letters.
    1 point
  6. If you only get that error from the voice server then it can only be an incorrect capitalisation of your password. Please retype it character by character, making sure that all lowercase and uppercase characters are correctly placed.
    1 point
  7. Dustin's comment was about controllers, not pilots, being mandated to maintain constant watch. (7110.65 is essentially the US ATC bible.)
    1 point
  8. https://vpilot.rosscarlson.dev/Documentation#dot-commands
    1 point
  9. I ran an airshow in 2005, 2006 and 2007 without breaching ANY Vatsim regs and that was Rule 1: We don't breach anything. It can be done and it was very successful but does take some doing. Prior to the first one a lot of work went into how to make sure Rule 1 was applied, all reviewed with the Divisional staff, and we had the then DCRM and SUPs controlling to ensure we kept in order. Gunnar will probably remember these. You do, however, have to be prepared to encounter the self-appointed Fun Police and their wooden spoons for agitating brown stuff 😄😄
    1 point
×
×
  • Create New...