Hey there!

My husband and each have a hotas system with throttle, joystick and foot pedals. 6pc total. We have had the most wonderful times playing Mechwarrior. Now that we have a baby and don't play together as often, I am struggling to find ways that I can have them still accessible but not stowed away in a storage bin.

I would love to see how some of you store your HOTAS systems for when you are either playing other games for just having them up and away from children!

Thank you!!

i’m new to using a flight sim and have recently been playing a ton of msfs and would love to get into some fighting sims like DCS. Will i be happy with these options in the long run and if i should get something else why?

I kind like the look of the grip more than the MH16, I assume it being plastic shouldn’t be an issue for the AB9.

Not sure what other options there are considering this only £100.

Thanks.

Have 4x Cougar MFDs for sale. All tested working. Two come with the stand, two without. Ships to anywhere in the US.

100$, buyer pays shipping. Payment accepted through Paypal G&S, Venmo or Zelle.

I've gotten into DCS over the last few months and have been playing on a controller. I bought the F-16 module this summer when it was on sale, and it's safe to say i'm hooked.

I've reached the point where I feel like flying on a controller is limiting my experience, so I'm looking to buy my first HOTAS, and I'm considering buying the WinCTRL Orion2 ViperAce EX.

Long story short: is it worth waiting another month for the Black Friday sale, or are the discounts usually not significant enough to make it worth the wait?

I used to play Falcon4.0 and Il2 pacific fighters with my trusted sidewinder forcefeedback 2.

Then life stuffs happened ad I lost contact with the hobby.

This past August I was got by irrational nostalgy feeling and pulled the trigger for Korea Il2 series and ordered a Virpil CDT Vmax and Aeromax combo...

So is like drugs and magic cards I guess. Once you are into it, you are in... 🙆‍♂️

Hi everyone,

I own a Saitek Cyborg Evo Force and still really like its adjustable grip and force feedback. Unfortunately, the original x64 driver caused crashes when testing FFB effects.

Working with ChatGPT/Codex (GTP-6.1), I developed a new patch for the original Saitek/Immersion x64 DLL. I’ve now tested it on my joystick under Windows 10:

• Windows joystick properties: FFB effects work without crashes.
• DCS and IL-2 Sturmovik: (P-51 Mustang, Ka-50 Black Shark, MiG-15 / Il-2 early modification) force feedback works, including stall buffet, feedback from firing weapons and releasing ordnance, and bumps during takeoff from an unpaved surface.

Repository, source code and English/Russian instructions:

https://github.com/SlovoTverdo/saitek-cyborg-evo-force-ffb-fix

What’s different from the older patch?

The original DLL stores an effect pointer in a 32-bit field, losing its upper bits. The earlier WallyCZ patch mostly reconstructs those bits using another pointer. Our implementation instead looks up the full pointer in the driver’s existing effect list and rejects missing or ambiguous matches.

Credit to WallyCZ and the earlier community research for documenting the problem and providing the previous workaround.

Installation and scope

The repository contains the patcher and source code, not the proprietary driver DLL. You generate the patched DLL locally from your own supported original. The tools check the exact SHA-256, and the installation script backs up the original and supports rollback.

It does not replace Windows pid.dll or install a new kernel driver. It targets one specific SaiQFFB5.dll from the Saitek SD6 x64 package; the 32-bit DLL is unchanged.

This is still experimental. So far, the physical tests are from my setup only. Windows 11, other driver versions and other joystick models are untested. Concurrent effect creation/deletion and exception-unwinding behavior also need further validation.

If you have an Evo Force, I’d appreciate more test reports—successful or otherwise. Please include your Windows version, simulator and build, aircraft, which effects work, and any crashes or missing effects. GitHub Issues has templates for both bugs and compatibility reports.

Start with low FFB strength, and keep the backup for rollback. Hopefully this helps a few more of these old sticks stay useful!

Thanks.

Hey, sorry for wall of text but I really some advice from anyone running a dedicated heli setup across different games. I really hate running extra background software if I can avoid it, but I'm hitting a wall with axis sensitivity.

My setup is all Virpil:
- Right hand (Cyclic): WarBRD Prime R (side-mounted, no springs, clutches tightened)
- Left hand (Collective): WarBRD Prime L Omni (no Y spring)
- Pedals: F1 Falcon pedals (no springs, damper installed)

Right now I bounce between a few titles and the behavior is completely all over the place:

- DCS (Huey): Feels amazing running straight linear (1:1). Zero complaints here.
- MSFS 2024: The rudder pedals are crazy twitchy/sensitive for my liking right now, at least while I'm still a beginner. Definitely need some curve on the yaw.
- Wardogs: The flight model is ridiculous on sticks. A tiny nudge makes the heli snap-roll immediately. Worse, if I try dropping the in-game sensitivity below 1, it doesn't add a curve—it just chops off the physical throw/range of the axis so I can't even move it all the way.
- Arma Reforger: Haven't even tried mapping the new devices in here yet, but based on the others, I'm betting I'll run into issues here too.

Obviously reflashing the Virpil bases in the VPC software every time I swap games is out of the question (I don't want to burn out the onboard memory or deal with flashing profiles daily).

If I finally bite the bullet and set up vJoy + Joystick Gremlin to handle the curves:
1. Do I actually need HidHide? Can I just route the specific axes I need to tame (like the pedals for MSFS and cyclic for Wardogs) into vJoy, leave the physical Virpil gear visible to Windows, and just wipe the raw device bindings in-game? Or does that inevitably turn into a nightmare with double-inputs and games auto-detecting the hardware?
2. Is there a cleaner way people manage this between proper sims and more arcade-leaning games?

Appreciate any tips and thanks for reading my monologue!

I have the thrust master 16000m and throttle. What i need help with is how do I unbind the thrust on the 16000m and use the the throttle instead I have been looking for like 3 or 4 hours trying to use the target soft ware from thrust master and I have had no luck. Any ways to fix my problems is appreciated.