Closed TheSystemGuy1337 closed 3 months ago
Also, for whatever reason the Master Caution and Master Warning lights are extremely dim. Two issues for the price of one!
There's lots of issues in XP11, many of which are fixed in XP12. XP11 support is now minimal at best, I'll do what I can to fix things that were working if they get broken, but other than that XP11 support is minimal.
FCOM stands for Flight Crew Operating Manual, you'll find them online, or via materials linked on the discord.
The ILS autotunes, so just enter an approach and then press APP and you should be good to autoland, you need to be 50nm from the airport and receiving signal before it will activate.
There's lots of issues in XP11, many of which are fixed in XP12. XP11 support is now minimal at best, I'll do what I can to fix things that were working if they get broken, but other than that XP11 support is minimal.
FCOM stands for Flight Crew Operating Manual, you'll find them online, or via materials linked on the discord.
The ILS autotunes, so just enter an approach and then press APP and you should be good to autoland, you need to be 50nm from the airport and receiving signal before it will activate.
Since XP11 isn't even properly supported anymore, I'll revert to an older version and just put up with the issues. The dim Master Caut/Warn lights won't be fixed, so might as well downgrade to a version that doesn't have this bug. I don't have any PC that can even run XP12. We should also consider dropping XP11 support fully at this point.
Even then, where do I enter the approach infomation?
Even then, where do I enter the approach infomation?
just enter an ils approach procedure in the FMC then
Describe the bug
Please provide documentation references:
Place an x to check the boxes:
Bug reports:
Many remaining issues are likely airframe specific, please provide the livery this bug happens with
Airframe: ____
The livery folder will also contain a jdat file of various data recorded during the flight, please attach it to the report if the issue occurs during a specific phase of flight
ILS is completely fried and refuses to lock onto proper ILS frequencies. Couldn't find a COM panel so I used NAVRAD menu as per #856 but don't understand what FCOM is and how to access it. Any attempt to insert ILS information from AviTab causes the FMC to load random ass data and will either cause the plane to divebomb into someone's house or just spin around in circles rather than lock on. This screenshot is from my attempt to land at JFK, runway 13L. Typing the information in instead loads data for KDTW.