Instale o Steam
iniciar sessão
|
idioma
简体中文 (Chinês simplificado)
繁體中文 (Chinês tradicional)
日本語 (Japonês)
한국어 (Coreano)
ไทย (Tailandês)
Български (Búlgaro)
Čeština (Tcheco)
Dansk (Dinamarquês)
Deutsch (Alemão)
English (Inglês)
Español-España (Espanhol — Espanha)
Español-Latinoamérica (Espanhol — América Latina)
Ελληνικά (Grego)
Français (Francês)
Italiano (Italiano)
Bahasa Indonesia (Indonésio)
Magyar (Húngaro)
Nederlands (Holandês)
Norsk (Norueguês)
Polski (Polonês)
Português (Portugal)
Română (Romeno)
Русский (Russo)
Suomi (Finlandês)
Svenska (Sueco)
Türkçe (Turco)
Tiếng Việt (Vietnamita)
Українська (Ucraniano)
Relatar um problema com a tradução
Sounds like some bindings are off.
nah man like i stated in the OP, the issue happens whether the knob is turned to BOTH or START, doesn't make a difference.
Which aircraft are you flying?
There's a problem with MSFS that it can only take so many Lua commands at once from a controller, something like 32. Unfortunately, the gorgeous Honeycomb uses steady-state switches (if it's on, it's always on), while MSFS uses momentary commands (press-to-toggle, like a keyboard key). So while there are fewer than 32 switches on the Honeycomb, there are more than 32 states, 36 I believe.
So... you have to get rid of a few bindings to get the number back down to 32. All of the non-handle switches are steady-state, as is the ignition key. If you delete all of the ignition key bindings, the Honeycomb should work.
Try that and see if it helps (make a backup of your profile). If that's the problem, you can get around it using Vjoy to fool MSFS into thinking that your steady-state switches are all momentary. I have a tutorial for that, but I don't want to hunt for it if this turns out not to be the problem. It's a solution that will remove an hour or two out of your life, but it works.