Just change the "EchoAllParams" to TRUE in your Orciter.cfg file.AutoFCS doesn't work in Orbiter 2010.
Just change the "EchoAllParams" to TRUE in your Orciter.cfg file.
I am building Hadfield, and I use Orbiter 100830. And AutoFCS. I never miss KSC with it, even when I landed the shuttle at Wideawake. Because AutoFCS fly them to the "0.00N 0.00E" geographic point.
In your "Config\Earh.cfg" make sure there is a ":" between fhe name and the location of the base. It works. And if not, I don't know why ...
As I said : There isn't a ":" between the name (eg. KSC) and the location (eg. 20.38 28.54)Then how come all the other people in the forum were complaining about how AutoFCS doesn't work on 100830?
KSC: 20.435 28.534
Then how come all the other people in the forum were complaining about how AutoFCS doesn't work on 100830?
; === Surface Bases ===
; place additional bases or
; base directories in this list
BEGIN_SURFBASE
DIR Earth\Base
EDW: -117.92 +34.892
KSC: -80.675 +28.5208
VBG: -120.5694 +34.7345
ZZA: -1.0467 +41.6683
END_SURFBASE
In Config/Earth.cfg, it seems that there are colons already there.
Code:; === Surface Bases === ; place additional bases or ; base directories in this list BEGIN_SURFBASE DIR Earth\Base EDW: -117.92 +34.892 KSC: -80.675 +28.5208 VBG: -120.5694 +34.7345 ZZA: -1.0467 +41.6683 END_SURFBASE
Is that it? But it still won't let me select my landing site.

Cras and SolarLiner, it seems like you have some secret information or something.
change the "EchoAllParams" to TRUE in your Or(b)iter.cfg file.
That's because they are awesome enough to have secret information. :thumbup: