Nealius Posted April 5, 2016 Posted April 5, 2016 I have the TDC key commands and the airbrakes programmed to buttons on my joystick via the Saitek software since they cannot be bound from the in-game settings. Two updates prior the airbrake bind broke but the TDC was fine. Now with the most recent update the TDC refuses to move with joystick commands, but will still work via the keyboard. Also my radar seems to be stuck in P mode even when turned on.
nomdeplume Posted April 5, 2016 Posted April 5, 2016 I have the TDC key commands and the airbrakes programmed to buttons on my joystick via the Saitek software since they cannot be bound from the in-game settings. Two updates prior the airbrake bind broke but the TDC was fine. Now with the most recent update the TDC refuses to move with joystick commands, but will still work via the keyboard. How did you use the Saitek software to program this? Is it set up to send synthetic keypresses as substitutes for when you press the button? Or if not, what is the software doing? I used to have the TDC directly configured with buttons in-game using the TM Warthog (I don't use TARGET, so just DirectInput joystick buttons). I think I've used it recently, but not completely sure as I use the axis control now. Also my radar seems to be stuck in P mode even when turned on. The radar now needs to warm up and will only start warming up after takeoff (which seems strange to me, as other radars I've seen modeled in flight sims can warm up on the ground). It'll take two minutes if you have the switch set to 'P'. If it's on SIL or fully on, the warmup period will last three minutes. The P will disappear from the radar display once complete, so you know it's okay to switch it to SIL/on.
Nealius Posted April 6, 2016 Author Posted April 6, 2016 The profiling software will send synthetic keypresses from what I can tell. I set the key commands to the default . , : ; and have changed nothing[\b] since the last three updates. Prior to this recent update it was working fine. The microstick can't be assigned in-game so I have to use the profiling software else it will function as a mouse.
Azrayen Posted April 6, 2016 Posted April 6, 2016 (edited) The microstick can't be assigned in-game so I have to use the profiling software else it will function as a mouse. Can't it? Weird. On a HOTAS Warthog, the microstick (slew control) is assignable in-game, as an axis. This is what I use for TDC. Edited April 17, 2016 by Azrayen typo
Sverre Posted April 6, 2016 Posted April 6, 2016 I don't think DCS recognise the slew control on the X55 as an axis. I have never been able to map it as one in either of the modules I own, had to use the software just like Nealius.
Nealius Posted April 7, 2016 Author Posted April 7, 2016 (edited) DCS doesn't recognize slew control, knobs, scroll wheel, or slider on the X52 either. All of those must be assigned via the Saitek software which, in the current Open Beta update, does not work. Just tested with the Su-25A as well, where I have wheel brakes assigned to one of the rotational knobs. It also fails to work with the Su-25A. This appears to be an ED problem and not a M2000 problem. Edited April 7, 2016 by Nealius
Recommended Posts