So I tried what happens if there's no terrain to load. My 4GB RAM need about 10min of flight to fill up completely (with a jet), which ends in a resource-wasting orgy of swapping and reswapping and so on, after 20mins my FG is completely unusable. The reason I was heading into the pacific ocean was a little research about newly introduced memory-issues. KSFO can be seen in the top left corner of the pic, the plane has a heading of 250, and it looks like going from the RWY10 in a straight line above the mountains should lead you there. I'm using the new ones for a while now, seems to work fine and it's so much accurate. I already asked if it was possible to release the intermediate version of FG with a new apt.dat and so, in it. publish screenshots of the bugs you noticed which are not known. if not, see if they are really scenery related or other part of FG related (FGRun, etc.), in case you don't know, just ask to re-read the known bugs on the wiki and see if all the ones your are annoncing are listed in it or not Moreover, we are facing a problem to properly clip roads on sea (which, in real life, is quite a common challenge Note that this also exist (even if it's a bit less common) which CLC, Result : a lake, or a river, badly defined in VMAP0, has a river going onto it, for instance here. Roads on rivers, lakes, sea, etc, this was already explained a few times: we chose to use accurate data for roads (ie: OSM), over a less accurate terrain (ie: VMAP).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |