-Pv-

Thanks for this! This gave me something to search for. The only file with that name in my old XP installation is: <installation drive>:\Eagle Dynamics\DCS A-10C\DCS Warthog\MissionEditor\Logbook.lua When I load it into notepad, it looked like it contains my flight history. For my new Win 7 installation, the only logbook.lua I find which is not a shortcut is in: C:\Users\<user name>\Saved Games\DCS Warthog\MissionEditor\Logbook.lua Copying the old file to the new location did the trick. I can now keep building on my pilot stats. Hope this helps others who need this information or want to back up the file. -Pv-

Anyone been able to identify the pilot logbook files? -Pv-

OK. Radio range makes sense. I built the mission based on a posting here somewhere saying to use that frequency in the tanker. Must have been wrong. Thanks. -Pv-

I spent some time investigating how a profile can be auto-loaded when the game is started. The Thrustmaster profiller has this feature and I see the "Clear Profile" and "Clear Startup" in the Pro Flight task tool. The poor manual doesn't mention clearly how the "startup" is used. Is this software capable of auto-starting a profile? It's tedious to always remember to choose one and I frequently switch between games. -Pv-

I tried creating a simple refuel mission so I can get the hang of it. It's certainly harder than Falcon4 and I thought that was hard. Start out in the air with CK-135 with tanking task. I have the tanker radio set to 110. I start out about a mile behind it and chase it around. I cannot get any response when contacting the tanker. I have the radios tuned. When I press \ and F6 the tanker shows as black. When I select to request refuel, the voice message is something like "request rejoin." -Pv-

Ah that's making more sense now. Never would have figured it out on my own. Many thanks Hawka! -Pv-

The first two "EASY" missions that come with the sim in the "Instant Action" are just want you want. -Pv-

I played the game for a while on XP and have since installed it on WIn7x64. I would like to transfer my pilot log and history over to the new install so I can build on what I accomplished. I'm having trouble identifying which file(s) I need to copy over and where to put them. -Pv-

I just got mine a few days ago, and it takes some getting used to not having the additional tactile position of the stick to send to the brain about how much force is being used. I have to retrain my brain. It's very doable though. I've been using a touchpad on my PC for 10 years and I'll never go back to a mouse. Getting the nulls, curves, and force levels set make all the difference. Once I got settings which felt confortable, my brain started retraining. -Pv-

Nothing fancy and yea, want to use the Pinky as a shift. Not sure how I would accomplish the same thing using the in-game mapper. I already have an SST mapping I like, just want to add a few pinky-shift keys. Besides, I just want to know how to do it. -Pv-

The SST programming manual which comes with the package is for the Cyborg X and while much of the programming is relevant, the ShiftState programing is nothing like the UI in the software I have. None of the tutorials and examples I've found on the Net are for this version of the SST. I've spent most of a day trying to figure out the ShiftState and I'm stuck. I have years of experience doing it on a Thustmaster Afterburner and was no trouble at all. The Saitek site seems dead and unsupported. Anyone mastered that feature? -Pv-

I've noticed the AI wingie(s) can stop in time for the 1st runway turnoff. With flaps fully deployed, speed break full and holding down the breaks the instant I touch down at stall, it still takes me the whole runway to stop. Something doesn't add up here. Is the Wingie using the one shot emergency break every time? Does the AI have stopping ability the user does not? -Pv-

I've gotten used to momentary external views to check. -Pv-

I would also like to see an *option* to hide the stick so I can see the status of the navigation switches and other stuff. In Falcon4 the stick is in a different position than the A10 so there is no important blocking, but in this sim where awareness is so important and 3D environments are rendered in 2D, there needs to be some compensation for the technical limitations. As far as reality, the option would not prevent realists from eating cake. Pilots cannot look straight out the back either, so if 100% reality is the only acceptable criteria, get rid of 30% of the key commands and restrict the extent of the pilot's pan as Falcon4 does. I would probably show and hide as the need arises. I too have sat in an A10 and people's bodies are more flexible than keyboard commands, even in a strapped flight suit. -Pv-