From: <fli...@go...> - 2012-04-30 18:17:55
|
Updates: Status: WontFix Comment #9 on issue 734 by bre...@gmail.com: Disabling AI traffic in fgrun disables entire AI module http://code.google.com/p/flightgear-bugs/issues/detail?id=734 Fred, the option probably made sense ages ago, when the AI module was only used for a single purpose: to process AI scenarios. Now that loads of features depend on it, it's just a bad option. Users cannot understand its consequences. And they don't want to. They want to enable/disable features they "know" (e.g. local weather/traffic/MP). User cannot understand that all these features depend on a common internal infrastructure. This is why we discussed in #248 to remove this option from the user's perspective and make sure that every individual user feature has an own enable/disable option (again: local weather/traffic/MP/...). Also, we should enable the "infrastructure module" internally, so a user doesn't need to know anything about FG internals, neither their internal switches. #248 has now been fully implemented. If a user enables traffic, then traffic is enabled (and the AI module too). If a user enables MP, then MP is enabled (an the AI module). If he enables an AI scenario, then the AI scenario is enabled (and the AI module). We still need to do the same for local weather and wildfire. So, "ai-models" are enabled automatically now and the external command-line switch becomes useless/deprecated. Hence, you could remove the "ai-models" switch from fgrun. Or, even better, alternatively provide a switch to enable/disable *traffic* instead (--enable-ai-traffic/--disable-ai-traffic). Many users would certainly like a traffic switch in fgrun, since the AI traffic module has a large performance impact - so it'd be nice if fgrun had a switch to disable it. But of course, we cannot influence what you provide in fgrun. It is your project and alone up to you to decide. I won't comment on this again. |