RouteMgr security: don't allow overwriting arbitrary files.Fix new splash screen with Rembrandt enabled.Fix broken build due to undef'd ref in test_flightplan.Abort with a clear error message for invalid uses of -config inside a config file.Update (obsolete!) package/debian/rules to use the renamed desktop file.Added support for multiplay/generic/bool packed into three ints of 31 bits.Add and improve translations in package/.: add Spanish and Catalan translations.Fix issues with package upgrades on Windows.Fix build errors in zlibstream*.cxx, re-enable their compilation.Add new test trying to read max amount with ZlibDecompressorIStreambuf::xsgetn().zlibstream classes: add constructors with sink semantic based on std::unique_ptr.Minor change to simgear/io/iostreams/zlibstream_test.cxx.gcc fails to catch std::ios_base::failure due to an inconsistent C++11 ABI between headers and libraries.Added SGStringValueMethods property implementation.SGPath::set is called by SGPath::operator=(const char*p) so it needs to be unconditionnally compiled.Merge /u/accek/simgear/ branch prop-strings into next.Packages allows thumbnails per variant.alternative terrain engine - SGMesh utilizing pagedLOD.Disable GDAL, and compiling new terrain engine by default.Flags ENABLE_GDAL and ENABLE_OPENMP are now carried over to FlightGear.Adjust some messages to be developer-mode.move TS dns lookup into the worker thread.Fix handling of SG_LOG()'s second argument.Use std::unique_ptr to avoid leaking logging.Make debugClassToString a public static.Add -fPIC to make FlightGear's shared library linking for fgtestlib happy.Fix build failure due to missing include.Package APIs to support multiple primary aircraft.Define SG_DEPRECATED, remove unused DEPRECATED.Improve warning of object in wrong bucket.New string helper function: property path matching.Add classes to ease writing command line parsers with GNU-style options handling.Change SGPath::pathListSep into a const char array of size 2.Fix misleading indentation in sg_path.cxx (g++ warning).argparse.cxx: allow arguments consisting of a single '-'.Fix (hopefully) sim4_t class initialization problems.strutils::unescape(): fix off-by-one error.strutils::unescape(): fix handling of hexadecimal escape sequences.zlibstream*: use C++11 scoped enumerations instead of C-style enums.zlibstream.cxx: explicitly mark as virtual the inherited virtual methods.Fix bug "dns timeout, no terrasync servers found".Add function template simgear::strutils::readNonNegativeInt().Fix MSVC warning: redefinition of default template parameter.Make position properties work for relative positions too.materials.xml support for osm2city Buildings etc.Change license from GPL2+ to LGPL2.0+ for the SimGear files I wrote.Allow animations to take an object as the centre and axis.Fit the property definied positions to the axis definition by negating them.Fix animation axis text for new calling conventions.Fix mesh visibility on pick animations.Fix a bug when using properties instead of a fixed position.The App provides you the IP address of the Android device.You will need this information in the following step.Changelog for FlightGear from 2017.1.1 to 2017.2.1 simgear Here you can enter a port number for the communication (default port number: 5502). I recommend starting with theĪndroidpfd787.xml protocol file which uses basic properties which areīelow you can find installation instructions for the three most common ways of starting Flightgear: command line, fgrun, and fgo!.įLIGHTGEAR SETUP (started from command line)ġ Download the protocol files (download links at the end of this page): You can try any of the protocol files provided here. Most probably will work with the BASIC configuration. *Other aircraft are not fully supported (yet), but they The following table explains the planes that supported and the protocol files that are needed. These are examples of the available PFDs:Įach selected plane uses a protocol file. Were not implemented however, workarounds may be available in the nearįuture. Some of these characteristics are not exposed in the Flightgear property The other PFDs include specific characteristics for eachĪircraft such as ILS indicators, DME, autopilot settings, Of them (Of course, there is no way I could have the chance to test all In Flightgear, and therefore this PFD should in principle work with most These are common properties for most of the planes Navigation information such as speed, altitude, heading, pitch, roll,Īnd vertical speed. WiFi network by using the generic protocol. It reads internal Flightgear properties through the The App "Flightgear PFD" currently supports 5 Primary Flight Display (PFD): BASIC, Boeing 777, Boeing 787-8, Boeing747-400, Airbus 330,Īnd Airbus 380.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |