Bush trips general

Hello everyone,

I think it’s wonderful that bush trips are back starting with SU 6. During the beta phase and even afterward, a lot of bugs were reported, but so far none of them have been addressed in the SU 7 beta. I’d like to avoid creating a new thread for every single bug, so I’ve compiled a comprehensive list here and really hope that at least some of these issues will be taken into account and added to the bug database.

  1. The multiplayer mode in FS24 doesn’t work. There’s also no general air traffic. You’re practically always alone in the air.

  2. Refueling during a flight doesn’t work. The only way to complete longer flights is to assign the “Repair and Refuel” function to a key or keyboard shortcut.

  3. There is no longer a co-pilot in FS24. So far, no developer has found a way to incorporate a co-pilot. Only your own avatar—the one you selected in Career Mode—is visible as the pilot.

  4. For flights that take off “cold and dark” from a parking spot, this no longer works after the first leg. The aircraft is then always positioned “cold and dark” on the runway instead of at the parking spot, and strangely enough, the avatar is sometimes at the designated parking spot and has to walk a long way back to the aircraft.
    Workaround: Use the keyboard shortcut for boarding; the default is Shift + C.

  5. When taking off for a “cold-and-dark” leg, the parking brake should always be engaged. This is usually not the case.

  6. On all GPS devices, the current heading is no longer displayed after Leg 2 if you click “Continue” after landing. Only when you return to the main menu and start the next leg will the GPS heading be displayed correctly again on most GPS devices (G 1000), though not on all of them.

  7. Another known issue is that aircraft do not function as expected.
    Examples: On the DA-40, fuel must be pumped from the right auxiliary tank into the left main tank. Although the switch designated for this purpose is turned on, the left tank empties, but no fuel flows from the right tank into it.
    In other aircraft (Cessna 152 and 172), the fuel pump must remain on, even though this should actually only be the case during takeoff and landing.
    Neither the XCub nor the NXCub offers a way to monitor the fuel level in the tanks. Both fuel gauges show the same fuel level, even though only one of the two fuel tanks is in use and the gauges should therefore display different values. This means you cannot tell when one of the tanks is empty and the engine fails. You should therefore monitor fuel consumption in the exterior view HUD and switch the fuel selector after reaching about 10%.
    In other aircraft, the electrical system fails after the 2nd or 3rd leg. In most cases, assigning the “Repair and Refuel” function to a key or key combination helps here as well.

  8. In bush trips, developers can set options for ending a flight, such as applying the parking brake or shutting down the engine. These two options still work in FS24. However, what is no longer recognized is turning off the main battery switch and the avionics.

  9. The images in the Navlog are meant to show meaningful landscape details that aid in navigation. In my opinion, they are displayed much too small in FS24, making it nearly impossible to make out anything. They should be at least as large as a cigarette pack on the screen.

  10. The Navlog does not display the names of the departure and destination airports, but only a runway number. However, this number may not correspond to the weather conditions and only causes confusion. It would be better if the ICAO code and/or the airport name were displayed.

  11. In FS24, the end of a flight is indicated by a performance chart, similar to Career Mode. Since you always reach 100%, this doesn’t make sense. The displayed flight time is also incorrect. I think it would be better to end BTs with a reward screen, as in FS20. It would be even better if the actual flight time and the nautical miles flown were also displayed.

  12. So far, air traffic control (ATC) for bush trips in FS20 has worked relatively well. In FS24, the whole thing has gotten a bit messy. After completing leg 1, only the options applicable to the departure airport are available. This means that after leg 2+, I can no longer request a takeoff clearance. Once you’re back in the air after leg 2+, air traffic control works as expected, so you can track your flight path and request the next landing clearance. As soon as you’ve landed and exited the runway, you’ll be prompted to change frequencies to request taxi clearance to the parking spot or the gate. From this point on, only the options for the final destination airport are available—that is, the end of the journey.

  13. The taxiway display worked up until FS20’s SU5. After that, this very useful feature was removed. I find this feature very important when landing at larger airports and receiving the instruction from air traffic control: “Taxi to the general aviation parking area.” PC users can then zoom in on the airport in Little Navmap to find any parking spot. Xbox users end up wandering around the airport for a while, trying to find one. For this reason, this feature should definitely be reintroduced.

@ Chewwy94

I would appreciate it if you could mark the items that have already been added to the error database and those that still need to be added.

Topic removed from SU7 Beta category as topic is neither a note of a regression, nor feedback on something in the latest Beta build.

To add to the Leg 2 onwards oddities: on the first leg POI markers - such as town pins - can be freely toggled on and off, if you click ‘Continue’ they are fully disabled. Going back to the main menu and reentering a leg that way restores the toggle functionality.