neilds37 wrote in Sun Nov 26, 2017 8:02 pm:Your experience with the commands is different from mine. And no, --lat and --lon DO NOT work perfectly fine!!!
I guess at this point, it might make more sense to exactly share with us what you are doing and what is happening, versus what you are expecting to happen.
I am suggesting to do so, primarily for the reason that we cannot know exactly what you are doing or what is broken for you.
For instance, there are a number of command line arguments in FlightGear that are basically mutually-incompatible, without that necessarily being obvious to most people.
And depending on what else you are telling the launcher/fgfs to do, it may actually ignore certain settings, because others take precedence, or are processed at a later/earlier time.
This is not suggesting that you are doing something wrong on your end, but rather that the way FlightGear does command line processing is rather static and at times even rather "dumb".
If in doubt, it may actually be helpful to also share your fgfs.log file.
If however you can reproduce that the same startup settings are working perfectly fine when NOT using the launcher, and ideally, when using a different launcher (fgrun, fgx etc), that would actually be helpful in trying to nail down the real problem.
Sorry if it seems that we're asking stupid questions - but you could also create a handful of screenshots and/or post a link to a youtube video illustrating the problem.