Multiplayer messed up with --disable-ai-aircraft

[Groucho]

Somebody else noticed this? With the latest GIT version disabling AI aircraft from the command line by specifying the --disable-ai-aircraft switch breaks the multiplayer experience.
All pilots appear at least twice in the pilots list and all are approximately 2900 miles away (not only shown as away but they are placed 2900 miles away).

Omitting the switch or explicitely enabling it does not interfer. This is a rather strange behavior.

[Gijs]

If you mean the option --disable-ai-models the behaviour is entirely expected - the AI models system is responsible for managing the MP/AI aircraft so with it disabled MP aircraft will not work.
It might have been good if --multiplay=... forced --enable-ai-models or if --disable-ai-models disabled MP too, but that has not implemented.

/Anders

[Gijs]

Thanks for the answer. However I was extremely surprised to see everybody being shown twice in the pilots list and being placed 2900 miles away which is odd.

[Hooray]

The thing is that there are a number of startup options that depend on each other, or that may even conflict with each other.
Most users will not be aware of such dependencies, certainly not without being intimately familiar with FG.

Unfortunately, the options framework is not especially flexible - so it cannot currently identify those options that have such dependencies and tell the user about it.

It might be a good idea to start a new wiki page listing all known instances of these dependencies (i.e. parameters that have an effect on other arguments).
That way, it would eventually be possible to either extend the options framework or simply express those relationships in XML, so that GUI frontends like fgrun can get smarter.