This is an example of the xjoymap.ini file you have to place under the 737 root folder to map the captain's EHSI range and EHSI mode to buttons or keys.Ġ,1,2,3,4,5 are the values the 'range' dataref will cycle under each mapped button clic. The documentation is included on the plugin and several examples over the forums. Xjoymap.ini file has a syntax structure for making the assignments you must comply. Just for the ones you require special assignments. No need to have a file for each aircraft in your hangar. You create a 'xjoymap.ini' text file on a per aircraft basis and the file has to reside on each aircraft root folder.Įverytime you select an aircraft in xplane, xjoymap will check on the aircraft root folder you are selecting if an 'xjoymap.ini' file exists and load it for aircraft assignment parametrization or will do nothing if the file is not found. Every aircraft developer provides their own datarefs for their simulation. Xjoymap plugin allows you to create assignments on a per aircraft basis. ![]() If you are a cockpit builder you may have a multi-position knob and no need to cycle, each position stores the proper value on the dataref for direct access to required range. You need xjoymap, a lua script, or simular, to map your hardware button to the dataref and each clic you cycle the value stored on the dataref for different ranges. This is a good example of a dataref 'ixeg/733/ehsi/ehsi_range_cpt_act' depending the value you set on the memory position, the range you get in the EHSI. So a custom command clic will not do it because the simulation doesn't know what size you want to set. You ve got it Selecting EHSI map range has multiple options. As we know if you have a pit switchology takes weeks to finish on each plane.Īmazing IXEG and dropping my other sim due to this plane! In the short time I have spent reading about using the GIT tool I get what you are saying about 0, 1, 2.Ĭoming over from microsoft FS and use to using those tools for programing keys (LINDA -not as flexible but simple interface). With 7 GF panels and MCP coming next week. So a dataref I suppose.Īre you saying I need something like XJoymap for that to work? (man I know I am annoying newbie here)Īfter that I am working on my GoFlight gear with Poly's tool - that will be my next hurdle. It has been a bit of a learning curve so your explanation has helped.ġst - Basically I have button on my TM MFD (recognized as a device under Joysticks and the buttons programmable in the XP11 interface) Right now I was working on XP-11 (might go back to 10. I was confusing those custom commands and datarefs. Great explanation! I am on my way to better understanding now. Thank you!! I just bought the 737 a couple of days ago. I tried to be as simple as possible on the explanation. I am giving you just generic examples to understand what a dataref is for So when you build a cockpit, depending on your hardware switch position you store a 0, 1 or 2 on the dataref. storing a 0 value means light is off, 1 value means low intensity, 2 means high intensity. You need to store there values 100ft 1000ft 15000ft whatever you need to store that will be the target for the nav systems. You can not map datarefs under joystick and assignment, you need a plugin/programing to manipulate the aircraft datarefs. Based on the value the simulation does/show something. 'a/p disc' when you map this custom command to a button or key, when you clic it will disconnect the autopilotĭatarefs. These are memory positions the simulation store values. You use custom commands via mapping as explained above. ![]() So when you invoke them via button or key press, they perform an action pre-programmed. These are actions the developers provide for the users to map to key/buttons directly. They are not, both lists are documented under the "2-interface guide.pdf.Ĭustom commands. It is quite common people confuses Custom Commands vs Custom Datarefs or think they are the same. You need to map / un map blind at first, and then items will populate on the list. Xp11 works the same but the UI is different and there is still parsing issues for the information to be shown properly. Navigate to ixeg stuff and select whatever you are looking for there. on the right side, you clic on the top right corner "custom cmd field" and a tree will popup. you press the button you want to map (or you select the key you want to assign)Ĥ. Depending you want to map a key or a buttonģ.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |