Nightdare

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)

Of course how one would need to bolter a 10,000' land based runway and go around again in a plane designed to land on a post stamp, requires a whole laundry list of "Specific moments where crap went wrong"

AI is a baby that still needs to be spoonfed, I shudder at the perceived expectation it will grow into a well adjusted adult as it is being raised by irresponsible parents

I don't think SAS is gonna do much when you're shortening your runway Unless you're one of those Airforce ballerina's trying to impress the CO with a pretty flare You're Navy, you don't land, you arrive!

If the joystick supports it: Might as well bind the stick lever button to Autopilot Disengage and the stick lever axis to Both Brakes It gives no issues airborne and no issues on the ground

Sounds like the Encoder acceleration option is set on full blast in SimApp

Dunno about the F-15 grip, but there is only a single 'paddle' on the base, an mine is as smooth as all the others

I cannot give you profiles, but I can give you a Site that helped me a lot with setting up my controls and understanding certain functions https://chucksguides.com/#dcs

RIP Ozzy

3 out of 8 motors on my OG HFS8 already failed and this is with about 30 minutes total use since I bought it 2 years ago

Might want to ask the guys at https://qr4rigs.com/ if they have something that compares or if can make you one

Might wanna check the axes keybinds in game

I have a twist version since release, with the idea I could also us it with Elite Dangerous, locked it the first time I mounted it, never unlocked it since

Not to mention the 'stations' communicating with each other are taking up extra processing power for the data transfers between one another

What I saw in my windows was P6 activating from zero position on the physical dial, then stopping when it's end value was passed and P7 starting to activate halfway open once it's start value was passed I'll see if I can give it another whirl later today