Nightdare

Shouldn't be that hard to get that connector on a new USB cable with a bit of solder and heat shrink, I should know, I once replaced all the wires on my Saitek Rhino Throttle unless it's the connector itself, but I believe that's a very common JST connector anyway (Though I'll admit that finding local shops still stocking small electronic parts are getting rarer every year)

Metal saws are capable of cutting metals harder than aluminium, even if it's an aluminium alloy Whether it's safe? meh, put on a mask if the dust worries you, I'd sooner tell you to take care of any burrs and file off rough edges, because cut aluminum can be razor sharp

Good sir, you appear to be missing a cupholder

I always chalked this one up to "Pilot incapacitated" as 'the game' would show again after the airplane crashed Especially since I could switch to the RIO in the F-14 and punch both out Edit: I forgot to add, this happens using a HP G2

I have the HF8, used if for no more than a few hours total in 2 and a half years but 3 out of 8 motors failed due to broken wires, which I managed to get 2 of those working again But it isn't good advertisement when seat pad stops working because you're sitting on it

I'll see if I can wait til a next system upgrade, but that would probably be no sooner than 2027-28

I was getting better at it with my Orion2 and Kaltokri Rhino FFB, these aren't really comparable to short(er) throw CH peripherals though Since apparently people can make do with basic gear and even keyboard, Hovering like a pro seems more a learning curve than a gear problem ...speaking of curves, have you tried setting custom curves? Because 1 basic is tiny movements, which are easier with a longer throw, but having a short stick using longer sloped curves might compensate a bit ...your link doesn't show me an actual product btw

What Mods are you running, and don't the mips require extra power? Could it be an NVidia CP setting? I would clean up DCS install and then testrunning plugging in, starting with the mips, then add each peripheral until problems pop up

Hmm, seems I've lost the ability to change led settings as well as I needed the newer configurator software for my Apache collective

I'm on the old V1 Mongoost, with older software (since everything still runs fine) I'm not using the modifier function, so keep that in mind that my shift states in the configurator don't do anything This is my throttle setup in the Apache (which has two 3 position throttle/power levers), though Idle is idle, the AB travel isn't AB, but movement wise, they are just as equal Basic state (s0) = green 0-10% on the throttle is button 78 on Axis 1 / button 80 on Axis 2 ON, enabling blue lighting 90-100% on the throttle is button 79 on Axis 1 / button 81 on Axis 2 ON, enabling red lighting S5 is my covered switch set to show orange when Open, this is when I have the APU running (as closing the cover will switch the APU Off) That sounds like a dual key/Axis bind problem DCS sometimes has the bad habit of assigning certain action to new hardware, regardless if you already have these mapped on a different peripheral Go into keybind list and see what keys are highlighted when going into AB, check every device if the same action isn't assigned to other hardware as wel

Aren't those keybind files? ...and as such don't actuallly show WinWing "Support" since AFAIK 99% of these are user made? Have you tried adding your own?

Just save and load the correct keybind profile per device (and plane of course) You could also keep both throttles connected (correct profiles stil apply), but this might get a bit confusing

Not really your answer, but I believe the volume of switches can be increased separately from all other audio? The audio itself doesn't seem to be so easily filtered out though

Not even the Spiffy? Because in comparison I find the Corsair rather tame compared to that bird

For those with a Rhino FFB and Helicopters: Do you guys use the DCS Force Trim or the VP Hardware Force Trim?