Search the Community
Showing results for tags 'Fail'.
Found 3 results
-
I just cross posted in someone else's topic but thought this was important enough to call out independently if you are having the MSFS won't load issues: All of a sudden after the last Win10 update I am in the same boat and MSFS will no longer load. Tried getting updates from the store, none available, signing in and out of the store and XBox, repairing, removing Community, no luck. Last time I flew was Sunday, shut down and all was fine and today I can't even load it. Frustrating Then I looked down and noticed my system clock was off. I have it set to Set Automatically, adjust automatically, all those settings but Holy cow it was my System Clock!!! It must have been off from Daylight savings time and while it is 4:15 est my clock had 5:15 est. I adjusted the clock and MSFS launched automatically because I had tried to launch it but it wouldn't load until the time was correct! So if anyone runs into MSFS not launching and you've tried all the other steps, check you system clock!!
-
Since last night i have been through this update sequence six times. This morning 'I thought' I was getting somewhere. After having lost all my 'Control Options' settings I was now able to input new profiles but the Default name would not change to the new profile name that I gave it. Then I got the message that I had to install some other essential update. I thought I had better do this before continuing. This I tried but after another 30 minutes it turned out to be the same update that I had previous installed !!! Then it finally hung with a blue screen with a '/' at top righthand side. Every time I try to access the 'Control Options' to restore my lost settings, it can take over 15 minutes before I can actually start to select anything again. If I try to select another tab it can take another 15+ minutes before I am able to start again with the new tab. Anyone out there Know what's going on?
-
I can Autoland CATIII at other airports where the runways are designated as CATIII capable, but in 2 different flights from EBBR to EGLL, I was unable to have both CMD a/p buttons remaining lit during final approach and the CATiii landing failed in both cases.Does anyone know what I might have done wrong? Configured Runway Length for 27R at Heathrow on the HUGS setup panel 12798 feet Entered Runway Altitude in HUGS panel 79 feet Confirmed 3 degree GLS in HUGS panel Selected PRI in MODE for HUGS panel STBY AIII ARM in HUGS panel Set CRSE both seats for 271 degreesSet NAV1 and NAV2 both for 110.30 hzFollowing the above for other airports such as CYVR (Vancouver Int'l) the plane autolands including flare just fine. I simply push the nose down following touchdown and engage the reverse thrusters and then the brakes - spot on.None of this works as I expect at Heathrow.The A/P switches from Capt to FO (they will NOT both remain lit, even during the very final portion of the approach)Any suggestions will be most welcome - thanks.If perchance there is NO Cat3 capability at EGLL, I'd love to hear it, but that disagrees with what my other resources say.