
Microsoft Flight Simulator (2020) 40th Anniversary Edition







In this guide i will go through most steps on how to talk to Vatsim atc. Might be hard to understand for some but i tried to make it as simple as i can, enjoy :) Before Reading! + Tips This tutorial is mainly based about flying around Europe, I have never flown in America so i have no idea what atc is like there, but i guess pretty simmilar, i have around 300 hours on vatsim so im not some hardcore ''vatsim nerd'', This guide is more about IFR flying and from my own experience Some people might have sceneries, so for you they are taxing on grass, but for them they are on taxiway, vice versa :) but ATC doesnt mind that, ATC also understands you might have a scenery so they wont tell you off for going out of taxiways etc. If you see some mistakes or have questions or have suggestions make sure to comment down below :) Hope you enjoy. For Vatsim i use Vpilot, and for ATC coverage i google ATC Sectors, and i use http://www.vattastic.com/ In this Guide things in Bold will be things depending of situation, so for example if in bold i says callsign, you would say your callsign. If you using default airports simply google airport ICAO and charts, and free charts from jeppesen are mostly from 2006 so the layout really matches the game as FSX is from 2006 Some commands that i know on vPILOT .com1 : Switches to com 1 .com2 : Switches to com 2 .x : Squawk Code ( e.g. .x 2550 ) .com1 [frequency] : Switches to that frequency ( e.g. .com1 122.800 ) .com2 [frequency] : Switches to that frequency ( e.g. .com2 125.800 ) .chat Callsign : You can chat to other pilots ( e.g. .chat RYR2812 ) .msg Callsign : Works like .chat, but sometimes buggy. .METAR [ICAO] : For example if there is no ATIS available and you want to check current weather at a certain airport you can type in .metar icao of airport and it shows information like wind, qnh etc. If you know anymore make sure to comment Special Squawk Codes 2000 - IFR when no squawk given 7000/1200 - VFR when no squawk given 7700 - Aircraft in danger (seven seven – go to heaven) 7600 - Radio Failure (seven six – radio fix) 7500 - Hijack NEVER SET THIS ON VATSIM! (seven five – man with knife) If you know anymore make sure to comment The guide isnt fully finished Before you talk to ATC Before you talk to ATC make sure you filed your flight plan on vPILOT, or what ever you are using, by clicking on ''Flightplan'' tab and filling the information there. So then the ATC will see your route etc. PREPARE A PEN AND PAPER AS WELL AS GROUND MOVEMENT CHARTS ATC's I use vPILOT, this information might be different on other programs The are different types of ATC's in Vatsim Area Control, e.g. Wien Radar LOVV_CTR Approach, e.g. Gatwick Approach EGKK_APP Departure, e.g. Liverpool Departure EGGP_DEP Tower, e.g. Warsaw Tower EPWA_TWR Ground, e.g. Liverpool Ground EGGP_GND Delivery, e.g. Gatwick Delivery EGKK_DEL ATIS, e.g. Manchester ATIS EGCC_ATIS What does each ATC do? If there is no atc around you, you can check via the left side of vPILOT, or on http://www.vattastic.com/ . You simply tune in to 122.800 (unicom) and just say your actions there. Area Control ATC; This ATC is in charge of a sector, for example London Control has i think 5 sectors, North,East,South,West and Central. Airport Approach; From this ATC you will recieve a STAR to an airport, or vectors depending on the situation, you will also be informed about airport information, traffic etc. Airport Tower; Tower will simply give you clearances for Takeoff / Landing. Airport Ground; This ATC is in charge of the ground, it will tell you what stand ( gate ) to taxi to, what holding point etc. Airport Delivery; This ATC will give you IFR clearances to an airport you flying to. Airport ATIS; This is an automatic message, no human behind it, this gives you the airport METAR, so the airport information ( airport information is important e.g. Delta ) it will give you the weather, wind etc. UNICOM (122.800); This is no ATC, but its a frequency that you should be on when thers no atc around so you can inform other pilots of your actions. How to talk to ATC ( Departure ) Things in BOLD Change depending on situation and place. ATIS First Listen to the atis to get the information !!! Once you get your information e.g. Alpha you can proceed. If no ATIS available simply say no Information or dont mention it, Listen out for ''on initial contact say you have xxxx'' Delivery to be honest this can be said in any order, it is also preferred to state the airport QNH With Information: Template: Departure Airport Name Delivery, this is Callsign at Stand Number with information ATIS information,Aircraft type Aircraft, QNH BARO, Request IFR Clearance to Arrival Airport. Example: Gatwick Delivery, this is Easy 2281, at stand 109 with information Alpha, Aircraft type a320, QNH 1013, requesting IFR clearance to Frankfurt. With no Information: Template: Departure Airport Name Delivery, this is Callsign at Stand Number,Aircraft type Aircraft, QNH BARO, Request IFR Clearance to Arrival Airport. Example: Gatwick Delivery, this is Easy 2281, at stand 109, Aircraft type a320, QNH 1013, requesting IFR clearance to Frankfurt. *ATC* You are clear to Destination Airport via Airport SID Departure, Squawk Template: Callsign Clear to Destination Airport via Airport Sid Departure, Squawking Squawk Example: EZY2281 Clear to Frankfurt, via BORI 2J Departure, Squawk 5512 Ground Tip If you not aware how to move on ground at certain airport, google airport ICAO and chart eg. EGKK Charts, and find ground charts, there you will see taxi ways and holding points. Pushback Template: Airport Name Ground, Callsign at stand Stand Number, Aircraft Type request Push and Start Example: Gatwick Ground, this is EZY2281 at stand 109, A320, request Push and Start. *ATC* Callsign Push and Start Approved facing South Template: Push and Start Approved facing *direction* callsign Example: Push and Start Approved facing South EZY2281 Taxi Template:Airport Name Ground, Callsign Pushed back from stand Stand Number request taxi. Example: Gatwick Ground, EZY2281 pushed back from stand 109, is ready to taxi. *ATC* Callsign Taxi to Holding point Via Taxiway Example to what ATC might say, EZY2281 Taxi to Holding point Juliet 2, via Kilo, Qubec, Juliet. Template: Taxi to Holding point Via Taxiway, Callsign Example: Taxi to Juliet 2, via Kilo, Qubec, Juliet EZY2281. ONCE YOU APPROACH THE HOLDING POINT YOU GET TOLD TO CONTACT TOWER Tower Sometimes when you contact tower he might tell you to go to another holding point. Template: Callsign With you, taxing to Holding point Example: EZY2281 with you, taxing to Juliet 2. *ATC* Callsign taxi to Juliet 2 and hold. Template: Taxi and Hold, juliet 2.Callsign Example: Taxi and Hold juliet 2. EZY2281 *ATC* Callsign You are clear for takeoff Runway Runway Number Template: Clear for takeoff runway Runway Number, Callsign Example: Clear for takeoff runway 28R, EZY2281 Once you take off you will get told to contact a Centre if online, if not you get told to monitor unicom on 122.800 *ATC* Callsign No Further ATC service available monitor unicom on 122.800 Template:Callsign Moving to 122.800, bye bye. Example: EZY2281 Moving to Unicom on 122.800, bye bye. How to talk to ATC ( In Air ) In air you wont get much atc, only Centres. Once in air if there is some Centre Online and you will approach his sector, you will most likely get a message on vPILOT to contact him on given frequency, if not, message him and ask if you should be in his sector. In Centre Just a note, sometimes centres might give you a new squawk code. On First Contact Template: Centre Name, Callsign With you at Flight Level Inbound Waypoint Example: Langen Radar, EZY2281 With you at Flight level 360, inbound GASKO. *ATC* Callsign Identified. Now sometimes the atc might tell you to direct to another waypoint due to traffic or him being bored, e.g. : *ATC* Callsign Identified, Direct to Waypoint Template:Directing to Waypoint,Callsign Example: Directing to POBOR, EZY2281 Once you Leave a Sector you get told to monitor unicom, or if available contact another sector If you are reaching T/D ( Top Of Descent ) Simply by informing the controller: Template: Callsign approaching top of descent. Example: EZY2281 approaching top of descent. *ATC* Callsign Descent to Flight Level Template:Callsign Descending to Flight Level Example: EZY2281 Descending to Flight Level 210 If you are approaching your airport after Top Of Descent and still in Centres sector, he will tell you to contact the arrival airport Approach if available, if not he will help you with the approach, that is of course if the sector control is controlling your area. How to talk to ATC ( Approach ) If Approach is Available you would contact them Tip: If you dont have a certain STAR because your AIRAC is outdated, simply say unable to do that arrival, something in those lines. Template: Callsign With you Descending to Flight level Example: EZY2281 With you Descending to Flight Level 110 What ATC might say? *ATC* Callsign Identified, expect STAR Arrival for runway Runway Number *ATC* Callsign Identified, expect vectors to runway Runway Number How to Reply? Template:Expect STAR Arrival for runway Runway Number, Callsign Example:Expect POBI 4H Arrival for runway 25L, EZY2281 Template:Expect vectors to runway Runway Number Callsign Example:Expect vectors to runway 25L EZY2281 Once you approach the runway, and around 25 miles away or so, you will get told to contact tower ( If tower is available ) *ATC* Callsign Contact Arrival Airport Name Tower on Frequency Template: Contacting Arrival Airport Name Tower on Frequency, Callsign Example: Contacting Frankfurt Tower on frequency 123.250, EZY2281 BEFORE CONTACTING TOWER If ATIS for arrival airport is available make sure to listen to it as you will need the information code for arrival too for a landing clearance, if no atis, simply dont give the atis code. Also if you didnt get a STAR, simply just say you on vectors Contacting Tower Template: Arrival Airport Name Tower, Callsign with a STAR Arrival, request landing clearance for runway 25L with information ATIS information Example:Frankfurt Tower, EZY2281 with a POBI 4H Arrival, request landing clearance for runway 25L with information Bravo YOU CAN ALSO SAY YOU ARE ON FINAL, OR WITH YOU APPROACHING RUNWAY #/b][/u][/i] *ATC* Callsign Clear to land Runway Runway Number ( ATC will also give some information about weather How to talk to ATC ( At Arrival ) On landing ATC will probably tell you when to turn off, also depending on airport he will tell you what Holding point to turn off at and what side, which is why charts are important. Once turned off, Tower will tell you to contact ground if available *ATC* Callsign Contact ground on Frequency Template: Contacting Arrival Airport Name on Frequency, callsign Example: Contacting frankfurt ground on 152.200. EZY2281 Ground Template: Arrival Airport Name, callsign with you Holding point, request taxi to Say where you want to taxi to Example: Frankfurt ground, EZY2281 with you at holding point bravo 5, request taxi to gate/stand. *ATC* callsign Taxi to stand Stand number via Taxiways Template: Taxing to stand Stand number via Taxiways,callsign Example: Taxing to stand 155 via Bravo, Kilo, Juliet, Tango. EZY2281
复习一下北约音标字母表。 北约音标字母表 A - 阿尔法 B - 布拉沃 C - 查理 D - 德尔塔 E - 埃科 F - 狐步 G - 高尔夫 H - 酒店 I - 印度 J - 朱丽叶 K - 基洛 L - 利马 M - 迈克 N - 诺维ember O - 奥斯卡 P - 帕帕 Q - 魁北克 R - 罗密欧 S - 塞拉 T - 探戈 U - 制服 V - 维克多 W - 威士忌 X - X光 Y - 扬基 Z - 祖鲁 补充说明 其官方名称为国际无线电通话拼写字母,也被称为国际民航组织音标字母。 当你想使用Vatsim时需要了解它。 游戏内空中交通管制也会在呼号、滑行道、自动终端情报服务信息代码以及其他一些情况中使用它。曾经有一个漏洞,导致“罗纳德·里根国际机场”变成了:罗密欧·奥斯卡· november·阿尔法·利马·德尔塔·罗密欧·回声·阿尔法·高尔夫·阿尔法· november·印度· november·探戈·回声·罗密欧· november·阿尔法·探戈·印度·奥斯卡· november·阿尔法·利马(很高兴这个漏洞已经修复了:D)酒店·狐步舞·高尔夫·利马
本指南将为你介绍航空领域的计量单位、单位换算成千米和米的方法,以及航空领域的语音字母表。 主要计量单位及换算: 1 海里(1 NT - Nautical Mile) - 1.85 千米 1 节 - 1.85 千米/小时 0.1 马赫 - 122 千米/小时 1 英尺 - 0.300 米 29.92 - 标准气压(单位:毫米汞柱)或者1013,这是标准语音字母表。乍一看,航空领域使用的是普通英语,但实际上远非如此,至少在MCDU编程中,用于表示机场、降落点等信息时,使用的不是英文字母,而是特殊的航空字母表:A - Alfa - 阿尔法,B - Bravo - 布拉沃,C - Charlie - 查理,D - Delta - 德尔塔,E - Echo - 埃科,F - Foxtrot - 狐步,G - Golf - 高尔夫,H - Hotel - 霍特尔,I - India - 印度,J - Juiett - 朱丽叶,K - Kilo - 基洛,L - Lima - 利马Лима M - 迈克 N - 十一月 - 诺维ember O - 奥斯卡 - 奥斯卡 P - 爸爸 - 爸爸 Q - 魁北克 - 魁北克 R - 罗密欧 - 罗密欧 S - 塞拉 - 塞拉 T - 探戈 - 探戈 U - 制服 - 制服 V - 维克多 - 维克多 W - 威士忌 - 威士忌 X - X光 - X光 Y - 扬基 - 扬基 Z - 祖鲁 - 祖鲁 此外,您还可以查看我关于如何安装涂装以及在哪里获取它们的指南。

《微软模拟飞行2020》视频指南,包含游戏玩法、训练和基准测试

Overview Modern MSFS add-ons often ship with 4K textures by default, which can significantly impact performance - especially with AI traffic and large airports. This guide highlights a simple, effective tool that allows you to downsize texture resolutions for AI traffic liveries (such as FSLTL) and airport textures, improving performance with minimal visual loss. Who This Guide Is ForUsers with heavy AI traffic setups People experiencing stutters at large airports Anyone running MSFS with extensive add-ons Users looking to improve smoothness without lowering in-sim graphics settings What This Tool Does The tool allows you to: Batch-resize texture files Convert 4K textures to lower resolutions (e.g. 2048×1152) Reduce VRAM usage Improve CPU/GPU frame pacing Reduce stutters at busy airportsIt is particularly effective for: AI traffic liveries (FSLTL, AIG, etc.) Large scenery packages Airports with excessive texture resolution Why This Helps Performance In Microsoft Flight Simulator, AI traffic and scenery textures: are loaded simultaneously compete for VRAM increase draw-call pressure Reducing AI livery resolution from 4K to 2048: preserves acceptable visual quality (AI aircraft are rarely viewed close-up) significantly reduces memory bandwidth usage improves smoothness at busy hubs The Tool MSFS Texture Optimiser[izn-flightsim.s3.amazonaws.com] I found this tool via a flight sim forum, created by a very talented fellow simmer. It is: lightweight straightforward and does exactly what it claims How I Use It (Example) I used this tool to downsize FSLTL AI traffic liveries. Original resolution: 4K New resolution: 2048 × 1152 Why 2048?: 2048 maintains near-identical visual fidelity at typical viewing distances while significantly reducing VRAM usage and stutter risk. 4096 textures are often unnecessary unless inspecting aircraft at very close range. Result: noticeable performance improvement no meaningful visual downgrade for AI traffic smoother camera movement at large airports The same approach can be applied to: airport texture folders scenery packages with excessive texture resolution Tutorial Do not be put off by the developer's comment that non-fluency with the cmd prompt should exclude you from using this tool. It is very easy to use once you get your head around it. Please be mindful of the different spellings (British and American) of optimiser/optimizer. Unzipping the texture optimising program and installing it First, place your unzipped texture optimizer folder on your desktop for ease of access. I renamed it "textureoptimiser." Now, run the executable located in the folder. When prompted, select the installation directory of the folder on the desktop, in my case "textureoptimiser" and install into that. Download and install the ‘Compressonator.’ Second, download and install the two programs you are directed to in the guide. The guide is located in the installation folder. Install “Compressonator” to C: (recommended for simplicity). Place/install "texconv.exe" in the "bin CLI" folder inside the root folder for the compressonator e.g. C: Compressonator bin CLI Copy textures root folder (e.g. fsltl-traffic-base) to your desktop Next, copy the root folder of your traffic addon to your desktop for ease of access. E.g. fsltl-traffic-base Run CMD (command prompt) Now click search on the Windows lower taskbar, and enter "cmd" without quotations and hit enter. Next, direct the cmd program to the installation folder of the "Texture Optimizer" so it can run the executable. As it's on the desktop, I wrote the following into the prompt: cd C: Users <YourName> Desktop textureoptimiser Keep the cmd window open. Now, run the texture optimiser to downgrade the textures to either: 2048 1024 512 256 For example, to do this, in the cmd prompt write textureoptimizer -source "C:/Users/<YourName>/Desktop/fsltl-traffic-base" -resolution 2048 Note: The executable uses the American spelling “optimizer.” When typing commands, use the exact spelling shown by the program. If you are unsure of your Windows username, open File Explorer and click “This PC / Local Disk (C:) / Users” to see your folder name. The texture optimiser should run. It can take a while, depending on CPU and drive speeds. Leave the cmd window open as it downgrades the textures. You should see a percentage rate increasing up to 100% until all textures are optimised. You will see something like "TOTAL SIZE OF INPUT FILES PROCESSED: 48.3 GB TOTAL SIZE OF OUTPUT FILES PROCESSED: 20.3 GB" at the end of the optimisation process. That is when you can safely close the cmd prompt. Once it's done, it will create a new folder in the same directory as the source folder is located in (e.g. my desktop), denoted "-OPTIMIZED". This means you will have a backup folder in case anything has gone wrong. Final steps Finally, delete the traffic root folder from your Community folder and place the "-OPTIMIZED" folder into the Community folder, and rename it so it is named the same as the original folder e.g. "fsltl-traffic-base". That should be you done. Remember that every time the traffic addon receives models updates, you will have to repeat the entire process after updating from the addon installer. If you have any issues, please feel free to comment below. Troubleshooting assistance is provided in the guide that comes with the texture optimiser tool. Important Notes Always back up textures before modifying them as a precaution - although the optimiser should create a separate folder denoted "-OPTIMIZED" anyway AI liveries are ideal candidates for downscaling Avoid aggressive downsizing for cockpit textures or aircraft you fly manually This is a performance optimisation, not a visual overhaul Note: These optimisation principles are also likely to apply to MSFS 2024 due to shared engine heritage, but this guide is written and tested for MSFS 2020.





一份简单易懂的逐步指南,用于解决伴随特定错误代码出现的崩溃问题 需要注意的现象: 加载期间(主菜单出现前)突然发生“无声”崩溃 如何判断是否适用本指南: 为了确定本指南是否对您有帮助,您需要了解需要注意的现象以及该错误的常见迹象。 崩溃原因: 可能是Asobo和microsoft在游戏优化方面存在不足(不确定) 如何确认错误: 1. 打开路径:C: Users YOURUSER AppData Roaming Microsoft Flight Simulator 2. 查找崩溃报告,例如名称类似“AsoboReport-Crash.txt”或“microsoft flight sim crash”的近期包含“crash”字样的文件 3. 在报告中查找代码【Code=0xC0000005】(通常在崩溃文件顶部)。找到此代码即可确认您遇到的是该错误。如果是其他代码,本指南可能不直接适用于你,但你可以尝试按照本指南操作,说不定会有帮助。 修复方法: 这非常简单。 首先,确认你确实遇到了此错误(或类似错误——请务必按照本指南操作,DX11 可能比较挑剔!)。 找到 UserCfg.opt 文件,该文件位于 C:Users你的用户名AppDataRoamingMicrosoft Flight Simulator。这本质上是一个设置保存文件。 在该文件中按 Ctrl+F,输入“PreferD3D12”,找到高亮显示的关键词。 如果显示为“PreferD3D12 0”,这很可能就是你的问题所在。 只需将其更改为“PreferD3D12 1”。 然后按 Ctrl+S 保存并重新启动微软模拟飞行! 现在应该可以正常运行了! (注意:这可能会导致一些帧率下降,但这只是一个提醒,并非绝对会发生。)

















