Nightdare

Just like the Democratic People's Republic of Korea, even though it says "Wing Fold" on the box, doesn't mean it needs to be so Also, the ergonomics between them are vastly different, in VR I'll never mistake my gear for brake handle on the PTO2 And where the PTO2 tries to give a more realistic approach, the Orion2 has it's realism end the moment you let go of the throttle handles

Hmm, just did a run, no problems to get Alt Hold to function, even at a pretty steep bank and/or pitch up (Got the regular Rhino, but that shouldn't matter) Did you keybind the pinky switch? Though I would point to keybinds and mods before I'd suspect the device if all other FFB values are working as intended, in the VP Force Configurator, did you check this: I turned my motors to get as close as possible then attached the belts (Probably could get Y a tooth closer, but I'm having no issues, so not gonna bother)

SAS switches on?

Seems you're missing one action alt hld+autopilot on+nws

I do not have a 'favorite' in my catalogue, but what I currently think is the most 'fun' to fly is the Huey It's all analog, you can throw it around quite a lot before you get into trouble (when you do, the wipe is often comedy gold), it can actually still get me queasy in VR if I get a bit too epileptic maneuvering at low speed ...but what they don't prepare you for is the incessant use of "Fortunate Son"

I see so much wrong with this, I don't know where to begin

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?

Occasionally, if I'm setting up keybinds, it's easier to switch off VR to configure commands So when I fly to try out the new controls, I only have control for views as: Reset view, Seat u/d, Zoom in/out, and I have View Pitch U/D+Yaw L/R on my numpad Even without assigning those to a HAT, it's still a breeze to take a Tomcat on manual final and land So even without Track IR, but with a few hats assigned to basic views, I see no reason to bind exotic camerapositions, except to fly 'EZ-mode' I expect a self-centering analog stick would work better though ...but then, I'm a guy who still tries to hook up in pouring rain without outside views, while the F-14's canopy rain dispersion system isn't implemented

Indeed, if it was just a matter of de/re-soldering a few chips (still not an easy diy job), I'd understand the point But having to use totally different PCB to get things to work is on a whole other level It's like turning a sedan in a pickup truck, you can't simply shove 33" wheels under your Honda Civic

My HP G2 surround camera doesn't have a resolution high enough to make screens (or buttons) readable

All buttons are perfectly usable in DCS setups, I use the PFP-7 in the A-10 and Apache, so there's nothing stopping you from using the functionality mind you I fly VR, so the screen does not have any added value (though I still would love to see things fully functional)