Speedbrake

I realize that it may be considered a cheat...but I also agree with the idea that an co-pilot is supposed to exist. I was just checking features and thought it might be a bug. I was setting up my Warthog HOTAS. I had the special auto-pilot box checked but I guess I needed to reset it after the last beta patch which is what I have done and it works fine now. thanks!

The UH-1H capability to use a auto pilot in not working in the most current beta v1.2.8. It works fine in v1.2.7. Is it working in the update v.1.2.8?

Come on guys is it that hard? You have it right in v1.2.7??? New update but still no fix to the pilot's logbook. While I have the 1.2.8 beta...I haven't updated my copy of v1.2.7 because of this.

Much Too New Just a note...Lockheed turned out the 100 F-35 this past week. With it being so new and the avionics so confidential or secret you won't see enough data on this aircraft (or rather 3-aircraft - variants) for years. :pilotfly:

Check Here I think there was some type of .lua problem with the last update. You might want to check this out. http://www.digitalcombatsimulator.com/en/files/463993/ Be sure to note where you place the new .lua files. It is only the lua file not the textures in each folder.

Yep! Present and accounted for....enjoying learning to land...and land....and land!

There are a couple of posts on this topic. Some of the controls aren't yet set up to operate: Start here: http://forums.eagle.ru/showthread.php?t=113516

Create A File I don't think it is the file. Try this, create a mission by placing an A-10A (CF3) on the runway (I used Glendzhik) and just takeoff and come back around and land. See if you get anything more than Mission Start, Took Control, and Mission End in the summary. Also all the radio calls are screwed up. You can also create a mission on the A-10A going from one base to another ( again Gelendzhik to Anapa) and see if it bombs out after you land and leave the mission. BTW, I just updated to the most current build and it still does the same. You should be able to get the files here: http://www.ge.tt/5uBDB4p/v/0?c

Can anyone else verify the problems I mentioned on page 129 of this thread, log #1287??? I want to be sure it is not a problem on my side.

While I posted this under FC3, I think it is because of the update to the A-10A so I'm reposting here: I have created two short cross-country missions in the A-10A FC3 most current version. At the end of the mission the program has CTD with the comment "DCS Has Stopped Working" as it tries to go from the end of mission to the mission summary screen. Don't know if this has been reported before. It did it from flying the mission inside the mission editor as well as selecting it from a mission list outside the editor. Alienware Aurora R3 Intel ® Core i7-2600K CPU @3.4 GHz CPU 64 Bits ClockSpeed 3401 MHz Video Nvidia GeForce GTX 560 Ti 1280 MB RAM 8 GB HardDriv 2TB DirectX 11 WartHog HOTAS Track IR A-10C, BS 2, P-51D. UH-1H Huey, FC 3 There were no error logs in the game folder: saved games/DCS/logs. The crashes occurred while trying to go to the mission summary GUI. The A-10A missions where the crash occurred was going from one base to another. Another point, on another mission I created in the A-10A I took off from the runway, pulled up into a closed pattern and landed, total three minutes fifty seconds at the same base. The log only recorded three items; Mission Start, Took Control, and Mission End. I've flown it several times and it does not record takeoff or landing or give me credit in the General Debriefing Window. The system is not recording time, landing, etc. on my pilot record. I've done a similar mission editor problem for the F-15C and SU-33 and both of those work fine and record fine. It seems to be a A-10A problem.

A-10A CTD I have created two short cross-country missions in the A-10A FC3 most current version. At the end of the mission the program has CTD with the comment "DCS Has Stopped Working" as it tries to go from the end of mission to the mission summary screen. Don't know if this has been reported before. It did it from flying the mission inside the mission editor as well as selecting it from a mission list outside the editor. Alienware Aurora R3 Intel ® Core i7-2600K CPU @3.4 GHz CPU 64 Bits ClockSpeed 3401 MHz Video Nvidia GeForce GTX 560 Ti 1280 MB RAM 8 GB HardDriv 2TB DirectX 11 WartHog HOTAS Track IR A-10C, BS 2, P-51D. UH-1H Huey, FC 3 There were no error logs in the game folder: saved games/DCS/logs. The crashes occurred while trying to go to the mission summary GUI. The A-10A missions where the crash occurred was going from one base to another. Another point, on another mission I created in the A-10A I took off from the runway, pulled up into a closed pattern and landed, total three minutes fifty seconds at the same base. The log only recorded three items; Mission Start, Took Control, and Mission End. I've flown it several times and it does not record takeoff or landing or give me credit in the General Debriefing Window. The system is not recording time, landing, etc. on my pilot record. I've done a similar mission editor problem for the F-15C and SU-33 and both of those work fine and record fne. It seems to be a A-10A problem.

Data Alienware Aurora R3 Intel ® Core i7-2600K CPU @3.4 GHz CPU 64 Bits ClockSpeed 3401 MHz Video Nvidia GeForce GTX 560 Ti 1280 MB RAM 8 GB HardDriv 2TB DirectX 11 WartHog HOTAS Track IR A-10C, BS 2, P-51D. UH-1H Huey, FC 3 I'm not sure where any logs are stored. Another point, on another mission I created in the A-10A I took off from the runway, pulled up into a closed pattern and landed, total three minutes fifty seconds. The log only recorded three items; Mission Start, Took Control, and Mission End. It did not record takeoff or landing or give me credit in the General Debriefing Window. The system is not recording time, landing, etc. on my pilot record. I've done a similar mission editor problem for the F-15C and SU-33 and both of those work fine. It seems to be a A10-A problem.

I have created two short cross-country missions in the A-10A FC3 most current version. At the end of the mission the program has CTD with the comment "DCS Has Stopped Working" as it tries to go from the end of mission to the mission summary screen. Don't know if this has been reported before. It did it from flying the mission inside the mission editor as well as selecting it from a mission list outside the editor.

Glad to see this get a section of it's own!!!

Thanks ! Thanks for the response!!!

Latest Update to 1.2.5 For the A-10A changes. Wags: Fixed autopilot (you may need to delete your input file to reset) Three questions: (1) Where is this file? (2) Does it only effect FC 3 aircraft? (3) If I delete it will I have to reset all my DCS aircraft settings, A-10C, BS2, UH-1H Huey, P-51, FC3? :joystick:

New Question Based on this statement: These updated FC3 aircraft will be made available for FREE to Flaming Cliffs 3 customers. Does that mean that I can load these two (so far) as individual modules and the system will read my CF3 serial number so I can have them on my main page as individual aircraft selections without the $???

New Modules Dang...that was quick...Thanks!

Are the newly released DCS modules for the A-10A and Su-25 the same that are in Flaming Cliffs 3? If not, if I already own FC3 can I add those two modules to my simulation...will they be included at additional no cost?

There may be more at lockonfiles.com but they are probably for an older version. You can download them, open them up in the mission editor and then resave them. That may update them????

I have the same thing - it only shows Black Shark and not BS2. I think it is in EDs programming. I wouldn't worry about it, you should get all the program updates for what is installed when they are released.

A Question: How does one program the INCR/DECR control on the Warthog throttle quadrant? Any of the other switches you can just hit add and move it to get the correct value. :joystick:

LOW RPM Toggle Switch There is a toggle switch next to the fuel switch on the left panel which shuts off the warning....until the next time you go low RPM.

Go for WARTHOG! Cougar was great....really used mine to the max but when a spring retaining bracket broke I went with the Thrustmaster Warthog HOTAS....best move I've made in simulation. You will need rudder pedals too for Black Shark, P-51 and the Huey. Seltek works great!

Even Better It's even better in the A-10C when you have a Warthog HOTAS with the world at your fingers.:pilotfly: