I love this program ... but ...

[Guest subdriver]

OK ... I'm having great fun with FG ... but ...Just how am I supposed to save a file and replay it on demand?What's the procedure? Do I "save" before a flight or afterwards?I've tried everything but just can't seem to do it properly ...Sorry to be a pain ....John

[Guest mfranz]

>Just how am I supposed to save a file and replay it on>demand?If you tried the entries "Save flight" and "Load flight" in the "File" menu -- this is not for recording flights. This only saves a subset of the parameters in the property tree, and resets them accordingly. (This is a rather seldom used feature, and developers do often not notice when it got broken. :-)For recording/replaying flights you need to use the network options. This is described in $FG_ROOT/Docs/README.IO:example to record a flight path at 10 hz: --native=file,out,10,flight1.fgfsexample to replay your flight: --native=file,in,10,flight1.fgfs --fdm=externalWhereby "flight1.fgfs" is an arbitrary file name.

[Guest subdriver]

>>Just how am I supposed to save a file and replay it on>>demand?>>If you tried the entries "Save flight" and "Load flight" in>the "File" menu -- this is not for recording flights. This>only saves a subset of the parameters in the property tree,>and resets them accordingly. (This is a rather seldom used>feature, and developers do often not notice when it got>broken. :-)>>For recording/replaying flights you need to use the network>options. This is described in $FG_ROOT/Docs/README.IO:>>example to record a flight path at 10 hz: >--native=file,out,10,flight1.fgfs>>example to replay your flight: >--native=file,in,10,flight1.fgfs --fdm=external>>Whereby "flight1.fgfs" is an arbitrary file name.Yes ... very nice ... but one assumes that I'm running on Linux.Unfortunately I'm not!What do all us unfortunate souls at the mercy of Mr. Gates have to do? Regards,John:-wave

[Guest mfranz]

>>--native=file,out,10,flight1.fgfs>>--native=file,in,10,flight1.fgfs --fdm=external>Yes ... very nice ... but one assumes that I'm running on>Linux.No, it assumes that you are bright enough to type that in on the command line. Unix/Linux users usually are. FlightGear's command line options are the same on all supported platforms. Maybe you know a Linux user who can type that in for you? :-}

[Guest subdriver]

>>>--native=file,out,10,flight1.fgfs>>>--native=file,in,10,flight1.fgfs --fdm=external>>>Yes ... very nice ... but one assumes that I'm running on>>Linux.>>No, it assumes that you are bright enough to type that in on>the command line. Unix/Linux users usually are. FlightGear's>command line options are the same on all supported platforms.>Maybe you know a Linux user who can type that in for you? >:-}Hi,Thanks for the heads up ... !....But a little more courtesy, and slightly less sarcasm would have been appreciated in your reply.I was born in 1943, not 1973 - I may not have been brought up with the computer foremost in my life ... but I am trying to learn as much as possible, as quickly as possible.I do so hope that, obviously being bright, you know as much about life as I have learned over the years - but I assume not, judging from your helpful, but arrogant response.Best Regards, kid.John

[Guest mfranz]

>>>>--native=file,out,10,flight1.fgfs>>>>--native=file,in,10,flight1.fgfs --fdm=external>>>>>Yes ... very nice ... but one assumes that I'm running on>>>Linux.>....But a little more courtesy, and slightly less sarcasm>would have been appreciated in your reply.I watched for a while how your question remained unanswered. It's not that much fun to answer user questions, but at some point I jumped in and tried to give a correct and helpful answer. This wasn't enough for you, which is perfectly fine. But instead of asking more questions ("Where do I type this in? I'm on Windows and I'm not familiar with that kind of commands." ... or something), *you* started with unfriendly remarks. You complained about what you got and implied that the answer was incorrect -- only for Linux. I just replied in *your* tone. "One assumes ...". *That* was arrogant. But it looks like you can't take what you give.>I was born in 1943, not 1973 - [...]>Best Regards, kid.Growing old is mandatory, growing up is optional. :-}

[Guest subdriver]

>I watched for a while how your question remained unanswered.>It's not that much fun to answer user questions, but at some>point I jumped in and tried to give a correct and helpful>answer. This wasn't enough for you, which is perfectly fine.>But instead of asking more questions ("Where do I type this>in? I'm on Windows and I'm not familiar with that kind of>commands." ... or something), *you* started with unfriendly>remarks. You complained about what you got and implied that>the answer was incorrect -- only for Linux. I just replied in>*your* tone. "One assumes ...". *That* was arrogant. But it>looks like you can't take what you give.>>>>Growing old is mandatory, growing up is optional. :-}Yes. I do most sincerely agree that, on occasions, wording can sometimes be construed as being

[Guest chicken.jao]

People,I am sorry for this unfortunate discussion you guys have been had. I am myself today a Linux User, but I also am a Windows User and I think I may help.In M$Windows I think it happens that you are using some kind of user interface to launch flight gear. This interface makes the options of the command as a series of buttons and so-so, and in the end you press "Run" and the whole thing just works.What is happening is that under the hood the program look what options you entered (such as aircraft, airport and so on) and WRITES the correct command line and then launches Flight Gear.What is unsaid in this thread is that windows do have a command line mode. On Start Menu, if you go in Execute. Then there you type "cmd" (with out the ") and press OK. It should launch a command line shell (wich is a black screen and you can type commands in there).To call Flight Gear on Default options just type fgfs (and ENTER right after). It will launch FGFS (windows and all that stuff that comes with it - I think you will be on a cessna in KSFO...). Ok, if you exit FGFS, on the same shell you can type fgfs --help[ENTER]. This should give the parameters you can define on the startup of fg. What the other dude was saying in English is that with the option --native=out,10,FILE you are commanding FG to start copying the internal data to the FILE 10 times per second, meaning that ALL parameters (aircraft position, engine parameters and such) are recorded in that rate (so you are "saving your flight as you fly").To replay it you have to stop FG and then Start it again. This time, you set --native=in,10,FILE so FG will RECEIVE data from the file. Ok, but you also add --fdm=external so the simulation engine (the thing that calculate forces) will be offline and overriden by external input wich is the file you entered. FG will work as a "player". By the way --fdm means FLIGH DYNAMICS MODULE. Your caller program (wich has buttons and all the stuff) probably have this options under some kind of "Advanced" tab. Try look for it. If it doesn't, then it is command line then. Note that there are lots of options in FG so the command, depend of the options may be huge.Best RegardsJoao FranciscoAeronautical Engineer