![]() As soon as I get down to about 15,000 feet, all instruments return to normal, correct readings and I can restart my climb.My pitot heat was on from engine start, and I was watching my instruments carefully all through my climb, so I'm pretty sure I'm not REALLY at FL600 and 470 kts (but who knows?).Can anybody help? This is driving me mad! This is a fairly new and clean install of FS9 and FSNav on a new build - less than a week old - and it happened again! Could this be attributable to some sort of hardware issue - heat, perhaps?As always, thanks in advance for taking the time to read this, and any suggestions you may have. I then tried to set it manually on the panel with the mouse with no effect - all sypmtoms persist. I was using the preloaded "Fair Weather" scenario and as I'm quietly climbing through about FL280 using FSNavs Fly Flight Plan feature that runs with my Overland 777LRs autopilot, instead of all my speed indicator instantly falling to 000 kts and the thottle pegging out to max, this time both of my altitude meters and airspeed indicators jump to over 60,000 feet and 490 mph respectively, and I get a "Cockpit Tip" telling me my barometer isn't set correctly for high altitude flight, when I had manually set it to 29.92 through FSPassengers L key feature. Has anyone tried FDC Live Cockpit 2011 (for FSX and FS2004), sold by Aerosoft, in P3Dv2 Perhaps using the EMT My system specs: Intel i9-108503.6 - 5.2 GHz, NVIDIA GeForce RTX 3080, 32GB DDR4 RAM, Noctua NH-D15 CPU Cooler,1TB Seagate SSD, 4TB Seagate HD, Windows 10, Asus 32 inch monitor, Saitek Yoke, Throttle Quadrant, Rudder. ![]() ![]() This problem has cropped up again only this time about 400 miles into a flight from EGLL to KBOS, and with a little twist to it. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |