![]() /sim/rendering/max-paged-lod controls the minimum number of objects that will be kept in memory.You can control the memory usage with the following properties: WS3.0 can use a lot of memory - significantly more than WS2.0. Either set -prop:/scenery/use-vpb=true on your command-line, or in the Additional Settings part of the Settings pane of the launcher. To run WS3.0 you need to set the /scenery/use-vpb property to true at startup. If you add the airports the first time you might have to close the launcher and reopen it again to get the navigation data loaded properly into the session. When adding an additional scenery folder, you need to point to the folder immediately above the "vpb" subfolder. Using the FlightGear FlightGear_Qt_launcher both the terrain and the airport are "installed" by going to tab "Add-ons" and then add the respective folders to "Additional scenery folders". The scenery files above are compressed and include the "vpb" folder. To be recognized by FlightGear, the selected scenery (from the table above) must be located in a folder with a "vpb" subfolder, such as (EX: C:\mysceneryfolder\hawaii\vpb). Uncompress the downloaded scenery files into a folder of your choice, such as E:\MySceneryFolder. You can find them here Scenery Files Placement In addition to the selected areas above, global up-to-date WS3.0 airports have been built. If you are using merspieler's updated airports, then it will most often work fine, but there might be residuals (e.g. PNG Includes high resolution water raster from OpenStreetMap. Osm2city buildings, trees, maritime, pylons etc. 230 MB) - San Francisco Bay and San Pablo Bay PNG for most pilots this is the only scenery that works without troubles. If you set these in your scenery path ahead of any other scenery, it will pick up osm2city, scenery objects etc. If you don't wanna deal with changing your terrasync settings, you can always download sections of scenery via the links individually and added to your scenery path. As of writing () it contains all of the sceneries below (duplicates removed) and will get updated when a new Airports package is made and when Wayne provides her with new US scenery. Scenery is currently not distributed using the official Terrasync, Nia provides a terrasync compatible download, point your terrasync client to to make use of it. 2.1 WS 2.0 scenery might still be needed.Now I need to know how do I add the path and how do I set the environmental variables. Nor is there any directory labelled lib in /usr/share/flightgear. I have no idea what the LD_LIBRARY_PATH is and where to find it. The manual also talks about adding /use/local/share/Flightgear/lib to my LD_LIBRARY_PATH. It’s the same with Scenery files - for FG_SCENERY - there is no data subdirectory for usr/share/flightgear but there is usr/share/flightgear/Scenery, which I assume is what I use. The manual says I should be looking for a data subdirectory called data, but there isn’t one. FlightGear is installed to /usr/share/flightgear. ![]() The installation manual says I have to set some environment variables next.įirst it tells me to set FG_ROOT to the data subdirectory of where I installed FlightGear. I’ve installed Flightgear and uncompressed the Scenery tarballs into the /usr/share/flightgear/Scenery directory, and the additional Aircraft tarballs into the /usr/share/flightgear/Aircraft Directory. I’m using Flightgear 2.8 with OpenSuse 12.2, KDE3.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |