> The hang glider is using the UIUC fdm, right? Perhaps that is using a > float (6-7 digits of precision) to represent it's initial > conditions ... or somewhere in the startup pipeline or the flightgear > interface to the uiuc > model, the initial lon/lat is stored as a float?
Curt, you pointed me in the right direction! But it's the other way around. The UIUC-Version of the hang glider works perfectly. The JSBSim-Version is wrong. Further investigations with several planes show that only (but all) JSBSim-aircrafts are affected! I've tested the ASW20-JSBSim, C172p and Rascal110-JSBSim. The YASim- and UIUC-aircrafts work fine (ASK13, bo105, Rascal110-YASim)! It seems that we have a problem with the FG/JSBSim-interface or it's a rounding error during JSBSim-initialisation?! Summarizing my observations: - immediately after FG is started the property browser shows the correct values - this values hold true as long as the splash-screen appears - as soon as the splash-screen disappears and the plane pops up, the --lon/lat values jump to the wrong (rounded?) values - I also noticed that the "correct" values in the property browser are displayed with the same numbers of digits as typed. Simultaneous with the jump to the wrong values the number of digits increases to their count for "double" values Maybe this observations help to debug this issue. Best regards D-NXKT ------------------------------------------------------------------------------ This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
