sirrah Posted June 17, 2011 Posted June 17, 2011 Hey there, I'm having trouble with the startup sequence for dcs A-10c. At the point where I need to set the left and right throttle to idle the "RAlt+Home" and RCtrl+Home" do not respond. The throttle just stays in cut off.. I'm absolutely sure I did not forget any of the required steps for engine startup. Even when following training mode step by step, both throttles stay in cut off Any ideas? Is it a known issue? (BTW: I'm using a HOTAS Cougar and made sure it is set to idle before startup. Also changing the LAlt+Home combination keys to something simple wont help) System specs: i7-8700K @stock speed - GTX 1080TI @ stock speed - AsRock Extreme4 Z370 - 32GB DDR4 @3GHz- 500GB SSD - 2TB nvme - 650W PSU HP Reverb G1 v2 - Saitek Pro pedals - TM Warthog HOTAS - TM F/A-18 Grip - TM Cougar HOTAS (NN-Dan mod) & (throttle standalone mod) - VIRPIL VPC Rotor TCS Plus with ALPHA-L grip - Pointctrl & aux banks <-- must have for VR users!! - Andre's SimShaker Jetpad - Fully adjustable DIY playseat - VA+VAICOM - Realsimulator FSSB-R3 ~ That nuke might not have been the best of ideas, Sir... the enemy is furious ~ GUMMBAH
MackTheKnight Posted June 17, 2011 Posted June 17, 2011 Make sure your throttle is zeroed out and calibrated. If your throttle is even slightly past 0, you won't be able to move them over the detents. A buddy of mine had the same issue with his CH throttle and calibrating the throttle solved it.
=Panther= Posted June 18, 2011 Posted June 18, 2011 Cycle your Cougar Throttle to max and back to idle a few times. I have found that the sim doesn't recognize the input at first. Twitch Channel [sIGPIC][/sIGPIC] Virtual Thunderbirds, LLC | Sponsored by Thrustmaster Z390 Aorus Xtreme, i9 9900k, G.SKILL TridentZ Series 32GB, 1080ti 11GB, Obutto R3Volution, Thrustmaster HOTAS Warthog, TPR, Cougar MFDs, FSSB R3L, JetSeat, Oculus Rift S, Buddy-Fox A-10C UFC, F/A-18C UFC, Tek Creations F-16 ICP
jctrnacty Posted June 18, 2011 Posted June 18, 2011 same problem here, sometimes it works sometimes not. this never happened in 1007 [sigpic][/sigpic] MB MSI x570 Prestige Creation, RYzen 9 3900X, 32 Gb Ram 3333MHz, cooler Dark rock PRO 4, eVGA 1080Ti, 32 inch BenQ 32011pt, saitek X52Pro, HP Reverb, win 10 64bit
ED Team Olgerd Posted June 18, 2011 ED Team Posted June 18, 2011 Try to calibrate the throttle to set 0 slightly above of the physical limit of the throttle movement. This would help if the axis is noisy. [sIGPIC][/sIGPIC] К чему стадам дары свободы? Их должно резать или стричь. Наследство их из рода в роды Ярмо с гремушками да бич.
MemphisBelle Posted June 18, 2011 Posted June 18, 2011 BTW: I'm using a HOTAS Cougar and made sure it is set to idle before startup. Also changing the LAlt+Home combination keys to something simple wont help) Dont change the settings...if you set the Throttle keys to a new one so set them back to default (it´s better for your Profile for later installations) The problem in DCS is that the modifier is bad explained. It says Key + modifier...but in fact it is modifier + key that works. The Keycombination in the option says Home + RAlt for the left throttle and Home + RCtrl for the right one. Try to start up the engines over your keyboard first before try to use your stick. Hold RCtrl or RAlt first before pressing Home key. That should work. After that redefine the keysettings for your stick. For making sure that you made everythings correctly take a look into my start up tutorial. If all that doesnt work, record a track and put it in here. BlackSharkDen | BSD Discord | DCS Tutorial Collection
Murf7413 Posted June 19, 2011 Posted June 19, 2011 I am having the same issue... except that doing the keyboard works fine for the starting procedure... after the engines are started my throttle works fine... except when pulled to cut off... the engines don't cut off. I have calibrated the throttle with the CCP... but no joy in movement until the engines are started by way of the keyboard throttle idle set. intel i7 960, Liquid cooled case, Vista 64bit, 8MB RAM, nVidia GTS250 XLR8 Extreme Performance 1MB, TM COUGAR HOTAS
MemphisBelle Posted June 19, 2011 Posted June 19, 2011 (edited) except when pulled to cut off... the engines don't cut off. I have calibrated the throttle with the CCP... but no joy in movement until the engines are started by way of the keyboard throttle idle set. You know, in those cases a System description and an information about what Joystick you use would be helpful to help you. Edited June 19, 2011 by MemphisBelle BlackSharkDen | BSD Discord | DCS Tutorial Collection
Murf7413 Posted June 19, 2011 Posted June 19, 2011 You know, in those cases a System description and an information about what Joystick you use would be helpful to help you. In this particular instance I did not believe a system description was necessary, as I am not having a performance issue.... and since the original post stated the issue was with the TM COUGAR throttle... I took it as a given that is what the thread is about... But, Yes... I too am using the TM COUGAR HOTAS setup... However... if system specs are essential... I am using an intel I7 960, Vista 64bit, with 16MB Corsair DDR3 RAM, and a GTS250 XLR8 1MB vid card Later... intel i7 960, Liquid cooled case, Vista 64bit, 8MB RAM, nVidia GTS250 XLR8 Extreme Performance 1MB, TM COUGAR HOTAS
sarancha Posted June 19, 2011 Posted June 19, 2011 Calibrate same problem here, sometimes it works sometimes not. this never happened in 1007 Calibrate your joystick. In that case it works for me perfectly.
sirrah Posted June 20, 2011 Author Posted June 20, 2011 Hey guys, thanks for all advise. Like most cases it was something very simple I forgot to check before. In the options menu I checked my throttle axis settings. For some reason the axis tune settings of my throttle were incorrect. I messed around with the Y, X and curve options in such a way that my throttle could never been set to idle. (I think this mistake happened when I was adjusting the deadzone and curve lines of my rudder pedals and stick) System specs: i7-8700K @stock speed - GTX 1080TI @ stock speed - AsRock Extreme4 Z370 - 32GB DDR4 @3GHz- 500GB SSD - 2TB nvme - 650W PSU HP Reverb G1 v2 - Saitek Pro pedals - TM Warthog HOTAS - TM F/A-18 Grip - TM Cougar HOTAS (NN-Dan mod) & (throttle standalone mod) - VIRPIL VPC Rotor TCS Plus with ALPHA-L grip - Pointctrl & aux banks <-- must have for VR users!! - Andre's SimShaker Jetpad - Fully adjustable DIY playseat - VA+VAICOM - Realsimulator FSSB-R3 ~ That nuke might not have been the best of ideas, Sir... the enemy is furious ~ GUMMBAH
mvsgas Posted June 20, 2011 Posted June 20, 2011 :D You kids and you nice toys This never happens with my cheap, 10 year old SideWinder Precision 2 :joystick: To whom it may concern, I am an idiot, unfortunately for the world, I have a internet connection and a fondness for beer....apologies for that. Thank you for you patience. Many people don't want the truth, they want constant reassurance that whatever misconception/fallacies they believe in are true..
jctrnacty Posted June 20, 2011 Posted June 20, 2011 my problem solved clean reinstall [sigpic][/sigpic] MB MSI x570 Prestige Creation, RYzen 9 3900X, 32 Gb Ram 3333MHz, cooler Dark rock PRO 4, eVGA 1080Ti, 32 inch BenQ 32011pt, saitek X52Pro, HP Reverb, win 10 64bit
Fakum Posted June 20, 2011 Posted June 20, 2011 I am still having problems relative to the initial post, not sure if these adj are to be done within the Cougar Control Panel, ot within the axis adjustments in the game control section? I see comments about recalibrating, I assume it is meant within the Cougar Control panel, but I see comments about setting to "0", I have tried 2 manual calibrations in Cougar, and my range for Throttle back to forward are from 571 allthe way back to 96 all the way forward? Im missing something here? I am not having any issue with the Cougar HOTAS except this startup procedure where the throttle wont respond until AFTER I use the keyboard to move both to IDLE? Thanks for any help guys Windows 10 Pro - 64 Bit / ASUS ROG Strix B650E-F Gaming / AMD 7800X3D / G.Skill Trident Z5 NEO 64GB DDR5 6000 Ram / SSD M.2 SK hynix Platinum P41 2TB / MSI Gaming GeForce RTX 4090 SUPRIM Liquid X 24G / SteelSeries Arctis 7 Headset /LG-Ultragear 38" IPS LED Ultrawide HD Monitor (3840 x 1600) / Track IR4 / Thrustmaster TPR Pendular Rudder Pedals / Virpil HOTAS VPC Constellation ALPHA-R & VPC MongoosT-50CM3 Throttle
Bulletstop Posted June 21, 2011 Posted June 21, 2011 We usually have our specs in the signature so it alleviates the issue of what are your specs. I find if my throttle is off even a little I can not start the engine using the key commands. Just verify that how ever you calibrate the joystick, the throttle is in fact 0 at 0. Bullet I7 4790K running at 4390 with a gigabyte board with 16 gigs of ram with an Asus gtx 660-ti and 2 tb of hard drive space on 2 wd hard drives. A X-65F Hotas with trackir4 and pro combat peddles. A kick butt home built machine unfortunately running a windows 7 OS.
dbeaty Posted June 22, 2011 Posted June 22, 2011 (edited) I have a very old set of sticks, yet whenever I start up I never touch the actual sticks until I throttle up to taxi out. Also, I do not use the sync throttle position at start in options. During the start up sequence, left engine start R-Alt Home and right R-Ctrl- Home, the virtual throttles advance as expected. But I've noticed I do have to carefully press them quickly - left engine start - wait for spool up, RPM to stabilize. Then Right. As a new pilot, this sequence was not as intuitive as the tutorial presented. There is a slight delay from hitting start keys and the spool up. Hitting the keys multiple times, I think can cause further problems modeled in the sim - where one engine will not come up to full RPM. Also, I've noticed that if I hit the right engine start up before the left one is spooled up, sometimes, it will start up delayed - 10-20 seconds later on it's own. Not sure if that is how it works in the real world or not. Edited June 22, 2011 by dbeaty Asus P6 MB i7 6GB OC'd 3.8Ghz Win 7 64bit Cogage Cooler Radeon 6870 OC'd 975Mhz Core 1250 MHz RAM TM Afterburner TrackIR [sIGPIC][/sIGPIC] Aardvarking it
Fakum Posted June 22, 2011 Posted June 22, 2011 We usually have our specs in the signature so it alleviates the issue of what are your specs. I find if my throttle is off even a little I can not start the engine using the key commands. Just verify that how ever you calibrate the joystick, the throttle is in fact 0 at 0. Bullet on my Cougar Hotas, my raw data range indicates a range from 0% to 100% of 96 to 571, how do you zero it in CCP? Windows 10 Pro - 64 Bit / ASUS ROG Strix B650E-F Gaming / AMD 7800X3D / G.Skill Trident Z5 NEO 64GB DDR5 6000 Ram / SSD M.2 SK hynix Platinum P41 2TB / MSI Gaming GeForce RTX 4090 SUPRIM Liquid X 24G / SteelSeries Arctis 7 Headset /LG-Ultragear 38" IPS LED Ultrawide HD Monitor (3840 x 1600) / Track IR4 / Thrustmaster TPR Pendular Rudder Pedals / Virpil HOTAS VPC Constellation ALPHA-R & VPC MongoosT-50CM3 Throttle
Caspar Posted June 22, 2011 Posted June 22, 2011 I had kinda the same issue, no problems with left engine but the right engine didnt start, and the right throttle in the cockpit didnt move from off to iddle with the "RCtrl+Home"-hotkey. Im on a laptop, and I have to press the "Fn"-key to activate the "Home"-key. As said, the left engine worked with "R-Alt+Home, but no responce on right engine. I sat up new keys for right engine.. and it worked. Somehow my "RCtrl+Fn+Home"-combo must be broken on my Laptop.
Tailspin45 Posted June 22, 2011 Posted June 22, 2011 (edited) Just a note that perhaps is more in response to other posts but applies here as well: there are few cases where a special sequence is required by the sim to do something, say, start the engines—or to do anything else for that matter. If you have the proper equipment on (e.g. battery, inverter, fuel pumps and APU) the engines will start. (Yes, I understand that the issue here is the zero point with the Cougar throttles, and yes this is therefore a little off topic but still relevant, I hope). I make this point because some "toy" sims require that you touch certain buttons in a certain order for the thing to work. Thus, some people seems to think, I gather, that if you don't turn on the O2 and then check the indicator as part of the pre-start checklist the engines won't start, which is not the case. DCS A-10C is about as real as you can get and the systems do what they do IRL so if you supply air, fuel and a spark you will get fire (suck, push, bang, blow). I'm making an issue of this only out of admiration for the incredible fidelity of this sim, and to alert new folks that you don't need to treat it as a Myst puzzle. It is deterministic, and works as it should. That said, there are a few procedures that, thanks to physics and technology, do require that events take place in certain order such as an air start. But I hope it's clear that's a different issue. Edited June 22, 2011 by Tailspin45 typos Blue Skies & Tailwinds tailspinstales.blogspot.com
Orsi Posted June 22, 2011 Posted June 22, 2011 I using a X52 (normal) but always i'll start the star-up sequence i have to press R-alt Home to start the engine? Can I just move the stick to start the engine?
159th_Viper Posted June 22, 2011 Posted June 22, 2011 I using a X52 (normal) but always i'll start the star-up sequence i have to press R-alt Home to start the engine? Can I just move the stick to start the engine? No. The throttle movement from Off to Idle over the detent on the HOTAS Warthog is not an axis movement and thus cannot be replicated on the X52 by merely moving the throttle. Novice or Veteran looking for an alternative MP career? Click me to commence your Journey of Pillage and Plunder! [sIGPIC][/sIGPIC] '....And when I get to Heaven, to St Peter I will tell.... One more Soldier reporting Sir, I've served my time in Hell......'
Tailspin45 Posted June 22, 2011 Posted June 22, 2011 I had kinda the same issue, no problems with left engine but the right engine didnt start, and the right throttle in the cockpit didnt move from off to iddle with the "RCtrl+Home"-hotkey. I had the same problem with Thrustmaster HOTAS and solved it by deleting the entire Throttle column in Options|Setup|Controls and then using Load to pick default set. Seems hard to imagine that keyboard could have same issue, but might be worth deleting keyboard bindings and reloading them. Blue Skies & Tailwinds tailspinstales.blogspot.com
Recommended Posts