If that isn't the case, that's a clear bug and should be reported immediately (it happened once with the built-in aircraft center, which is no longer functional due to the optional Qt5 launcher being expected to be available at all times, which is a flawed assumption for obvious reasons. PS: Note that many of the issues reported here are most likely to be related to the new built-in Qt5 launcher, but that fgrun (and other launchers like ffgo) should be totally unaffected by the Qt5 launcher. Note however that it would still make sense to file a proper bug report - the people working on the corresponding features (navdb/terrasync) are otherwise unlikely to ever be made aware of any issues you are reporting here, because they don't normally follow the forum, and they expect bug reports to be made using the proper channels (devel list/issue tracker) and using sufficient information to reproduce such issues. To see if that's the case, you can simply disable this feature and/or disable scenery altogether - if fg succeeds booting, you nailed the problem. In general, these sorts of issues are usually related to either the built-in terrasync functionality and/or the navcache - if deleting/re-creating $FG_HOME does not solve the problem, it's most likely scenery/terrain related (aka terrasync). dilbert Posts: 774 Joined: Wed 9:36 pm Location: KJKA, Alabama, USA Callsign: db1 Version: 220.3.19 OS: W10,Ubuntu64 The summary menu works perfectly on my I3 desktop, and allows an immediate start using the last used combination, which is nice.
Don't necessarily assume it's quit if it has temporarily paused.Įven when you do an uninstall remains, so sometimes the temp files, like FGRUN, can still cause a problem, so I always do the above, even when I'm upgrading to a new version.įor some reason I only had this menu lapping problem with an old Celeron laptop and a new AMD A8 laptop-and haven't As I mentioned, scenery initially takes a long time to download, and sometimes appears to have stopped, so try giving it more time.
Try the same starting routine, but leaving automatic scenery downloading selected, and see if you can get it going. This usually clears any messed up temp files that may have been introduced and gives you a fresh If it were me, I would do the following: go to C:\ Users\\AppData\Roaming\ and delete I assume that when you disable automatic scenery downloading you find yourself on a runway in Spain (40n000w is now the default scenery).