C2615

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.

IRL the mag HDG/TRK displayed on modern airliner ND/FMS is based on true HDG/TRK subtract magvar mostly based on interpretation of nearby NAVAID/Airport data, so normally 28day cycle update will take care of them. Only when FMS fail or in place with no nearby navdata (eg. cross ocean) it will fall back to IRS stored data, which might be decades old. 1~2 degree difference to chart might also due to chart not update frequent enough, for example in ZSSS the runway heading shown on ND is 003 for almost a decade but only about 1~2 year ago the eAIP chart updated from 002 to 003. But magvar in China in general is few degree and the change rate is only a few minutes per year anyway... It also might be due to great circle interpretation (on FMS) vs rhumb-line (on some charts), if the distance is long enough. In my company <=3 degree difference is consider acceptable. What matter the most for IFR flight is actually the calibration(incidence) of VOR on the ground, any VOR is of course geography fixed, the magvar change doesn't effect it's beam, but to make the course align to mag bearing it'll need to be align manually, in XP11/12 it's the same data of FMS NavDataBase so it's also frequently updated (28 days if you subscribe for that). but in other platform like P3D you hardly update the "base" navaids (part of scenery), that will cause problem, I have once flown 737-200 in fs9 in the US and when switching from one VOR beam to another as arrival chart, I lost my position totally.... RNAV/FMS is totally coordination and true TRK based internally, only display mag when needed, so not much effect on slightly misaligned magvar anyway.

I have written a small program using FSUIPC for this back in FSX days, input speed range and number of engines so I can practice V1-go/no-go on airliner, I think It'll be earlier to do so with FWL?

Hear me out, to install as many people as possible, we should build the fuselage in cubic shape, you may ask how about the pressurization force? Well we can fly them low, like very low. I know it sounds dangerous, but we can clear out the route it flights, and build, let's say...rails... and as you fly so low, you don't really need wings, so get rid of that, we can fly using magnets, or just old MKI wheels, and as you can get cheap electric power from the rail, or maybe I don't know, power line near the rail, you don't really need fancy jet engines burning expensive fuel, that's a big save! And if you feel need to put more people in the "aircraft", maybe just link more fuselage together. Now everyone could travel fast and cheaply!

🫠And it uses 30% less fuel than spec, who need a MAX

TO N1 never matches the realworld data, outdated Normal checklist, Wrong turn on LOC capture, GPWS on stable final, late RA callout.... well, it's "not too much issue" on numbers but still very annoying for a normal A-B flight. And don't let me start on the EICAS and NNC ECL logic... it's so painful to do even a simple engine failure drill, let along other "more than thousands of failure available"... PMDGT7 in P3D makes more scene on that.

While I enjoy BMS and IL2, recently I addicted to Tiny Combat Arena, try to grind though the arena is kinda mixed with boring and fun...

I feel this have been on me for years (while I have gradually moved to XP12 for main sim anyway) The symptom is about 2~3hour in flight get a CTD and in the event viewer I see a Event 1026 .NET Runtime error like this one: - <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> - <System> <Provider Name=".NET Runtime" /> <EventID Qualifiers="0">1026</EventID> <Version>0</Version> <Level>2</Level> <Task>0</Task> <Opcode>0</Opcode> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2026-06-09T10:38:53.3705063Z" /> <EventRecordID>98516</EventRecordID> <Correlation /> <Execution ProcessID="6168" ThreadID="0" /> <Channel>Application</Channel> <Computer>Umi</Computer> <Security /> </System> - <EventData> <Data>Application: Prepar3D.exe Framework Version: v4.0.30319 Description: The process was terminated due to an unhandled exception. Exception Info: exception code c0000005, exception address 00007FFDED2123D0</Data> </EventData> </Event>And 1 seconds later: - <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> - <System> <Provider Name="Application Error" Guid="{a0e9b465-b939-57d7-b27d-95d8e925ff57}" /> <EventID>1000</EventID> <Version>0</Version> <Level>2</Level> <Task>100</Task> <Opcode>0</Opcode> <Keywords>0x8000000000000000</Keywords> <TimeCreated SystemTime="2026-06-09T10:38:56.1479704Z" /> <EventRecordID>98517</EventRecordID> <Correlation /> <Execution ProcessID="4604" ThreadID="20496" /> <Channel>Application</Channel> <Computer>Umi</Computer> <Security UserID="S-1-5-21-1507506471-1515142045-11927022-1001" /> </System> - <EventData> <Data Name="AppName">Prepar3D.exe</Data> <Data Name="AppVersion">5.4.9.28482</Data> <Data Name="AppTimeStamp">6463925f</Data> <Data Name="ModuleName">VCRUNTIME140.dll</Data> <Data Name="ModuleVersion">14.44.35211.0</Data> <Data Name="ModuleTimeStamp">0f259d81</Data> <Data Name="ExceptionCode">c0000005</Data> <Data Name="FaultingOffset">00000000000123d0</Data> <Data Name="ProcessId">0x1818</Data> <Data Name="ProcessCreationTime">0x1dcf7ee2026fc8a</Data> <Data Name="AppPath">B:\Program Files\Lockheed Martin\Prepar3D v5\Prepar3D.exe</Data> <Data Name="ModulePath">C:\Windows\SYSTEM32\VCRUNTIME140.dll</Data> <Data Name="IntegratorReportId">8403ad19-4ac2-4a57-8292-b2689cb23f70</Data> <Data Name="PackageFullName" /> <Data Name="PackageRelativeAppId" /> </EventData> </Event>The .dll name is very random, this time is VCRUNTIME140.dll, but it have been terrain.dll, api.dll, ntdll.dll etc etc....but always 0xc0....05 exception code. I have tried made full reinstallation of P3Dv5 before, still like this, and when I had enough I simply move to XP12.... Last weekend I thought since I not fly P3D that much, I now can uninstall many add-ons anyway, so I did , and give it a test (I still have some aircraft that's exclusive to P3Dv5 so I still want it work). I got a PMDG747 set with some random long 10+hour route, LNAV VNAV in and went to work, and as I went back it still works! I though maybe I got it, so next day I set a 2.5h route with PMDG747 and try properly fly it, and this time, 2 hour in to flight, CTD again. but along with that, I also see 1026 lead c0005 with "ActiveSkyUtils.exe", emmm, that seems suspicious, as the last 10h+ test I didn't have ASP3D running. So I disabled ASP3D in add-on.xml, fly same route again (with FSGRW), this time no problem. I though I got it, and the next day I got another 3h+ flight without issue. And to today, I though it'll be OK, but boom, 1.5h into flight, this again. I tried to see if it's the .net runtime issue but Framework4 is integrated in win11 and I can't upgrade or repair it anyway. While I'm thinking about make another full reinstall again this time add only minimum add-ons, the very nature of randomness makes this issue very hard to verify if it's gone, and I really don't mentally want put too much time in it as... I can always flee to XP anyway...

NG have new wings compare to 1/2/classics, MAX is same with NG, just different wingtips. Stability augmentation system is surprisingly common in airliners, but sure MCAS on MAX was catactrophicly faulty.

I so miss a 737-400 Also lacks a -700 with 26A-B2 engine and gaseous pax oxygen system for proper ZULS routes, not to mention BBJ with axu fuel tank and -27 engine. Heck, even the -300 from IXEG only came with -20K, not -22K Engine, totally unflyable in airports like ZPPP Also the ZIBO/LVUP still missing some old-school options like EFIS display config, non-RNAV and non-TO profile FMS, meanwhile IXEG's U4.0 FMS is kinda too old-school to my taste.

Air manager can be use in network with different computer so might save some GPU use. Also it's data driven, it might be different to the "real" thing, but it'll show things when your main view is not in cockpit, although I think Toliss have fixed that, as long as you are "near" the cockpit (say forward view without cockpit as you are using physical one) the pop-out will refresh fine. The best bet would be ToLiss Display App came with HOME/PRO SIMULATOR Licence, but that's not cheap.