![]() ![]() Roads, rivers and shore lines are made up of straight sections with sharp angular corners. I only see some major roads and no secondary roads and the major roads only sort of follow the correct route and some take implausible routes through the mountains. In spite of it appearing that terrasync is working I am not seeing the new scenery or at least anything that looks like any of the screen shots I have been seeing here in the forums. The default scenery directory has a little over 20MB and has not had any downloaded data added. At this point my terrasync directory has about 860MB of data with the default tile and the tiles to the east and south of it. ![]() I have terrasync enabled in fgrun and I can see it getting started when I start FG or I tell fgrun to do a "Scenery Prefetch". I did a fresh install just to make sure that I didn't have anything that might be causing an issue. Thank you all.Īlan Alant Posts: 1192 Joined: Wed 6:58 am Location: Portugal Callsign: Tarnish99 Version: from Git OS: Windows 10 From what I have seen so far it is a stupendous piece of work, and gives a new way forward for the whole flightgear project. I am not sure of the best way to proceed on these matters, perhaps one of the scenery team could find a moment to help. the last is not a very good idea for a number of reasons (80 gbytes I am told, and you may have trouble with the number of files involved), but it is possible to use svn to download just the tiles that you need.įinally a clear statement of when and how to replace apt.dat in fgdata is needed. as well as the possibility of using svn checkout terrascenery-read-only. We have several ways to download scenery - describes the key ones and now needs a quick update.Īlso there is terramaster. In general, contributions to the manual target next by default, but we also apply them to the release/2020.3 branch if it makes sense.I think that a "how-to migrate" to the new scenery is probably required. On the other hand, the LaTeX source code of the manual for FlightGear 2020.3 lives in the release/2020.3 branch of getstart. Note that this link is for the next branch, where most of the development happens. You will find the source code here, at the FlightGear Git repository. You will find contacts of current maintainers in the Manual itself. ![]() Turn your head to the FlightGear developers' mailing list and you will find someone to talk about how to improve The Manual. The available README's in the FlightGear source tree or the Base Package orĪnd merge these into an appealing shape for The Manual.Your personal experience with FlightGear.It lies in the nature of FlightGear development that The Manual is always a bit behind current development. Instructions on how to get the source code are below. If you are a skilled writer and are familiar with LaTeX, please take the time to dig into the PDF or HTML version. This piece of documentation aims at being printed onto paper and being read as a reference while you are exploring FlightGear - or simply taken with you on a long trip. Manual for the development version of FlightGear ( next) 2 Manual for the development version of FlightGear ( next).1 Current Version (for FlightGear 2020.3). ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |