Check that you don’t have conflicting hardware bindings for the avionics switch
Thanks, I will
Bingo! Problem with Honeycomb B buttons… soved
Thanks again
It seems that the occasional “not following GPS/ILS course” is still not fixed right? I just had it again after the update. How is your mileage? Also sometimes using HDG because NAV/GPS does not work?
How does one get the cabin altitude setting set up? I keep getting the warning sound, and no matter what I do, I can’t seem to get it right.
They changed the smoke effect again… but it’s still terrible! Think they need to look at Just Flight’s F28 and Vulcan for some inspiration…
1 Like
Hi,
Make sure that you have set the flight altitude in the pressurization controller and that the controller is in AUTO. After engine start flip the FLT /GND switch to FLT.
Also insure that the bleed switches for engunes 1 and 3 are OPEN, while the bleed switches for ENG 2/APU are closed.
Double check that both pack switches are ON.
Hi all
Following up on the issue of “not following GPS/ILS path” - I also now have the issue that the plane would not “set the bugs” when you click on the option in the clip board.
Before - in most cases - the speed bugs were set automatically. Now no longer.
I am not sure but it seems as whenever the speed bugs are not set it will also not follow the flight path
Do you have that issue too?
It really bugs me because without navigation you basically can forget to fly this plane - which really sucks…
If you scroll up a bit you can see that some of us had the same problem.
For me only MSFS restart helped.
I see -thanks! Do you talk about the missing speed bugs or the “not following GPS”?
Anyway, I tried that also restarting prior posting but it dit not help. I think this needs a fix anyway - hope they find the issue soon
For me this bug exhibited with more things not working: Cargo upper door dead, clicking on Set bugs in the clipboard didn’t do anything, heading bug was stuck in one position (probably the AP wouldn’t follow the GPS if I took off) and radios blue indicators were also stuck regardless the left/right radio switches.
Fortunately it’s only happened to me twice and didn’t happen recently. What I also did and what you could try… go to “C:\Users[your user name]\AppData\Roaming\Microsoft Flight Simulator\Packages” and delete the “fss-aircraft-boeing-727-200f” folder. That will trigger a new WASM compilation of the airplane.
Good idea! I will consider doing this indeed! Thanks!
Interesting - this folder does not exist. Gonna try to deinstall it in the apps and re-install from scratch I guess?
1 Like
OK I uninstalled and re-installed via Aerosoft App and now it looks like this:
I still don’t have the folder you mentioned…
I will start MSFS and load the plane - maybe this needs to be done to create the folder … Hang tight lol
I guess you have MS Store version of MSFS?
Correct! And now I just started a flight but the folder is not yet there. But the bugs work - gonna make a test flight to see if GPS works. Wish me luck
I see - will check! Thanks - was looking at another place
The uninstall & reinstall seemed to work - we are guided again 
Thanks mate!
2 Likes
Id like to see them remove that aweful black smoke during takeoff, its overly exaggerated , along with that looping cockpit sound…also the engine sounds as you get to 30-40 percent sounds like in cockpit like your going full thrust…
I agree. It looks ridiculous. I ended up editing the visual effect library config file so it doesn’t display the smoke.