Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Discussions Rules and Guidelines
7 
Report this post
A good explanation, he shows the assignment of things not pre-programmed in the section on his rudder pedals.
https://www.youtube.com/watch?v=1DXdGaRgnhU&t=11s
In that video, the game doesn't recognize the pedals though. Game doesn't recognize Virpil sadly.
So, when I went into the controller settings, it said my Virpils were highlighted but did not show a picture. That part is so far correct. However, I can't even program any buttons as then I get an error message saying button config does not exist. Aka, it doesn't actually recognize my switches on the throttle despite saying it recognizes that it's a Virpil HOTAS. Can't even bind anything on the joystick. Sadly, it seems that Virpil users can't even play the game until Microsoft offers support of some kind with that HOTAS as it seems they only go for certain HOTAS over others. Similar to that one Ace Combat game that only did certain HOTAS and not all.
Agree with the auto assign. However, when the game recognizes that you are using a Virpil HOTAS but then says the button does not exist, that becomes a problem. Without getting too much into it, the Virpil Throttle has switches on there in which this game does not recognize leaving half the controller unusable. And sadly those switches work great for having a 4 engine play or creating a startup sequence to turn on the plane. But the game doesn't recognize those switches which is all I'm asking is to recognize those switches and the Stick itself. Otherwise the only way for me to play is M/K and I most certainly can't fly M/K no matter the game.
When binding, with your HOTAS selected, if you select the rectangle for the function you'd like to bind, and then select "Search for Input" and press the key on the HOTAS that you'd like to bind, does that not work?
Rereading what you've said, does the game recognize some of the switches, but not others?
If so, I would expect Device Manager to react the same, just some of the buttons. I'd think that if that was the case it would be the Virpil not sending recognizable signals from those buttons, and maybe the Virpil software controls that?
Have you posted on the Virpil forums to see if anyone else has a clue? It just seems odd that something as straight forward as binding keys from a usb device to a game that's looking for keys from a usb device should be difficult.
So, I've seen on posts that players, using Virpil, are having issues playing this game with that HOTAS. As such, the game recognizes Virpil, but half of the switches on there are not recognized. The axis are also not being recognized and it gives an error stating that the button or axis is not recognized. I've tried this with other switches with some success. The major problem is that axis aren't being recognized and half the switches and buttons aren't being recognized either making it unplayable. I have not posted on Virpil forums, mostly due to the fact that it's not exactly the best place to get advice on fixing issues. I'll have to check with those forums later. However, I prefer sticking to one forum, i.e. this forum for guides or if devs are kind enough to say what system they are working on next. I see many are having issues in the peripherals section that a dev have posted. I do own the x-55 as well, however, that doesn't seem to be supported either.
Weird seeing as how the x-56 is a slightly better version of that one, but apparently x-55 is not being supported currently by even saitek.
All do show up in Windows Device Manager?
I have noticed that the game just refuses to bind certain buttons and switches on my throttle (I have an original MT50). I'm suspecting the game actually has an upper limit on the logical button assignments, but that's a guess, I haven't tested it.
I did end up having to create a custom profile in the Virpil Software Suite for the throttle in order to bind some of the switches. By default they're set so they ALWAYS transmit as if they're pushed when they're in one position or the other. This is great for games that support three-way switch abstractions (DCS) or can deal with a toggle being held (literally everything else). However MSFS apparently doesn't like this. I had to re-program them so they act as momentary switches when toggled.
I had no issues binding the momentary ON-CENTER-ON switches. The momentary push buttons seem to not be recognized every now and then and I have to restart the program to get them to work.
The encoders seems to work fine, as do all the axis.
I'll need to do some more testing to see what physical button is assigned to what logical button and see if there's an upper limit to what MSFS will detect. DCS will support 128 buttons but IIRC Windows itself can actually only see 32, so if MSFS is using the built-in windows stuff it may ignore certain logical buttons.
Windows Device Manager won't really be useful, OP will need to use the Virpil Software Suite. Windows will only see 32 logical buttons.. the Virpil throttle (depending on model) can have over 80.
Do you have a video of this somewhere? Also, the game doesn't recognize the throttle's axis as a thing but does recognize the sticks axis. Well, recognize isn't the correct word, but there is a setting for the Joystick X, Y, Z axis but nothing for the throttle axis which I believe should be Slider.
Nevermind. Look in the periphials trouble shoot forum post. that apparently fixes everything and you wont have to do what you did anymore.
Direct X devices support up to 128 buttons? I have my warbrd base with f18 grip and hog throttle bound to one device using T.A.R.G.E.T (I changed the usbid of the virpil to match the hog flight stick usbid) and it supports 128 buttons in both windows AND in MSFS2020?
Some games, for some reason, still use older DI components that only support 32 buttons (I'm looking at you, Elite: Dangerous). If you open the USB game controller thingy in the Windows Control Panel, you'll only see a max of 32 buttons.
As for the button issue I was having in MSFS with it not detecting my buttons, that was my own fault -I unintentionally changed mode on the throttle to a mode those buttons aren't mapped to. Though I still couldn't get it to bind the constant state switches.