Jump to content

Would ATC accomodate FS2020 limitations?


Recommended Posts

So, after about a dozen flights on the FS2020 A320Neo ...

1. The aircraft is only able to follow a normal flight plan when it is entered from the World screen.

2. Customizing a flight plan mid flight, or even something as simple as entering a Direct waypoint will not work, most of the time.

3. VNAV will not follow airspeed nor vertical restrictions.

My question is... if an ATC sees a pilot who is stating FS2020 on the flight plan, would she/he accomodate to that reality? I.e., if I plan for a specific departure or approach, not giving the instruction to deviate much from it?

Vectoring, speed and altitude instructions are OK specially on arrival, but then never ask me to return "as planned" after you made me deviate!

And before you answer, remember both Asobo and VATSIM very proudly announced FS2020 support from day 1.

 

 

Link to post
Share on other sites
5 minutes ago, Diego Vasquez said:

1. The aircraft is only able to follow a normal flight plan when it is entered from the World screen.

Put unable SID/STARS in your remarks and file a flight plan with out them.

 

5 minutes ago, Diego Vasquez said:

3. VNAV will not follow airspeed nor vertical restrictions.

Use V/S and manage your aircraft your self, you are flying the plane. Revert back to basics, 3 x FL / 100 to calculate TOD.

This is not a problem, vatsim has been around longer than the first FMS equipped aircraft for FS. People who can actually control the plane using raw inputs will be better pilots than those that constantly rely on FMS/VNAV/LNAV, my pet hate as a controller is having a pilot blame their inability to follow instructions on the FMC.

Kirk Christie - VATPAC C3

VATPAC Undercover ATC Agent

Worldflight Perth 737-800 Crew Member

956763

Link to post
Share on other sites
4 minutes ago, Kirk Christie said:

This is not a problem, vatsim has been around longer than the first FMS equipped aircraft for FS. People who can actually control the plane using raw inputs will be better pilots than those that constantly rely on FMS/VNAV/LNAV, my pet hate as a controller is having a pilot blame their inability to follow instructions on the FMC.

Darn I triplicated content while the forum server crashed! 

The argument of "better pilots" is IMHO beyond the point, airliners are not meant to be flown regularly manually, specially long haul and the A320 can get many many miles on a single tank.

 

 

So I guess that the answer is NO, VATSIM ATC will not make any concessions for the well known limitations of the sim?

 

Edited by Diego Vasquez
Link to post
Share on other sites
1 hour ago, Diego Vasquez said:

So I guess that the answer is NO, VATSIM ATC will not make any concessions for the well known limitations of the sim?

No one actually said that.

 

VATSIM allows all aircraft regardless of their inbuilt simulator capabilities, FS2020 is an approved simulator and with it, the aircraft that come with it.

The answers given to you were to advise the controllers weather or not you could accept what they were offering. VATSIM ATC will manage you accordingly. 

 

1 hour ago, Diego Vasquez said:

The argument of "better pilots" is IMHO beyond the point, airliners are not meant to be flown regularly manually, specially long haul and the A320 can get many many miles on a single tank.

Thats fine in the real world where things work, you are in the simlator environment and things like that are not working as they should be, if you wish to fly the aircraft on the network, then learn to operate it in a way that you can follow instructions given to you, if you aren't willing, wait untill a suitable aircraft has been released, or dont fly.

Edited by Kirk Christie

Kirk Christie - VATPAC C3

VATPAC Undercover ATC Agent

Worldflight Perth 737-800 Crew Member

956763

Link to post
Share on other sites
1 hour ago, Diego Vasquez said:

And before you answer, remember both Asobo and VATSIM very proudly announced FS2020 support from day 1.

It was supported from day 1. The lack of VNAV capabilities has nothing to do with simulator support, there is no where anywhere in the vatsim documentation that states any requirements for VNAV/RNAV minimums to be able to use the network.

Kirk Christie - VATPAC C3

VATPAC Undercover ATC Agent

Worldflight Perth 737-800 Crew Member

956763

Link to post
Share on other sites

Am I missing something here? This sounds akin to blaming the builders and maintainers of road infrastructure for your car being faulty.

Running with the above analogy, VATSIM has always supported "cars" from many different "manufacturers". It's the drivers responsibility to know how to drive their chosen vehicle, regardless of it's condition. If the vehicle requires special conditions (such as being unable to follow a SID/STAR) it again falls to the driver to advise of such conditions via accepted mechanisms (such as flight plan remarks or a PM to ATC).

2 hours ago, Diego Vasquez said:

So I guess that the answer is NO, VATSIM ATC will not make any concessions for the well known limitations of the sim?

In short, the answer is actually YES because for nigh on 2 decades VATSIM ATC has accommodated the varying capabilities of pilots (and controllers). To suggest that would suddenly change now is, in my opinion, patently absurd.

  • Like 2

spacer.png

Link to post
Share on other sites

The way I interpret the rules and customs on the network:

  • The policy is to accommodate whenever possible. If you can't fly SIDs or STARs, you'll get vectors - just note that ATC may have to delay you, vector you onto a suboptimal route, put you in a hold, or ask you to divert, if things are very crowded.
  • In order to accommodate, though, ATC needs to know what you can and cannot do. The magic word is "unable"; but you also want to file a flight plan that you are comfortable executing, and use the "equipment code" and "remarks" fields to indicate the limitations of your aircraft. And don't just write "FS2020"; you can't expect controllers to know by heart all the limitations of all aircraft types in all supported sims. Write "UNABLE RNAV", "UNABLE SID/STAR" or some such instead.
  • Flying the aircraft however is your job; you are expected to figure out how to follow ATC instructions, they will tell you what to do, but not how to do it. At the very least, you should be able to fly a heading, altitude, and airspeed, perform a visual approach and landing, and be aware of your aircraft's performance limitations. Beyond that, ATC will assume that you are able whatever your aircraft type can usually do; if you cannot do that, or you are uncomfortable doing it with the tools at hand, the magic phrases are "unable" and "request vectors".

Note that VNAV or a working FMS aren't required for the vast majority of ATC instructions you will get - almost all STARs, SIDs, transitions, approaches, and other procedures can be flown manually, or with simple autopilot modes (heading hold, VOR/LOC, altitude hold, FLCH), it's just more work. Planning your descent is something you should do anyway; ATC won't do it for you (and they can't, because they don't know the performance limitations of your aircraft in its current configuration, nor your mission parameters).

23.png
Link to post
Share on other sites

Flight plans can be put in to the aircraft during flat and not just the world view in fs2020. I do it often. In addition you can return to the normal flight plan after deviations you just might have to delete a waypoint or two. No big deal. The only autopilot system that deosnt work is vnav so just use vs mode. I did my first ever flight on vatsim with the 787 and had no issues.

  • Like 1
Link to post
Share on other sites
22 hours ago, Kirk Christie said:

VATSIM allows all aircraft regardless of their inbuilt simulator capabilities, FS2020 is an approved simulator and with it, the aircraft that come with it.

The answers given to you were to advise the controllers weather or not you could accept what they were offering. VATSIM ATC will manage you accordingly. 

Awesome, that was my expectation I am glad to hear that.

And just BTW, throughout all my years on VATSIM whenever my flight breaks down because of my error, or because my PC, software or whatever, I apologize to ATC then simply disconnect.

The issue that I anticipated and the reason why I started this thread was, with FS2020 being so unpredictable, this will happen pretty darn often.

Link to post
Share on other sites
8 hours ago, Joshua McBride said:

Flight plans can be put in to the aircraft during flat and not just the world view in fs2020. I do it often. In addition you can return to the normal flight plan after deviations you just might have to delete a waypoint or two. No big deal. The only autopilot system that deosnt work is vnav so just use vs mode. I did my first ever flight on vatsim with the 787 and had no issues.

I have tried this several times and, for example on the Neo vertical navigation only works when the plan came from the world screen. I suppose this may be self inflicted (?).

Link to post
Share on other sites
22 hours ago, Kirk Christie said:

It was supported from day 1. The lack of VNAV capabilities has nothing to do with simulator support, there is no where anywhere in the vatsim documentation that states any requirements for VNAV/RNAV minimums to be able to use the network.

The reason I made the link between the pre-launch videos and the current long list of issues is, I don't ever recall VATSIM announcing so visibly a partnership before with Microsoft or any other vendors of the supported simulators.

Considering how proud of it all we all are (i consider myself part of VATSIM, as a pilot and general community member), I wondered if that partnership was only an announcement, or if it is a continued effort?

  • On this same line of thought, I would liked answers like how VATSIM has and will leverage the partnership with Microsft/Asobo providing feedback and raising visibility of top issues affecting the network. Or something in that direction.
  • Contrary to... embrace the sim for the purpose of publicity, but create distance when talking about the issues?
Link to post
Share on other sites
15 hours ago, Tobias Dammers said:

The way I interpret the rules and customs on the network:

  • The policy is to accommodate whenever possible. If you can't fly SIDs or STARs, you'll get vectors - just note that ATC may have to delay you, vector you onto a suboptimal route, put you in a hold, or ask you to divert, if things are very crowded.
  • In order to accommodate, though, ATC needs to know what you can and cannot do. The magic word is "unable"; but you also want to file a flight plan that you are comfortable executing, and use the "equipment code" and "remarks" fields to indicate the limitations of your aircraft. And don't just write "FS2020"; you can't expect controllers to know by heart all the limitations of all aircraft types in all supported sims. Write "UNABLE RNAV", "UNABLE SID/STAR" or some such instead.
  • Flying the aircraft however is your job; you are expected to figure out how to follow ATC instructions, they will tell you what to do, but not how to do it. At the very least, you should be able to fly a heading, altitude, and airspeed, perform a visual approach and landing, and be aware of your aircraft's performance limitations. Beyond that, ATC will assume that you are able whatever your aircraft type can usually do; if you cannot do that, or you are uncomfortable doing it with the tools at hand, the magic phrases are "unable" and "request vectors".

Note that VNAV or a working FMS aren't required for the vast majority of ATC instructions you will get - almost all STARs, SIDs, transitions, approaches, and other procedures can be flown manually, or with simple autopilot modes (heading hold, VOR/LOC, altitude hold, FLCH), it's just more work. Planning your descent is something you should do anyway; ATC won't do it for you (and they can't, because they don't know the performance limitations of your aircraft in its current configuration, nor your mission parameters).

Thanks, again that was more or less my understanding but I wanted to trigger the discussion because it will happen to people of different skill levels while trying to enjoy the sim and the network.

Link to post
Share on other sites

I think it's important to consider that we're talking about default aircraft, and comparing them to the fully-functional add-ons we're probably used to for FSX, P3D, and X-Plane.  If you think about the functionality of the FSX default airliners, and the additional pilot workload it took to fly them realistically on the network among the PMDGs of the world, it's about on par.  The patch that came out today allegedly addresses a lot of the complex avionics' functionality, so, maybe it's better than it was 24 hours ago.  But I don't think it's realistic to expect perfect operational behavior from default planes.  We'll probably need to wait until some more complete versions are available in the freeware and payware add-on marketplace.

  • Like 2

Cheers,

-R.

fvJfs7z.png

Link to post
Share on other sites

It is very nice to hear that VATSIM ATC's generally are accommodating. I certainly agree that maintaining control of the aircraft and adhering to ATC instructions is the pilots responsibility. 

My personal recommendation is that pilots should be experienced flying the specific aircraft they will fly on VATSIM, and aware of any shortcomings its simulated avionics and autopilot have in msfs202 and be ready to take manual control. 

It would be irresponsible to connect to VATSIM to fly IFR without vetting the aircraft and sims modeling shortfalls. I personally have found that only the Daher TBM 930 is close enough to be useable for IFR in a VATSIM environment. 

There is a specific problem I have seen (and reported to zendesk) which is really problematic. That would be the FMC automatically entering a USER waypoint when activating an approach. For whatever reason, instead of modelling real world, they decided that the FMC should insert this waypoint and a nice path to fly, which is between your current position and the IAF. The problem is, that waypoint is often behind you -- sometimes by a 100nm. 

Pilots should be aware of this and ready to manually direct the aircraft as required. Otherwise, what you will find happens is that as soon as you activate the approach you've been assigned, if autopilot is engaged in NAV mode, you might see the aircraft turn (maybe even 180 degrees) and if you don't catch it quickly that would be a deviation. 

Worse, is that it is very hard to get the FMC to fly anything other than that magical waypoint and path it picked. With the most recent patch released this week, it got slightly better. I find that at least now you can do a "direct to" the IAF and the autopilot will fly it instead of that magical path. Problem is, the FMC may not "count it" as arriving at the IAF and activate the next leg upon arriving at the IAF -- it may still want to fly back to that magical waypoint. 

You may or may not be able to activate legs beyond that IAF without flying the magical path. 

I would say that as long as a VATSIM pilot is aware of these problems, and can fly the aircraft despite them and maintain control and compliant with ATC directs, then flying on VATSIM would be appropriate. 

But if the VATSIM ATCs see a lot of deviations as a result of these issues, and that is impairing the management of the airspace and impacting others, that it would be appropriate to disconnect. 

Link to post
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
×
×
  • Create New...