![]() ![]() And bloody right you are, but that right also applies to simuations!ī. ![]() And the reply is always "But it's so much more comfortable!". I can even turn the argument around and say that driving an automatic transmission and using cruise control, automatic spacing, lane assistants and all the other gadgets doesn't count as real driving. That's why shortcuts like auto QNH or even the "pause" key are essential to get the amount of tasks to manage down to manageable levels. There's just no way that you can do everything at once when things get busy. On a normal sim setup, you need one hand for the stick, one for the keyboard and one for the mouse and you're all on your own. A lot of things have to be done by clicking on them with the mouse or using the keyboard, while in home cockpits, professional simulators and in the real cockpit, you can simply grab them without taking your eyes off the flight path and there's always one hand on the yoke. Mind the limited possibilities for interaction in simulated cockpits. If you just want to watch the scenery, set the weather to standard ISA and you don´t have to worry about that at all. If you simply want to fly some procedures, the B key (or a plugin) would be appropriate. I have looked diligently through the list of P11 keyboard commands and while I found the one for setting the DG. So if you want to know what its like to really operate a plane - you need to get the altimeter setting the way real pilots would. In FSX and P3D, pressing the 'B' key on the keyboard would always set the altimeter to the field elevation or, when in flight, the the nearest airport or ATC setting. You STILL have to remember to set the subscale, but you don´t have to go through the steps to obtain it (even though its as simple as having the dataref displayed on-screen in X-Plane, no need to even open the map). The chore of getting the altimeter setting is pretty boring and repetitive, so its a good candidate to replace it with a single keystroke in an entertainment simulator. If you mess this step up, separation to other aircraft or the terrain (ESPECIALLY on a non-precision approach) may be compromised, possibly resulting in a mid-air or CFIT accident. There is an option for FSX default keys but that is not really working. In addition, the aircraft has no way of knowing the correct altimeter setting (QNH), so it is totally manual work to obtain that (either listening to ATIS, getting an ACARS Direct-ATIS or asking the controller). I dont have a controller so I tried to map the keys as the ones I used to in FSX, but failed. Then Save file and reload the sim and that plane then use the translate keys to the location you like and then re-assign the camera again. Modern planes will "flash" the subscale if you are below the (databased) transition altitude, but the transition level can change with pressure, so its still very much up to the pilot to set the subscale. ![]() In real aircraft - even the most modern airliner types - it is a crucial and life-or-death step to have the correct altimeter setting dialed in. The case of the "B" key is a good example. After all, it´s THEIR way of having fun, and if they incline to do so, they should be able to. They like to sit in the cockpit, watch the scenery go by and pretend that they are a pilot flying across the countryside. I have found out that many people play simulators not to learn about flying or even "training" for it. It is nice to have a common set of MSFS/XP key mappings.There is often a debate about how realistic a simulator pilot should be forced to play - I used to be in the camp of people asking for pretty realistic conditions, but have recently moved a bit to the middle. Unfortunately it appears that the keybinds are stored in the “cloud” and not locally, so I do not know how to get a MSFS key mapping file that can be shared. As a result, there are some MSFS features that are disabled but I only care about the primary piloting functions that are convenient to have on the keyboard. The XP keys that I am very familiar with are the quick look keys (numpad 0 thru 9) and the quick look mem (ctrl numpad 0 -9), flight control keys 0-9, and engine control F1 - F12. So I started with the default MSFS keybinds and created a custom “XP” compatible keybind. I am not sure if this behavior has changed with the latest updates. A problem with the MSFS keybinds is that it seems to execute the primary keybinds of 0 - 9 regardless if they are already defined as part of other key combinations (ie. A couple exceptions are that I have a “Pause” key and I prefer that to “p” (XP) and I also prefer “End” to “shift 8” (XP). I have made the MSFS keybinds as close to XP as possible.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |