Try to download the aircraft again. The download may have failed for some reason.
Yes, but they may have changes that result in difficulties or issues. You should get the aircraft from Octal450's repo.
Q. I can't control the rudder with my aileron axis after turning on the FlightGear auto coordination system. Why?
This aircraft has a complex and realistic flight control system, which contains a yaw damper and turn coordinator. Therefore, auto coordination is not necessary, and the rudder is only used in the air when de-crabbing during crosswind landings.
When the aircraft detects that auto coordination has been turned on, it enables the aileron drives tiller system. This way, you will be able to control the nose wheel with the aileron axis to steer on the ground. Please use keyboard for rudder functionality.
Some functions in the regular menu (like Autopilot) have moved to custom menus. This is due to limitations in the way the default menus can be manipulated to prevent unsupported functionality (ex: Previous/Next Waypoint) from being executed.
Some of the functions may be implemented in custom way and still usable. Check the custom menus to the right of the "|" for these functions.
Please use our issues page to report bugs. Please fill out the template there to the best of your knowledge. Issues submitted with blank templates will be closed.
Yes, please do so! If we do not know about the bugs, there is no-one to fix them.
It does not make sense sending in flight recordings, as they do not hold enough information. That is why they are useless for us. We do not plan on recording full information in the recorder. See the "Why does the cold and dark state load after exiting replay mode?" section for more information.
Instead, for documenting issues, please perform the steps mentioned in the next question:
Besides describing it with words, you may do two things, which helps us reproducing your issue locally such that it can be debugged:
-
Hit the screenshot buttons (hotkey
F3by default) often and send them all in! Five screenshots with redundant data isn't a problem to sort out, but one screenshot missing out which would have contained vital information may prevent understanding the problem properly. -
If able you may also dump the property tree. That is also a very helpful source of information. To do so, please open the "Nasal Console" from the "Debug" menu, paste this command, and press "Execute".
io.write_properties(getprop("/sim/fg-home") ~ "/Export/MD-80-dump.xml", "/");The dumped file will be located in$FGHOME/Export.
First of all, did you ensure that the bug is reported on our issues page? If not, please do so (see also questions above on how to report them)!
We suggest never downgrading your aircraft for the best experience. If you must do so, you must delete your MD-80-options.xml file. You may find it in $FGHOME/Export.
Q. I like increasing the simulation speed on long flights. However, I encounter issues with it occasionally. What's up?
Increasing the simulation speed is quite tricky for the simulator. Depending on hardware capabilities it can be incredibly stressful and the algorithms behind the scenes can be challenged quite heavily. If the simulation is running faster than the corresponding algorithms can be computed, many funny (or even ugly things) may happen. we suggest not setting simulation speed above 4x or below 1/2x at any time.
Check your frame rate ("View" menu, option "View Options", toggle "Show frame rate") when increasing the simulation speed. As a rule of thumb, if the frame rate stays constantly above 10fps, you are fine. Keep in mind that already one little phase (and not just the average) where the frame rate drops below 10 frames per second, you are in danger facing issues.