I’ve been trying to make the Boeing 747, 748 and Airbus 320 use peripherals completely during the cruise phase, instead of switching between mouse and keyboard.
My equipment includes the throttle valve of VPC t50m3 and VKB MCG rocker. The number of keys of these two devices is enough for me to set all the keys of the autopilot panel. However, because the names and descriptions of most operation settings adopt abbreviations and professional terms, I am an ordinary player and can’t know its real function through screenshot translation.
For example: horizontal navigation, vertical navigation, altitude level change, and the confirmation buttons of the four knobs of speed, heading, altitude and vs. I’ve been trying to find these mappings in the key settings, but due to language restrictions, I’m not sure whether they don’t exist or I haven’t found them.
If you know which column these buttons I need are in, please help me, thank you
I also tried to search for relevant videos on youtube, but I didn’t find the videos related to the key settings of large passenger aircraft. If you know, you can also tell me the link. thank you.
This is actually unneccesarily hard at the moment, because Asobo in all its wisdom decided to hide input variables from external access without providing mappings of their own. This makes accessing all controls a really convoluted process if not impossible. This is more than annoying for home cockpit builders or mouse aversionists
Vote here to make a change:
It is patently ridiculous that all buttons and controls in any plane are not mappable to a button or switch on your controller or button box like a Stream Deck. Doing something basic like adjusting the range on the map on the MFD is not possible but if you want to toggle Magneto No4 on and off that’s no problem for the precisely zero planes that have 4 magnetos that are independently switchable. UX and usability in the is game is a garbage fire of inconsistency and there is no indication that it’s going to get any better.
OK, I like to participate in this kind of voting closely related to me. However, the change that Moby flight hopes to make is an appeal made as a third-party developer, or can it benefit all players. After all, I just set up two peripherals instead of going to a cockpit of DIY to realize the control effect through virtual buttons.
I tried to make a DIY device. When it was finished, I found that it didn’t work like Xp11, and it occupied most of my desktop. You can see that I like cleanliness very much, and a line is an obstacle in my eyes. So I gave up.
I hope I can find the general buttons I need in the game settings. If Moby’s voting can also benefit me and achieve my wish. I will very much agree with this appeal.
It would help anyone. Whether you have “just” a Joystick or a full homepit. Tools like the excellent Lorby’s Axis and Ohs or other external software could be so much more useful and the setup process would be way easier ( for example binding a three way switch when you have off, low, high could be done in a jiffy). The complexity of your input device does not matter in that regard.
Of course Asobo themselves could get around. But there is stuff like the inertial sperator for example, that you’d use in a turboprop at least twice in each flight that has been removed (there used to be a binding). My hopes regarding Asobo are quite low in that regard. They have their priorities elsewhere, not with the hardware mapping crowd it seems. They introduced the B Variables overnight with SU 5, which has been a while ago and left a couple of people stranded with their hardware. Seemingly it was not on their radar that there are quite some people that rather than a mouse or a controller like dedicated switches.
I think Sebastians endeavour is the more promising one, as you can bind whatever gets produced by third parties without having the need to update the sim binding dialog.
Asobo could of course provide an API to said dialog. But I do not see that happen either any time soon.
