Now checking for plug-in osgPlugins-3.6.4/osgdb_nvtt.soĠ.23 :general Enabling ATI/AMD viewport hackĠ.30 :terrasync Starting automatic scenery download/synchronization to '/home/garrone/.fgfs/TerraSync'.ġ.62 :nasal Request detected to initialize Advanced Weather on startup.ġ.70 :nasal Loading local weather routines.ġ0.18 :nasal setWeight() - not supported for ufoġ0.36 :nasal Starting hard-coded terrain presampling > /home/garrone/src/scripts/fg.py(27)run_fgfs()Ġ.09 :aircraft Aircraft does not specify a minimum FG version: please add one at /sim/minimum-fg-version Or at least consider using a Source Code Management system such as for example svn or git.The command line is fgfs, invoked from python script.įgfs Please note that it is easily possible to corrupt your base package simply by modifying files in the wrong way, so that FlightGear may no longer work without getting a fresh base package, thus you may want to keep your modifications separate from the rest of the base package. So, even if a certain syntax or feature is supported in a different part of FlightGear, it may simply not yet be available in other ones. GUI files are usually not necessarily also available in files for different subsystems/components, as features are so far being individually implemented for each single component rather than globally. Also, while the majority of FlightGear XML files follows the basic PropertyList format, the various individual FlightGear components support different functionality and features, so tags and attributes that may be available and usable in one type of files such as i.e.Invalid XML files cannot be used by FlightGear anymore (there are also various web-based validator available, where you can simply paste contents or upload files to be checked). Once you start editing XML files, you will want to ensure that your edits are valid and don't corrupt the XML syntax, that is make sure that tags are properly closed - if you are not sure whether your edits were properly done or not, you may want to use a so called "xml validator", there are numerous free/open source tools available to help you validating XML documents, under *nix you could for example simply use "xmllint".Also, most modern multi-user operating systems feature support for file permissions, so that files and paths need to have the proper permissions set in order to be accessible.On most modern operating systems, filenames and paths are indeed case sensitive, so make sure to watch out for this, as well.watch out for whitespaces, separators and case: When referencing file names or paths, make sure that they're used properly i.e.When referencing file names or paths, always make sure that files and paths actually do exist.However, once you do modify the base package, it is important to keep track of your changes and to make sure that files are modified properly. Many interesting modifications can be done by editing base package resources, such as for example aircraft files, instrumentation files, GUI files, Nasal scripts etc. Possible pitfalls when modifying base package filesĪt some point, most users will probably want to modify FlightGear in some way or another. Try Requesting Technical Help, but only after trying the other suggestions above! If you have control device issues (keyboard, joystick.) see Troubleshooting input devices.Ĭheck out Hardware Recommendations for more information about video cards and other hardware that has been reported to work with FlightGear.If the whole system is crashing when running FlightGear, please read System Crashes.If FlightGear is crashing, please see Troubleshooting crashes.the black window), see Howto:Understand console output. If you're getting errors in the console (i.e.If you're having graphics problems, please check the list of Problematic Video Cards and Troubleshooting graphics artifacts.If FlightGear runs slowly, please see Troubleshooting performance issues and Howto:Use the system monitor.To rule out some of the most common problems, see Frequently asked questions#Problems.3 Possible pitfalls when modifying base package files.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |