安裝 Steam
登入
|
語言
簡體中文
日本語（日文）
한국어（韓文）
ไทย（泰文）
Български（保加利亞文）
Čeština（捷克文）
Dansk（丹麥文）
Deutsch（德文）
English（英文）
Español - España（西班牙文 - 西班牙）
Español - Latinoamérica（西班牙文 - 拉丁美洲）
Ελληνικά（希臘文）
Français（法文）
Italiano（義大利文）
Bahasa Indonesia（印尼語）
Magyar（匈牙利文）
Nederlands（荷蘭文）
Norsk（挪威文）
Polski（波蘭文）
Português（葡萄牙文 - 葡萄牙）
Português - Brasil（葡萄牙文 - 巴西）
Română（羅馬尼亞文）
Русский（俄文）
Suomi（芬蘭文）
Svenska（瑞典文）
Türkçe（土耳其文）
tiếng Việt（越南文）
Українська（烏克蘭文）
回報翻譯問題
討論區規矩與守則
檢舉此篇文章
QNE: query nautical elevation (baseline 29.92 inHG, 760 mm - what Neo says to set above 18,000 feet so everything is tracked the same all over)
QFE: query field elevation (pressure adjusted to show height above ground, so when landing it will read 0)
Of many IFR flights I had there was only one that went perfectly. It maybe me but I think there are some serious hilarities with the ATCs here. Such as:
- assigning departures for runways that should be closed (tailwind sides) even with live traffic and weather
- spontaneously assigning a different approach than filed (which could be due to live traffic but re-programming the MCDU while on descend and / or beyond transition fixes often results in a complete f*ckup)
- repeatedly reminding you to expedite your climb / descend while already on the assigned flight level
- telling all the live traffic to descend to 10.000 ft for whatever reason
and so on.
Pretty sure the devs are aware of the problem. Of course also live traffic plus other players leads to lots of trouble, too.
(You can stop reading here)
I fought this problem in FSX and it's literally no different in MSFS. I swear it's the exact same ATC with a larger vocabulary, which just makes it derp even harder. I don't see why it's not as easy as giving me the option in the pre-flight route setup to tell the game I want to cross FISEL at FL220 (because that's the crossing restriction on the STAR). Then just have ATC make that happen when I'm flying.
If you make and save a route, and then open (notepad) the .PLN file. There's a line in there for each waypoint that seems to be an altitude, but if you change them the ATC doesn't do any different and it just makes the Nav Log altitude planner thing go crazy. The file structure is identical to the .PLN files we had in FSX, just with a new line or two for STARs, just BTW.
All I ever wanted was for them to give me a crossing restriction. I don't care if they know the name of the STAR or even the name of the waypoint. I know there's 3rd parties that will do this, but the AI solutions are not really controlling the traffic, they're just controlling you; VATSIM is really the only way to get both. And honestly, if I could just fix this one thing, I would totally be fine with the default ATC.
I don't want to just bash it pieces though, as I think there is some hope. I have no idea what airport I was near, but on one of my first flights I did hear the ATC tell a plane to reduce speed to 250kts. It's totally possible he was below 10,000 and ATC told him to slow down. I've not tested that, but it was never a thing in FSX, but that doesn't mean it wasn't added. What I'm hoping is, it was a speed restriction on a STAR for one of the featured airports.
(You can really stop reading now)
I messed around a lot with making my own addon airports in FSX and everything to do with ILS and RNAV approaches for an airport was completely tweakable. You could add that missing approach you wanted to a default airport (in separate piece of software) and set all the restrictions for each fix. Once you added your new updated airport to your mods folder, ATC would in fact tell you to descend to the altitudes you set.
If you've done enough ILS approaches, you know not every IAF has the same altitude and the default ATC does know this and will assign you the appropriate height for that approach. In FSX this only applied to approaches. It would appear we may have the ability to play with similar settings for STARs now, so it's possible it might finally happen. Of course, you'll need to find (or make) an updated version of every airport you want to fly into.
I've only done one IFR jetliner flight in MSFS and that was KJAX EXBOX2 OMN FISEL6 KFLL, which is something I've done 100 times in FSX. The flight was handled near the exact same way FSX ATC would have handled it except everytime I was handed off I would get "continue as planned" or "continue to 'waypoint' as planed".
The controller did vector me off the STAR which I thought was pretty neat as FSX wouldn't have done that. A bonus for me and probably just a luck of the draw, but he vectored me off pretty close to where I had been vectored off in Vatsim several times, so that felt cool too, I was just way to high. On my todo list is to fly a published STAR into one of the featured airports like O'hare and see if the ATC experience is any different.
(Look, I just got off work and smoked a bowl, I've got time, you, you move on)
I can't stop flying the smaller planes at the moment and been doing a lot of VFR flying into uncontrolled airports, but near bravo airspace. I'll give the default ATC (and AI) another nod here, I think it's actually pretty interesting. To really showcase it, give the copilot control over the radios. They'll ask for permission to enter the bravo, but only if you're actually in it, as in they understand how the shelves work.
You can fly underneath a published shelf and the copilot is smart enough to not radio for clearance. They seem to always request flight-following, regardless of distance. They aren't too bad at entering uncontrolled fields either. ~10nm out they will radio the CTAF and tell them we're in bound. If you fly close enough to what the game considers a pattern for the runway, the AI will also call your base and final legs. After that it just kind of quits, but I consider that pretty decent for what I expected from the IFR experience.
So all that to say we'll probably have to wait for a 3rd party solution, just like everything else. However, unlike FSX, we won't have to rely on Vatsim or the ATC "cover up" solutions to get a decent arrival. We'll instead need to download airport sceneries, as its the .BGL files that contain all the STAR information for each airport (don't forget all this applies to SIDs too!). Then, the default ATC will read the new files and actually give you a decent arrival. Maybe... it looks hopeful, but not certain.
I'm the same way. Get just a little high and i won't shut up
Set the altitude using the knob, then push the knob forward (up arrow on the cursor).
Then I push the thrust into CL mode.
The aircraft will then calculate the best speed to use to climb/descent. I've done multiple legs of flight on the A320 all on fully managed mode. Even got it to auto-land at the arriving airport. You just need to monitor the instruments and give her the right input, and she'll take care of you.
ATC Controller are drunk. They had me fly to FL40 in a plane that had a ceiling of 32,000.
Had me set up for landing at 20,000 feet less than a mile from the run ways.
They tell me to descend then turn around and tell me to fly even higher, the drunk B$%T@##ds
So, I think I'll follow the flt plan and ignore them until they sober up.
Totally agree, I do the same as you, never have problems, sometimes I also use the spoilers to increase a little bit the decending rate or when I am already below 10,000 and I have to maintain below 250 knots. That is all.
I have also noticed that when the ATC wants you to decend to 10,000 for example, and after a few minutes it says to you to climb to 13,000 is because the constrains in the approach are preset like that, I think that it is more an issue of the approaches than the ATC.
The real problem with the AP in MSFS 2020 is that all the decisions it makes depend on the airspeed. If the approach mode is active, it will try to slow down to the approach speed of the CDU, it doesn't matter if you have to decend, it won't decend until it reaches the speed, if you help the AP with spoilers to control the speed, it will do whatever you want. It is all about the speed, understanding this, the AP will work ok.
If you want to start your decend, the AP will first reduce the thrust and then the decend will start to maintain the airspeed. At first, it will do it like a rocket but it will get better when it reaches the airpeed. If you want to decend faster, apply spoilers.
The game is broke in so many ways, its riddled with bugs but I still love playing it though LOL.
I follow ATC and havn't had a problem(longitute mostly at the moment). I will make my descent at the MACH cruise(0.8) and at 2k ft/min until 280 kias and then will keep 280 kias untill 10k ft, then ~245 kias. You don't have to follow my kias, but staying at a kias while on descent is the key as your GS reduces. I am not quite sure if the current ATC takes aircraft performance into account but as I said I have had no issues.
Is your flight plan set up to fly at 21,000 ft? Maybe don't set up a flight plan with a cruising altitude that's higher than the maximum altitude of your aircraft. The ATC just follows the flight plan.
This is a good general practice. You can still travel at cruising speed up to 10,000 feet. Then the regulation limits your speed to 250 KIAS maximum. So you flying on ~245 is the right way to do it.
The good thing is, the A320 flight plans are all set up automatically, they already impose these strict limitations into the FMC so as long as you're flying with "managed" airspeed, you should be good.
Instead, I use a real-world rule of thumb to calculate my Top-of-Descend, and use another rule of thumb to manage my rate (since the vnav isn't all that great in the simulator either).
For the first rule of thumb, I take the altitude I need to lose, and multiply it by 3 to tell me the track miles from my destination I need to descend. (i.e., if I am at FL220, 22 x 3 = 66 nm. If I am at 10,000', 10 x 3 = 33 nm). During my descend, every few thousand feet, I would recalculate this in my head to see if I am on profile. If I am flying a faster jet, like an A320, I would add a little more buffer to account for speed and energy.
For descend rate, I take half my ground speed and add a zero. If my groundspeed is 300 knots, then half of 300 is 150, and adding a 0 would equal 1500 FPM.
These two rules will help you maintain a 3 degree glide path straight to your destination.
You do have to account for STAR altitude restrictions if they exist, but that isn't particularly hard to do either. Say you need to be at a waypoint at 3000', and your altitude is FL220. 22000 - 3000 is 19,000. 19 x 3 = 57. Therefore, 57 nm from the waypoint, you start your descend.
An A320 in real life does manage the descend profile on its own, but of the one time I've flown the A320 in FS2020, the system does not appeared to be modeled with much accuracy. So, I'd rather just use V/S and descend manually using the above methods.