Jump to content

DocP

Members
  • Posts

    14
  • Joined

  • Last visited

Everything posted by DocP

  1. Thanks rob10, I did reset the windows calibration to default as per a Thrustmaster recommendation. Did not seem to help, the windows game controller app still indicated they're reversed and in game was reversed also (the invert axis option had no effect). There's something not quite right - I disconnected the throttle and stick, shut down, restarted, shut down, reconnected to a different set of usb's, restarted, windows calibration settings still were reversed but in game (DCS Ah64d, and A10CII) now work as they are supposed to. Got to believe there might be something wrong with the windows app. Again, thanks, I'm back in the air.
  2. Thanks for the reply razo+r, I inverted the axis in DCS but it still is reversed when I fly, something's not right. Thing is it worked as it should a few months ago before I took a break from DCS. Obviously there have been a few updates to W11 since then, I'm guessing one of them may have messed me up.
  3. Recently re-connected my thrustmaster throttle and stick to my W11 system. The throttle axis (both throttle and slider) are reversed - push up throttles down and pull back throttles up, same with the slider. I've followed Thrustmaster's advice as to resetting the W11 calibration to default and re-installing the drivers - no joy. I'm aware of the 'invert' option when tuning the axis but that seems like a work-around. Anyone have this problem, if so how did you fix it? Thanks.
  4. Recently got back into DCS, attached all my peripherals (TrackIR, Thrustmaster Warthog throttle and stick, Logitech rudder pedals). Running WIndows 11 current patch level. The throttle inputs seem to be reversed. Any ideas? I know I can tune the axis in settings but I'm wondering if there isn't something in Windows causing this. Thanks in advance.
  5. Thanks Sabre. Just got back into town (Thanksgiving here) and will give these a shot later today.
  6. Ok - thanks. FYI I'm running the 1.2.16 version.
  7. A-10A mission name The name of the mission that is not working is: FC3-A-10A-Gory Gori.miz Thanks
  8. Trying to get back into this simulation in anticipation of DCS 2 and the NTTR map and thought I'd go back and play the A10A missions for fun. No joy. As far as I can tell the mission just doesn't work as the briefing describes. I opened the mission up in the editor and reviewed some of the triggers and other details and found all sorts of 'problems'. Just curious as to other people's experience with this mission or if anyone knows where an updated version might be located. Thanks, DocP
  9. Yes, works as you described. Radio F10 option appears at the 'correct' time, packages all wait for my command to push, affirm the push command, and the radio F10 option disappears. Now if I can just learn how to fly and survive the hostile environment :)
  10. For what it's worth I took a look at the details of this mission with the ME. One of the 'push triggers' was 'if any of the blue coalition is in any of the CAP zones then set the push flag'. At mission start the B52 was in one of the CAP zones. I changed the trigger to not include those zones and viola - still difficult but now it is playable.
  11. I'll have to play it again to know for sure - but I don't think I've received confirmation that the elements have pushed. Going to take another look at the mission with the ME to see what might be wrong with me/it. Thanks again, DocP
  12. Thanks for the reply - I'm all patched up to the current level so I'm assuming I have the 'tuned' missions in the campaign. I do manually push them from orbit (I've done it a number of times from different locations WP3, WP4 etc.) and still no joy. Weird thing is that even after I push them using the radio comm option F10 that option doesn't disappear from the menu list - it did in mission 5. I'm relatively new to this so I'm not ruling out pilot error but ...
  13. Survived through the first 5 missions of this campaign but am stuck at mission 6. Seems that no matter what I do the SEAD 3 group doesn't release from their orbit waypoints until it's too late to help the strike package - everyone gets shredded by the SA'a around Mozdok. Other than editing the mission does anyone know what the trick is to winning this? Thanks to all - this is a lot of fun.
×
×
  • Create New...