Hi all.
I was flagging an input bug to Zendesk and I got a very strange reply which was basically…
“Your Virpil device is not supported…”
My Virpil rudder pedals, joystick and throttles all work, I really don’t think that the bug I was reporting has anything to do with the controller that I use (I replicated it with a TM T16000) but this struck me as a pretty odd response from a technical support channel that is supposed to have a direct relationship with the Dev team.
I have also noted over the course of several updates that the release/bugfix notes frequently seem to include “fixed issue with - insert specific thrustmaster or honeycomb product here - / function input”
So I’m starting to wonder what input control API Asobo are using. Are they writing input code specifically for certain products rather than using a standardized API?
At least not entirely. I have a DIY input for my pedals, created with an Arduino Micro, and it works just fine in MSFS. I use the Joystick library to communicate with the computer.
I think when they write things like “fixed input problems with XYZ” it just means the default mappings or handling specific quirks of that input device (like the AP panel on the honeycomb bravo), by adding new binding options. It still all uses the same generic DirectX API.
Support is well… support. Most commonly underpaid people in a 3rd world country using scripted responses. Honestly I have not once in my life requested support for a consumer product. It never works. Business products are different.
You should also understand the term “not supported” literally. It doesn’t mean it does not work. Just that they don’t provide support for that specific hardware. Which is absurd, considering it’s a generic issue, but that’s what it means.
It would indeed also be incorrect…if they are using standard API’s…