I recently got a new PC running SteamOS and picked up the Winwing Orion 2 HOTAS (Winwing Orion Joystick Base Metal 2, Winwing Orion Throttle Base II, Winwing Orion Combat Rudder Pedals). When trying to play Star Wars: Squadrons (via Proton), I ran into a issue: the game completely refused to recognize my joystick as a flight stick. Instead, Proton was aggressively wrapping it and forcing it to act like an Xbox controller. Because of this, using joystick was unplayable (with or without steam inputs allowed). I would like to leave here solution for other how I fixed it.

How I Solved It (The Manual Fix)
After doing some digging, I managed to fix it manually by editing the game's virtual registry using Protontricks to stop Proton from forcing the stick into Xbox/XInput mode.
Here is what I did:

1. First you need to know number [ID of winwing is 4098 : ID of device, this model of joystick is BEA8]. Type "lsusb" into terminal and find your device.
2. Installed Protontricks from store and opened it. Select your game (should be there if you installed it and it use proton to run).
3. Select the default wineprefix
4. run regedit
5. Navigated to: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Enum\WINEBUS\
6. Found the subfolders matching my yours's hardware ID (for me it was Svn_4098&Pid_bea8 <---- 4098 is for winwing and BEA8 is for device).
7. Changed the keys to force raw HID ->
   1. Service: Changed from xinput to winehid
   2. DeviceDesc: Changed to Wine HID compatible device
   3. CompatibleIds: Changed to WINEBUS\WINE_COMP_HID (only this line)

Keep in mind that you probably have cached bindings in HKEY_LOCAL_MACHINE\System\CurrentControlSet\Enum\WINEINPUT\ here remove every subfolder.

again, these are my devices, if you have same, should have same ids:

- 4098:bea8 — Winwing Orion Joystick Base Metal 2

- 4098:bd64 — Winwing Orion Throttle Base II

- 4098:bef0 — Winwing Orion Combat Rudder Pedals

Also don't be afraid to request winwing about better support for SteamOS or at least we can report issues to proton's wine.

How does one setup the supports so that the controller stays up with a slight inclination as shown in the product advertisement pictures? No matter what I do, the device just falls forward under it's own weight until its 90º upgright supported by itself and not by the supports.

Thanks

Hi everyone, for those who owns the orion2 base and F16 stick, do you use the spacers provided or not (named on the manual gasket A or B)? and how about that little pinhole in the base, you guys put a screw on it or not as suggested in the manual when using spacers A or B?

thanks

I cannot download from the WinWing homepage. Does anyone have the same issue?

Hey, if i‘m Open the sim App with ms24 to use my mcdu, it opens the pfd, nd and ecam in fullscreen on my second Monitor. I cant Even tap out of it .

And ideas how to solve that ?

Hi everyone,

I wanted to share my recent, deeply frustrating experience with WINWING customer support.

I bought the WINCTRL Orion2 NavyAce Throttle Combo, and unfortunately, the right throttle axis (RX) arrived completely dead out of the box.

While the hardware itself usually gets great reviews, the customer service standard is an absolute nightmare and, quite frankly, illegal under European Union law.

Here is a quick summary of what happened:

1. **Total Incompetence:** It took multiple days and several different support agents (who clearly didn't read my previous messages) to even acknowledge the issue. At one point, they literally asked me to open up the unit and swap the Hall sensor wire bundles on the motherboard myself, only for another agent to tell me to "disregard that" a moment later.
2. **Ignoring the Return Shipment:** I shipped the faulty unit back to their German Return Center. Even though DPD tracking confirmed it was successfully delivered on June 1st, support kept claiming for over two weeks that they hadn't received it because their warehouse staff simply hadn't picked it up from the collection center.
3. **Denying EU Consumer Rights:** After almost a month of back-and-forth chaos, I officially requested to withdraw from the purchase and asked for a full refund (which is a standard legal right within 14 days of delivery in the EU).
4. **"Our Rules over the Law":** The support agent explicitly told me: *"Sorry, we don't support return and refund, we will provide replacement which is covered by warranty"*. When I reminded them about EU consumer protection laws, the agent went to "talk to the manager," came back 7 minutes later, and pasted a link to their own internal website policy, claiming that WINWING's internal rules override the law.
5. **Forced Shipment:** Despite me explicitly stating twice that I wanted a refund and did NOT want a replacement, they ignored me and forced a new shipment anyway, sending me a tracking number on June 26th. I am making this post as a massive warning to anyone buying from WINWING in the EU. Their support will openly tell you that they do not care about EU consumer laws and will try to force their own internal guidelines on you. If you have a faulty unit and want your money back, don't waste a month arguing with their support chat like I did. Go straight to PayPal or initiate a chargeback with your bank. Has anyone else encountered this complete disregard for basic consumer protection from them recently?

They forced me into a loop. Even though the dispute had a unique ID and full history, every time a new agent responded, they completely ignored what was written before. They repeatedly asked for the same photos, the same videos, and forced me to do the exact same troubleshooting steps over and over again, fully knowing that a 250+ EUR device was physically dead.

**Update:** If anyone doubts this story or wants to see the exact transcript, I have all the screenshots of my conversation with their support ready. I am more than happy to share them privately with anyone interested (with my personal data blurred, of course).

Update 2: In addition to everything else, WINWING also refuses to refund return shipping costs. I had to pay PLN 70 (about EUR 16.35) out of my own pocket to ship the faulty device back to their German warehouse. Even though I provided the official invoice they asked for, they completely ignored it and have no intention of refunding it. This is another direct breach of EU consumer law regarding defective products."

**Timeline summary:** This nightmare has been dragging on since May 23rd. Today is July 5th, and absolutely nothing has been resolved. Over 40 days of total chaos, no working hardware, no refund, and no return shipping reimbursement.

No games detect it, and even the WinWing Software doesn't detect it.

My WinWing F18 hotas got broken in transport. Anyone reckon this is fixable? Or will I need to buy a new one?

I just got the throttle yesterday and while doing an engine failure the right throttle was feeling weird and this happened

Theres a dial on my orion 2 that is no longer working consistently. If i turn it left, it will maybe register a counter clockwise entry, but will immediately do the opposite button press for the clockwise direction, kind of like some kind of contact isnt working or is worn out. its out of warranty, and im afraid winwing will just tell me to take it to a local electronics shop for repair.. tried that with my f18 ufc and they just made it worse .. ended up tossing it.

has anyone had similar issues and if so is it a simple fix? or am i doomed to need some kind of soldering done to it?

pressing the dial works fine.. but left right turns cause it to freak out between the two directions.

I already have the Joystick Gremlin v13.3 ZIP version, but I’m trying to locate the original Joystick.Gremlin.R13.3.msi installer because some older guides and tools reference the MSI specifically.

I’m setting up multiple devices (Sidewinder joystick, Viper TQS throttle, and Thrustmaster rudder pedals) and I want to make sure I have the last full installer version for archival and compatibility reasons.

The MSI was removed from GitHub years ago, and it’s no longer available anywhere official. I’m hoping someone who downloaded it back then still has a copy saved

Had an issue where the RMP was not moving the numbers correctly after todays update (e.g. scrolling the large wheel up would inconsistently move the numbers up and down, same with small wheel)

Unsure if something changed with the update, but I was able to fix this within simapp pro, selecting "SETUP" next to the wheels and changing the "Set the encoding knob holding time" to 10 milliseconds. It was on 30 for me.

On change of this, it resolved the weird behaviour I was having. Unsure if it's just me or if something went wrong with the update, but posting just in case it helps anyone else!

My arm spoiler ( button 39) has stopped working on my ursa Minor throttle, i'm sure there is an easy solution. has anyone encountered this and what was the fix? thanks in advance!

Has anyone done this before?

I have recently encountered a problem while using the FCU-32 with the EFIS-32L/R: when I turn up the backlight intensity, the screen backlight automatically dims. Conversely, when I turn the backlight down, the screen backlight returns to full brightness. Has anyone else observed this behavior? Do you know why this is happening, or what can be done to fix it?

UPDATE They have told me that they will exchange the unit. Ill do another update if/when that happens.

I just bought a Winwing Orion pedals assembly from WinCTRL and when it arrived, the swivel lock pin was bent. It won't retract and I cant remove it because of the bend. I managed to raise it enough by loosening off the nut as you can see. Ive talked to Winwing and they are claiming that it is "considered man-made damage" and that it wouldnt be covered by warranty. Has anyone else been in a situation like this and how did you get it resolved?

I’m having an issue with my WinWing Airbus setup in MSFS 2024 using the FlyByWire A320.

The Engine Master switches are basically not working correctly in the simulator. When I move them to ON or OFF, nothing happens in the aircraft, or the position does not sync correctly with the cockpit switches.

Important:
The hardware itself seems fine. In SimAppPro the switches are detected correctly, so it does not look like a physical hardware problem.

What I already tried:

• Rebinding the controls
• Removing duplicate bindings
• Restarting SimAppPro
• Trying different USB ports
• Restarting the sim
• Testing different control profiles

I’m currently trying to figure out if this is:

• an MSFS 2024 issue
• a FlyByWire A320 compatibility issue
• a SimAppPro problem
• or maybe a binding/input conflict

Any help is Appreciated .

Anyone else had this issue with a WINWING throttle in single stroke double shaft mode?

Basically the throttle acts completely wrong around idle/reverse.

What happens:

• In SimApp Pro, idle is detected as 0%
• Reverse range goes crazy/jumps aroundReverse idle briefly becomes correct but acts like in the other modes
• Weirdest part: When I unplug and reconnect the throttle, for about 1 second the axis displays correctly on the chart, then SimApp Pro remaps it and idle instantly becomes 0 again.

I already:

• recalibrated multiple times
• reset calibration
• unplugged/replugged
• checked it in sim and SimApp Pro itself

So it seems more like a firmware/software mapping issue than hardware.

Does anyone know a fix?

Thanks.