[Flightgear-devel] New idea for flightgear
Dear sir/madam I am a great fan of flightgear. I would like to point out that crashes in flightgear is not simulated. so add simulated crashes in the next flightgear version. -- ASHIRWADA WIJERATHNA -- 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
Re: [Flightgear-devel] Improved Scenery Data Question
Hi John: snip I'm wondering if anyone has any suggestions on getting this data into the system so users can start flying over it. snip I maintain a mirror for flightgear. (ftp://ftp.kingmont.com and http://kingmont.com) You might try contacting Curtis and see how you would go about putting some of your stuff up on that site! You would be welcome to use it as far as I'm concerned (I don't fool with it except to pay the bill! grin). jj -- 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
[Flightgear-devel] Positioning Aircraft: accuracy
Hello, I noticed that positioning an aircraft at FG startup with --lon= and lat= has only a limited accuracy. It seems that only the first 7 digits are read. This leads to an uncertainty of several meters/feet! For example lon=11.379070 --lat=47.306263 is needed to place our hang glider directly in front of the ramp (LOWI-Scenery). Unfortunately the hang glider pops up several meters right of the ramp. I found out that FG internally uses this (rounded) values: --lon=11.3791 --lat=47.3063. Same issue with input via the Menu Location/Position Aircraft In Air. Only positioning via the property browser leads to exact results. Maybe someone could fix this at the next opportunity?! Thanks in advance 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
Re: [Flightgear-devel] Positioning Aircraft: accuracy
Hi, Am 2013-06-23 22:27, schrieb D-NXKT: I noticed that positioning an aircraft at FG startup with --lon= and lat= has only a limited accuracy. It seems that only the first 7 digits are read. This leads to an uncertainty of several meters/feet! For example lon=11.379070 --lat=47.306263 is needed to place our hang glider directly in front of the ramp (LOWI-Scenery). Unfortunately the hang glider pops up several meters right of the ramp. I found out that FG internally uses this (rounded) values: --lon=11.3791 --lat=47.3063. How have you checked these values? I've just tried it myself and in the property browser exactly the same values appear. Same issue with input via the Menu Location/Position Aircraft In Air. Here by default values are shown with four decimal places, but also values with higher precision are accepted. Only positioning via the property browser leads to exact results. Maybe you are using an operating system with a low precision atof? In the property browser strtod is used to convert the number whereas for the dialog and arguments atof is used. Tom -- Thomas Geymayer www.tomprogs.at / C-Forum und Tutorial: www.proggen.org Student of Computer Science @ Graz University of Technology --- Austria -- 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
Re: [Flightgear-devel] Positioning Aircraft: accuracy
Hi Tom, How have you checked these values? I've just tried it myself and in the property browser exactly the same values appear. I started FG with --lon=11.379070 --lat=47.306263 --heading=155 --units-meters --on-ground and found me at --lon=11.3791 --lat=47.3063. Manual input in the property browser moved me to the correct position. Maybe you are using an operating system with a low precision atof? In the property browser strtod is used to convert the number whereas for the dialog and arguments atof is used. I'm using Suse 12.3 64bit. How can I check the atof precision? Thanks for the quick response 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
Re: [Flightgear-devel] New idea for flightgear
Hi Ashirwada, this feature is implemented but disabled by default in FG's source code. To enable it, if you really want that (think twice), edit file src/AIModel/AIMultiplayer.cxx and alter the false to true in FGAIMultiplayer::FGAIMultiplayer() : FGAIBase(otMultiplayer, false) This action, of course, requires FG to be recompiled. hth Alex Dear sir/madam I am a great fan of flightgear. I would like to point out that crashes in flightgear is not simulated. so add simulated crashes in the next flightgear version. -- 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
Re: [Flightgear-devel] Positioning Aircraft: accuracy
Hmm, everything is fine if I use a different plane. Seems to be a hang glider specific problem. Monitoring the latitude and longitude variabel from the very beginning shows, that both variables have at first indeed the correct values. Then the latitude value suddenly jumps from 47.306263 to 47.306206. Sorry for the noise. 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
Re: [Flightgear-devel] Positioning Aircraft: accuracy
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? On Sun, Jun 23, 2013 at 5:27 PM, D-NXKT d_n...@yahoo.de wrote: Hmm, everything is fine if I use a different plane. Seems to be a hang glider specific problem. Monitoring the latitude and longitude variabel from the very beginning shows, that both variables have at first indeed the correct values. Then the latitude value suddenly jumps from 47.306263 to 47.306206. Sorry for the noise. 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 -- Curtis Olson: http://www.atiak.com - http://aem.umn.edu/~uav/ http://www.flightgear.org - http://gallinazo.flightgear.org -- 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
