Long haul - no problems except

I just completed a long haul EGLL-KSFO without major issues. Scenery and weather was priceless and traffic light, although I’m seeing less labelled craft.

It may be me but in the EFB when I’ve set the route using IFR, at a cruise altitude of 390, I am persistently asked to drop down to 12200 when later in flight.

If I later ask to incrementally increase height I get the drop down instructions again.

I can turn the ATC sound off, but there must be something I’m doing wrong.

Or is it a Beta 3 feature?

I should also add that unlike any other release, with this I have been able to land and turn around and return without q crash, or having to restart the sim.

Therefore Ive managed egll-ksfo-egll-ksfo-egll, which I think is pretty good!

When I drive from Sydney to Melbourne, my car does it without a hitch. Even the return trip! But that’s not something I’m praising it for—it’s just what I expect!

1 Like

I find it quite strange how you can do multi-leg trips without issue but if you tried to return to the world map before continuing with the flight you’d have all kinds of problems. But this sim does love a weird quirk

I haven’t attempted a multi-leg flight on 2024 as I usually log my flights on a virtual airline which requires the logbook entry. A multi-leg flight such as your “egll-ksfo-egll-ksfo-egll” would just show egll-egll with it having taken over a day to complete. Whereas I do them all the time in 2020 as you can get the logbook entry without ending the flight by assigning a key to toggle master battery I think it is or, in the case of the 747, just shutting down the engines. I do miss that feature in 2024

On you question, I have encountered all kinds of weirdness with ATC. On my last flight on 2024, my AI ATC assist decided to request cancellation of my IFR flight plan out of nowhere. So chances are it’s just yet another bug

@Asobo
A new possible configuration option would be:
“log complete aircraft shutdowns within a session as separate flights”

And by the way…
Ask the user if a flight should be logged if

  • the sim crashed during the flight
  • the flight does not end with a landing
  • the flight was shorter then x minutes

I have long thought that a logbook entry should automatically be created after landing and the aircraft has come to a stop. This was the criteria for completion of legs on bush trips on 2020 and is the reason why bush trips aren’t in 24 yet

Sometimes I have a lot of landings and takeoffs in a row during flights. I don’t want to have a logbook entry for each of these hops. In 2020, it’s already pretty cluttered. I’d like to clean it up, but unfortunately, it’s not possible. Therefore, I would appreciate it if Asobo would implement rules like the ones I suggested above.

I have some entries with 0 flight seconds in my logbook.