moggel Posted December 20, 2015 Posted December 20, 2015 I'm a noob, trying to learn the A10C but I just can't crack how to start the engines in 2.0. I've read up on the sequence and tried it without any problems in 1.5 but when I press RAlt+Home (or RCtrl+Home) in DCS 2.0 nothing happens. The throttle gauges remain in the OFF position and the fans doesn't move an inch. The same startup sequence in 1.5 works fine though. I've double-checked the key bindings and they really are RAlt+Home / RCrttl+Home to ignite engines in both versions. Is this a bug in 2.0 or is there some additional step they've added that I haven't found out about? i7-3930K CPU @ 3.20GHz; 16Gb DDR3; GeForce GTX 1070; Windows 10; TM Warthog HOTAS
razo+r Posted December 20, 2015 Posted December 20, 2015 The A10C is not a FC3 style plane press lwin or rwin + home to start up or do it manually
BaconSarnie Posted December 20, 2015 Posted December 20, 2015 The startup sequence for the A10C in 1.5 and 2.0 is exactly the same. Try doing a repair, and try after that. And lo, Reverend Vegas did say "Take forth unto the infidel the mighty GAU 8 and expend its holy 30MM so that freedom will be brung upon them who knoweth not the joys of BBBBBBBRRRRRRRRRRRRRRRRRRRRTTTTTTTTTT" "Amen"
moggel Posted December 20, 2015 Author Posted December 20, 2015 The A10C is not a FC3 style plane press lwin or rwin + home to start up or do it manually I'm starting manually. It's just that the engines won't start up when I press RAlt+Home or RCtrl+Home. i7-3930K CPU @ 3.20GHz; 16Gb DDR3; GeForce GTX 1070; Windows 10; TM Warthog HOTAS
Tucano_uy Posted December 20, 2015 Posted December 20, 2015 Have you checked the key assignments? They might be different in 2.0
Blackeye Posted December 20, 2015 Posted December 20, 2015 (edited) The autostart key is RWIN+home not RAlt+home - the latter will move the throttle from off to idle. This does start then engine during the manual startup but you need to perform a couple of steps before that (do at least: battery on, inverter on, fuel pumps on, apu on and wait for 100%rpm) Also some keyboards offer the option to disable the right windows key, so you may need to rebind the autostart (cheats section) - you should double check that binding anyway. Edit: Saw that you are using manual startup. In that case visually check that the throttle is moving from off to idle when you press the shortcut. If it does you're missing some other step before that (track could help). Otherwise check the bindings. Also do you have an axis assigned to the throttle? Edited December 20, 2015 by Blackeye
moggel Posted December 20, 2015 Author Posted December 20, 2015 (edited) The autostart key is RWIN+home not RAlt+home - the latter will move the throttle from off to idle. This does start then engine during the manual startup but you need to perform a couple of steps before that (do at least: battery on, inverter on, fuel pumps on, apu on and wait for 100%rpm) Also some keyboards offer the option to disable the right windows key, so you may need to rebind the autostart (cheats section) - you should double check that binding anyway. Edit: Saw that you are using manual startup. In that case visually check that the throttle is moving from off to idle when you press the shortcut. If it does you're missing some other step before that (track could help). Otherwise check the bindings. Also do you have an axis assigned to the throttle? My keyboard does not have a RWin. I have double-checked the bindings and also tried to clear and rebind them, as per the following screen shot: (screen shot) APU is running at 100% before I try it but the throttles remain in the OFF position. Running the exact same sequence in 1.5 does fire up the engines as expected; I only see this in 2.0. How do I perform a repair? Do I need to uninstall 2.0 completely and then reinstall, or is there a better way? [EDIT] Not sure why the screen shot isn't working. I added an image with a link to a screen shot that I've uploaded to IMGUR. Using the URI in the browser address field works fine but not as a link here. Edited December 20, 2015 by moggel i7-3930K CPU @ 3.20GHz; 16Gb DDR3; GeForce GTX 1070; Windows 10; TM Warthog HOTAS
BaconSarnie Posted December 20, 2015 Posted December 20, 2015 No, go into programs/eagle dynamics/open alpha and there is a repair exe And lo, Reverend Vegas did say "Take forth unto the infidel the mighty GAU 8 and expend its holy 30MM so that freedom will be brung upon them who knoweth not the joys of BBBBBBBRRRRRRRRRRRRRRRRRRRRTTTTTTTTTT" "Amen"
Blackeye Posted December 20, 2015 Posted December 20, 2015 Have you checked your axis assignments? I have a HOTAS throttle and the keys only work if the throttle is in the off position (synchronize on).
moggel Posted December 20, 2015 Author Posted December 20, 2015 No, go into programs/eagle dynamics/open alpha and there is a repair exe I didn't find a "repair.exe" in that folder (nor in the 'bin' sub folder within). I did try running a command console in the 'bin' sub folder though, and then "dcs_updater repair". I let it run and then tried again but the throttles remain in the OFF position no matter what I do. :huh: i7-3930K CPU @ 3.20GHz; 16Gb DDR3; GeForce GTX 1070; Windows 10; TM Warthog HOTAS
BaconSarnie Posted December 20, 2015 Posted December 20, 2015 Start bar/programs(not program files)/eagle dynamics/open alpha And lo, Reverend Vegas did say "Take forth unto the infidel the mighty GAU 8 and expend its holy 30MM so that freedom will be brung upon them who knoweth not the joys of BBBBBBBRRRRRRRRRRRRRRRRRRRRTTTTTTTTTT" "Amen"
moggel Posted December 20, 2015 Author Posted December 20, 2015 Suddenly it worked. I have no idea what I did differently. I was sitting in the pit, just seeing if flaps or ailerons reacted to my stick input (which they didn't) with the APU running. Could it be that I just hadn't waited long enough before? The APU *was* at 100% before, when I couldn't get the engines to start but is there something else I need to wait for, like PSI bullding up more or something? i7-3930K CPU @ 3.20GHz; 16Gb DDR3; GeForce GTX 1070; Windows 10; TM Warthog HOTAS
moggel Posted December 20, 2015 Author Posted December 20, 2015 I have run this same sequence a few times now and, indeed, the only way I can get the throttles to hop from OFF to IDLE is actually by first moving the stick back and forth a few times. I guess this is not an expected behavior? i7-3930K CPU @ 3.20GHz; 16Gb DDR3; GeForce GTX 1070; Windows 10; TM Warthog HOTAS
Deezle Posted December 20, 2015 Posted December 20, 2015 The throttle(s) need to be all the way down before it will let you move them out of cut-off. Intel 9600K@4.7GHz, Asus Z390, 64GB DDR4, EVGA RTX 3070, Custom Water Cooling, 970 EVO 1TB NVMe 34" UltraWide 3440x1440 Curved Monitor, 21" Touch Screen MFD monitor, TIR5 My Pit Build, Moza AB9 FFB w/WH Grip, TMWH Throttle, MFG Crosswinds W/Combat Pedals/Damper, Custom A-10C panels, Custom Helo Collective, SimShaker with Transducer
Aeger Posted December 21, 2015 Posted December 21, 2015 I have run this same sequence a few times now and, indeed, the only way I can get the throttles to hop from OFF to IDLE is actually by first moving the stick back and forth a few times. I guess this is not an expected behavior? I've got a thread reporting this issue: http://forums.eagle.ru/showthread.php?t=155338 [sIGPIC][/sIGPIC]
Tucano_uy Posted December 21, 2015 Posted December 21, 2015 Hi Moggel, at least you found a work around to start the engines. Sorry I insist with the key/axis assignments, since you say it works after you move the stick, check if in the axis assignments your stick is binded to the throttle axis. If it is, delete the assignment. I see there's a bug report opened by Aeger, maybe there's a bug after all.
moggel Posted December 21, 2015 Author Posted December 21, 2015 The throttle axis was indeed also bound to rudders but clearing it didn't remove the need to move the stick around before EAC can be engaged. i7-3930K CPU @ 3.20GHz; 16Gb DDR3; GeForce GTX 1070; Windows 10; TM Warthog HOTAS
Tucano_uy Posted December 21, 2015 Posted December 21, 2015 EAC not engaging might be another issue, like not having clicking nav on the CDU after alignment or not selecting EGI.
SnorreSelmer Posted December 22, 2015 Posted December 22, 2015 What joystick are you using? If you're using the TM Warthog stick and throttle, make sure you go into the settings menu, under the MISC tab and check "Synchronize Cockpit Controls with HOTAS Controls at Mission Start". I had the same issue of having to move my throttle and a lot of the toggle switches back and forth one time before DCS registered the Off > Idle change. Also, I found this guide to be a great way to learn the start-up procedure: http://forums.eagle.ru/showpost.php?p=1655973&postcount=1 ASUS Z170-P w/ Intel i7-7700, 32GB DDR4 RAM, SSDs out the wazoo and a GTX 1080Ti, Oculus Rift CV1, TM Warthog stick and throttle, TM Cougar MFDs, MFG Crosswind pedals and WheelStandPro Warthog (w/ the custom small Warthog plate) Former F-16 Ground Crew @ RNoAF [sIGPIC][/sIGPIC]
moggel Posted December 22, 2015 Author Posted December 22, 2015 I'm using a battered old Saitek X52. Thrustmaster's Warthog is still on the list I send to Santa every year but the fat judgmental bastard still hasn't granted it! :wallbash: i7-3930K CPU @ 3.20GHz; 16Gb DDR3; GeForce GTX 1070; Windows 10; TM Warthog HOTAS
Recommended Posts