C2615

Default 737 is kinda old mess and LR seems not bother to update it anyway as Zibo is effectively constantly updating whit their own version anyway. I would suggest just skip the default 737 and go download zibo or Lvup version and start from there.

There are -100 to -900 then Max7 to 10, that's already 13 different big variants IRL, then there are different engine rating, ADV, IGW, BBJ,PIP, SFP, C,BCF, BDSF.... so no, we don't have enough 737s in sim yet

Flight Factor 767 is rather OK

There is no Antarctic terrain in default XP, there are freeware add-on by maps2xplane in .org, Or as part of base pack for XPME, Or payware Antarctica Mega Scenery XP12 by HSimulators in org store (which I use) I visit Antarctic, most of the time Wilkins in flight sim almost annually every southern hemisphere summer.

My company's OFP and EFB can provide a profile of weather information along the route, I'm not aware any simulation product could provide that though...

AFAIK there are panels for Toliss in AM but IRC it will need premium beside AM basepack? I also simply click and pop them out, works totally fine on my multi-monitor setup, I heard there are some problem with 50xx GPU, then maybe try X-TextureExtractor If you really want go premium, Toliss provide official tool for remote monitor at steep price, mainly for simulator building,

I got a lot OOVM CTD with MEP recently and I suspect it's something to do with it's basepack, let me see if it's fixed. For many airport in southwest mountainous area of China, their basepack are much better to get a nice sloped runway on the mountain side rather than totally unusable jagging runway or a big area with unnaturally flat square(thus very jagging boundary)

FMS or any other modern aircraft systems build "by the FCOM" is almost useless, FCOM only describes how pilot use it, it doesn't provide much detail to replicate it properly. I know it because I have tried.

I just got the MIG15 and it's surprisingly well done. Although still can't deep stall this notorious spin machine, hope 12.5 would address that.

Just made a PDCS for it, you can try it out! https://forums.x-plane.org/files/file/100641-performance-data-computer-system-for-flyjsim-737-200v4/

Some old/simpler helo have no governor, so it's needed, and governor fail could be a thing IRL. If you only fly sim one with governor and not plan to practice on manual throttle, it's not mandatory.

I was able to complete a flight with it, however the traffic is weird , I see them when doing per-flight, and even heard a taxi in command to one of them (but no reply), but as I starting to taxi , I see none moving. Same when enroute, I see in the nav display there are quite some flight approaching my destination but when I arrive it seems all landed and non is still moving, so I didn't hear any other exchange between ATC and traffic. The UI and control is fine by just using 2 joystick button, I didn't try voice command as I fail to download it's component. Overall I didn't feel it's any better than XP's own system so far, the main complain I have with Default ATC is it only generate random AI traffic, or no chatter at all with others when using better scheduled traffic (I use World Traffic), which is basically the same in NextATC....

OK, after reading FTOB again and get some test on 737MAX simulator, I think I got something wrong and mixed. At least for modern Boeing, FMS does have 3 different magvar input, but the sequence is not what I said. 1st is IRU var, it's use for current HDG/TRK, including the one shown on ND and the active legs on LEGS page 2nd is FMC var, it's used for most of the LEGS page. 3rd is NavDB var, it only uses for legs after a NAVAID. So the 3 var doesn't override each other, but applied on different things. As my test, when I setup ABQ V190 FTI in CDU, the LEGS page shows ABQ 052> DULKE 058>CAYAL 058>RENCO 058>FTI , but on ND is shows a straight line. (btw it's also how it's shown on Skyvector's navlog) After crossing ABQ, the legs page changes to 058>DULKE...., the TRK on ND keeps at 058, while to keep the VOR needle in center I still need to dial 052 on COURSE, and the tail of RMI pointer stays at 052.

They are called blastpad, may looks same as stopway but it's generally not marked on airport chart EMAS also have same looking (at least from distance), but marked different on chart

True, but in XP's navdatabase system (sort equivalent to ARINC429 database) there is only magvar data for given VOR, same with AFCAD/ADE file for P3D afaik. I'm not sure how FMS will use that data IRL (if you fly on 052 course near that VOR in a modern airliner, what the TRK will read, vs the whiskey compass). And how XP will use these data (I'll give a test once back home) In CAE Level-D simulator's database, magvar and incidence are separate line of input for a given VOR.