Leaderboard

Hi Jan, Navigraph would be pleased to offer such data (Transition Alt and Transition Level ) if IXEG would like to make use of it. Cheers Ian (Navigraph Development Team Member)

Just wondering by any means the IXEG crew will add a HUD to the 737 Classic. Not sure if many people know but Southwest Airlines has a hud installed on their 737-300 aircraft and it would definitely be very cool to add that and use it in IMC. Please take this as an idea not a request

O'Hare Int. AirportAfter hours of work.... the terminal 3 G Gates, is not finished yet, but we are close...... Hope you like it.... FB Page. @icarus.simulations

where do you get this? copy/paste from boeing: Landing Gear warning Config - Visual Indications (737-300) The landing gear indication lights are activated by signals from each gear, the LANDING GEAR lever, and the forward thrust lever position as follows: Green light illuminated – landing gear is down and locked. Red light illuminated – • landing gear position is in disagreement with LANDING GEAR control lever position (in transit or unsafe) • landing gear is unlocked • landing gear is not down and locked, and either or both forward thrust levers are retarded to the idle range. All lights extinguished – landing gear is up and locked with the LANDING GEAR control lever UP or OFF.

Done! BASE OVERLAYS.psd

Updated May 15th Hi all, I've attached the configuration file that includes all the custom datarefs that I use with my TM Warthog and some standard commands. I use XJoyMap for all custom commands. See chart below for how I mapped them in X-plane. You can map these as you please, but I find this layout to be quite efficient. Furthermore some switches are based on the how the physical switches on the TM Throttle operate, but as the config file contain a lot of different button-layouts, feel free to experiment. Any ideas on how to improve would be greatly appreciated Some controls have been taken away from the chart and config file as they're not needed on a 733 (such as prop sync, micture axis etc). Controls with "(O)" behind them,are using original X-plane commands and can be found under regular advanced buttons. I'll add these later when I figure out how to back up the bindings from X-plane itself. The TM Joystick use datarefs already configures by IXEG (such as flaps), and some other commands (X-camera, trim etc) so I excluded these for now. xjoymap.ini contains all customs controls Comments.txt contains all custom datarefs from IXEG and the documentation from XJoyMap devs. I highly recommend using Notepad++ for editing the files! Challenges/Problems: Mapping Keyboard commands does not work. It will work until you restart X-plane. Then it renames the command and it stops working. I've not been able to combine commands yet. Tried every logical combination there is. Any suggestions you might have, please share! Warthog Chart: Hello! My first post and my first encounter with the X-plane community. This is going to be fun! I've installed X-plane a couple of weeks ago in order to get ready for the 733. In the beginning, it was quite hard to figure out the different concepts used in X-plane as they often differ from the way things are done in Prepar3d. Two weeks have passed, tons of pages read, a vast number of forums visited and I'm really starting to understand why things are done in a certain manner and the value it brings to our simulation. Using the 733 has been a joy from the start. Yes, there are some minor bugs and glitches but all fade away when I turn off the Autopilot and manually fly this wonderful simulation. Nothing surpasses the feeling of having all your confidence stripped away when trying to land in Norway during a winter storm. Never ever have I experienced anything like this in a simulator before! Outstanding work Gentlemen! So over to my first of probably many questions to come: In the Interface guide PDF, there are several custom controls that are listed. Mapping these was surprisingly simple, and I can now use my Thrustmaster Hotas for the most common controls needed. There are however more controls listed underneath in the same document for "more advanced users" that I would certainly like to map as well. How do I configure X-plane to use these controls? Are there any information or general documentation on the subject? I have read some SDK-info and are starting to figure out how the logic behind the mapping is done, but I'm struggling to find out how one configures controllers to the custom controls within the simulator itself. Any advice or "pointing me in the right direction" would be greatly appreciated. Sincerely Torbjørn Comments.txt xjoymap.ini

It is time to get the X-PlaneCON annual convention going. There is a new facebook page to discuss this but also would love to discuss here on this thread. We need opinions, comments and even volunteers to make this annual show work. XplaneCON is going to happen. If you are interested in attending this annual event your opinions and comments are welcome on the new XplaneCON facebook page here https://www.facebook.com/groups/xplanecon/ There is a poll on the facebook page about possible dates. The location has been decided, it will be held in Las Vegas, Nevada. Chime in here or there if you think you would attend the event. Chime in here with suggestions on what you would like to see at the event. Thanks for any comments, suggestions and interest.

As that link require the logon is there a standard, normal, beautiful web page for those that don't use facebook?

@paulferg thanks for sharing the info! first thing i noticed on your screen capture is your next active waypoint is an (INTC) order. I have seen this problem before the aircraft not joining the magenta when this order is in place. maybe you are experiencing the same issue/bug here? the developers already know about the other case. We need to wait a bit for them to investigate. Can you please edit your legs page and remove the INTC and set next waypoint PALCO to confirm this fixes your issue? Anyway i will reproduce your flight a bit later when at home to confirm we are having the same behaviour.

Short vids on Beta4 of 10.50 Ksea Area, and KORD iirc lol Will keep adding a few with different areas to show the neat new Auto-Gen Rig specs ..... Win10 Pro x64 5820k at 4.7 Watercooled Palit Gtx 1080 FE at around 2.0 core - 5643 mem (that's what msi says, eg : +650 over my stock) Asus Rampage V Extreme 4x8Gb DDR 4 3200 at 3200 128Gb SSD OS Drive Sim runs off old HDD 7200 spinner ! hence glitches until larger SSD (also weather changes darn fast for some reason !) Just had my large 2TB HDD die so hey ho, SSD later today i hope X-Plane settings i will display in-game, sim is Stock, no HD mesh etc, i also have fps capped at 30fps for smoothness, still new to nvidia settings lol

Hiya mmerelles, Well, 600 sterling for what will relatively soon become a mid-range gpu is at the very top of my buying limit, i really thought wth have i done last friday, but welp, i love it i mean if the Ti and maybe the Titan (if they will do a titan) were out per say, well i would of gone for a Ti up to a max of 800 But, coming from a damned good overclocking r9 290x this fe 1080 is still amazing me If i am right in my thinking, when the Ti version comes out, i think it might be the first gpu when coupled with a good cpu to max x-plane out, after a minor glitch having to buy another hdd, i'm saving for a G-Sync monitor next, then no matter what unless reviews are bad i'm getting a 1080 ti when funds allow, once you've seen the new eye-candy in the flesh i swear you'd sell a kidney to have it all maxed at high fps (well i might consider it hehe) No idea where in the world you are or what gpu you have now, but i have another R9 290x, think it's an asus, stock fan setup, used maybe at max for 2wks in x-fire, if you pay the postage you can have her, my watercooled 290x is for a mate down on his luck or you could of had that Offers there if an r9 290x would be of benefit to you I see all your posts helping others, you're usually the first to help which is nice Will go n check name etc, no idea if any warranty left on it, so i'll edit back Cheers Tony Edit : Asus Dirct CU II https://www.asus.com/uk/Graphics-Cards/R9290XDC2OC4GD5/

very nice videos! i am looking for selling one of my full rig imacs and getting a powerfull pc based on gtx 1080, it is shame i can not crank anything up on my imac for autogen, clouds, etc. and they cost twice

I wouldn't call zero plugins you are running silverlining for skymaxxpro and real weather connector, anyway i wouldn't think that is the problem at all. Lot of people use them, i use them myself with no issue. by looking at your log file, i see you are running AI aircraft 2 of them besides you. This has been a problem in the past specially when AI tries to load the 737 twice. Just for the purpose of testing i would recommend you go to Aircraft -> Aircraft & Situations -> Other Aircraft tab and set it to 1 (just you). Check if problem is solved. Also double check on joystick & assignments your shift xxx assignments are still in place, sometimes the pref file get messed during betas forth & back. Does them work properly to other aircraft normal and replay flight?

Thank you sir and it is greatly appreciated. As I was flying the mission, I was looking out of that vantage point as the clouds were going by at 11,000 feet. And it did give you some sense of realism. I can't wait when Laminar introduces the upgraded graphic affects that they talked about at the SimCom 2016. I would suspect that that shot would even look better when they institute those graphical upgrades that they propose. Also looking forward to the sound upgrades and hopefully the aircraft developers for X-Plane will revisit all of their aircraft such as the PC 12 shown, with graphical upgrades and sound upgrades. And to be honest with you, to some degree, I would not have a problem to pay them for their time in the upgrades to the aircraft that we fly and enjoy to use. But regrettably (sorry for the downer) I do not have confidence that the existing developers for existing aircraft would do as I proposed. Even if customers such as myself are willing to give them more money. They just don't want to do it, and I think they do not have the mindset it would be good for the community and it would be good for their product. They just don't think that way I guess, based on aircraft developer track records in the past. They seem to lag and just do fixes to keep their airplanes current in the context of allowing them to work in X-Plane or whatever platform the user uses. Actions speak louder than words and their actions have demonstrated what I just spoke. It sad, but that's just the way it goes. On an up note more pictures to come in trying to get those magic moments when we take our photographs of. Take care and talk to you soon, Dion

Just out and about between KBFL Bakersfield Ca. and KTPS Tehachapi Ca. Quick flight before I had to go to Work in the Real World Dion

Idea is noted. For the future: Ideas and suggestions will be ranked much higher on my internal list if posted in the correct forum subsection . Jan

Thanks for the reports and the investigative efforts! We will look at this one! Jan

i tried ro recreate your flight and had the same weird behavior. The aircraft does not try to join and follow the magenta to the right when engaging LNAV. Because you did not select any arrival star neither runway (which was a problem on the past), i tried recreating the flight again but selecting BAVES1 arrival and runway 27. i selected the arrival procedure with no issue, as soon as i selected runway 27 and i had a gizmo soft crash! I cleared everything and managed to complete the fmc programing including the arrival and runway. Departed again and had the same weird LNAV behavior, i manually pressed LSk3 and then LSK1 skipping the initial LSK1 conditional and LSK2 (int) orders from the legs page and now LNAV was able to turn right and join the magenta properly. A bit later i realized VNAV was unable to engage, i had to remove the miss approach procedure from the legs page leaving RW27 as the last step on the plan for the fmc to allow me engaging vnav and resume the flight. conclusion: there is a big mess here trying to recreate this flight, full of problems. I wonder whether this is related to navigraph database (running 1607rev2 here) or part of the fmc fine tuning still in progress. the developers should try to recreate this flight and shed some light here.

Yes, this is the normal and correct modeling. The APU receives fuel from the left tanks. If you can still operate the pumps from the hot battery bus, you can open the crossfeed valves and pump fuel from the center to the left tank to get the APU started In your case where the situation has unfolded while unmonitored, your best bet is to look for a good spot to put the plane down Please read this page at the very least before proceeding: http://www.b737.org.uk/fuel.htm

Need some zzzzzzzzzzzzzzz's Last ones for a while i promise Tried filming around KSEA, upload tomorrow

mmm this is weird. can you share more details? i would be happy to reproduce it and provide more evidence to the developers. It is necessary you share the detailed flight plan you loaded on the fmc, departure runway, sid, route, arrival star, runway. What altitude, ci, you configured? What navdata version you have installed? it could be also an error on the navdatabase. Just saying it doesn't work will not help the developers reproduce and fix it if anything to blame ixeg for.

We also have a system in place that will initialize your TA to either 18000 (western hemisphere) or 5000 (eastern hemisphere). Jan

transition altitude (TA) is 18000 by default! do you mean to change it from 18000 to 5000 instead? it is on the PERF PAGE 1. Press MENU 2. Press LSK1 (FMC) 3. Press LSK6 (INDEX) 4. Press LSK3 (PERF) 5. type 5000 on the sractchpad and press RSK6 to replace This is the step by step, there are several pages on the fmc where you can press INDEX soft key then PERF and get into the PERF page LSK# (Left Soft Key on the screen 1 to 6) RSK# ( Right Soft Key on the screen 1 to 6) hope this helps

EDIT: A temporary HotFix downloader is located here. Hi Folks, We had an unexpected situation which caused us to take down the server for analysis and re-configuring. Because this was not planned, it was very abrupt and we were unable to communicate this as a planned maintenance session. We are taking this downtime as a great opportunity to make some other updates on the HotFix system itself, so I don't have an exact time as to when this will be back online. That said, I am currently programming a new solution for everyone as a temporary "fix" so you may still update to 1.0.7. This will be out shortly today (USA time). Apologies for the experience, but sometimes things happen that don't always go as planned. We're on it though, and we appreciate all of you for your patience!

Hi there, started to create a fictional Livery for all of you who love to get the sun addicted onto their beaches in the holiday season Hope you like it! Everything isnt finished yet, its the first "try out" after the initial paint session, so if theres anything you love to see, just let me know! Cheers Steffen

Thanks Jeremy! Looks really very promising indeed. Keep 'em coming ;o)

A picture. Evidence that I am actually doing something and that I have "invested" (ie stolen stuff from my parents' basement) in some hardware. Sorry for the weird location, I have my apartment desk torn apart for reorganization and cleaning in preparation for my bachelor's in elementary education. While to most this will be a "who cares" moment, to me it is a massive victory. I've been fighting a battle against Windows XP SP3 for two weeks to get this computer to acknowledge a local area connection. The machine is from early 2005, not 2007 as previously thought. It barely can anti-alias XHSI. As you can probably guess, I'll be splitting these (very much smaller than real life) displays into nine main sections with the MDF panel overlay when it's all carved up with the jigsaw and router: PFD, ND, EICAS, MFD (more on that later), Clock (intentionally in the wrong place, I have to make concessions), Master Caution/Warning, Annun., flaps, and gear indicators. The blank space on the right is where the anatomically incorrect gear lever will be. I hope to have a layer of plexiglass between the monitors and the idiot using them, but budget will dictate that. Now for the "more on that later" part of the post. Today's "Help Colin because he's confused:" The MFD in XHSI is brilliant, with the airport maps, flight surface monitoring, fuel, etc... but once I have my laptop locked in behind the panel and yoke for flight, I won't be able to switch what it's showing easily. The ND is lovely because it listens to X-Plane's opinion of what the ND should be showing, but the MFD has no in-sim equivalent, and thus has no in-sim switch or function to try to cling to for instructions. Here's the question in a nutshell: will it be possible for me to have a rotary selector switch (big words for Colin) switching what the MFD is displaying? If anyone has used XHSI in conjunction with a cockpit populated by physical switches, I'd love help with this. I have no programming knowledge and therefore not rip the program apart to try to establish a USB controller for this purpose. The Yoke I redesigned the yoke. I'll still be carving the "important" (handle) part of it out of MDF in two components to allow for wiring inside without damage to the exterior afterwards. That will be spray-painted black and will likely be the second most fun part of building this panel other than using it. However, I have changed the style of yoke from a true-to-reality floor-mounted pillar-and-yoke to a CH products style homebuilt yoke. Yes, I have a plan. No, I have no effin' clue if I can even get it close to working. I do, however, know that all the parts I need exist and that my concept is sound. The execution will just have to be pretty solid to make this fly (heh). I found a great website for the measurements of the yoke so that it will be as close to accurate as possible. The website may be from the 90s but the information is great and indispensable for cockpit builders: http://www.markuspilot.com/ Pedals You can throw tomatoes for this one. I'm using racing pedals for my rudder. I'm going to try to modify them to more closely resemble the 737 pedal layout (with the block in the middle), but sadly, there will be no way (yet) of having them move simultaneously in opposite directions. I've already taken them for a flight without modification, and they work quite well. It just doesn't quite click in the brain it does when you're using pedals that move opposite to one another. Maybe I'll come up with something for that. Conclusion This is a brief summary of what has changed or been added since my last post: Yoke redesigned from the ground up (and no longer comes up from the ground). Avionics now communicating with aircraft (makes them far more useful). I have a great relationship with the MFD but I fear that distance will make us come apart. Help. I have no idea what rudder pedals are. I need to make sure my avionics don't turn into the Star Field Win XP screensaver on short final (Just looked over and realized this). Thank you for reading, if you have. And thanks for any help in advance regarding XHSI. I am incapable of posting on X-Plane.org for support from the authors (where it's hosted) for reasons that belong in the rant section, not this one. And they are there. Just dig for them.

Hi Torbjoern, Came across this preference manager: http://forums.x-plane.org/index.php?/files/file/33305-x-plane-10-preferences-manager/ Very handy as it saves copying key preferences files for each individual aircraft once it's all set up.

Hi Ikari! From what I can see, there are two commands for "horn cutout". I'm guessing the first one is for the warning of the cabin pressure (overhead) and the second one for altitude warning (pedestal). If I remember correctly, they should both have two states only (away from my X-plane computer at the moment). These commands are specified in the interface guide as: ixeg/733/hydraulics/horn_cutout_act (guessing cabin pressure as it is categorized under hydraulics?) ixeg/733/misc/alt_horn_co_act If you check the two files uploaded in the first post of this thread, you should be able to quickly add them yourself. If not, I'm definitely adding the second one as I sometimes do low-level flying in the fjords of Norway ;o) When it comes to the Master Warning/Caution, I see several that might fit the bill (see comments.txt for all commands). These "might" be the cation (yellow) button for both sides. I'm also guessing that "recall" is for the caution panel that is next to it. ixeg/733/caution/caution_reset_act ixeg/733/caution/caution_reset_cpt_act ixeg/733/caution/caution_recall_act ixeg/733/caution/caution_recall_cpt_act I haven't been able to find the master warning yet. But I'm certain that its buried in there somewhere ;o) I need to look at this further, and figure out what command correlate to each button, but feel free to check it out yourself and report back the findings as I'm away from the X-plane computer until tomorrow. Sincerely Torbjørn

Hi, everything in: X-Plane 10\Resources\plugins\PythonScripts (One python-source file for Xjoymap, one compiled and the .ini file for config) Not installed. Bad sentence on my part. It was a part of the plugin.

Thanks. Will remove the redundant references to EHSI though tried this before - with just lights added - and that didn't work. Where do you place your xjoymap.ini btw? In the resources/plugin folder or in the aircraft one? When you say you installed XjoyMap.... do you mean you created a folder for it in plugins?

Can't see anything wrong here. Did a compare on the files to look for errors in the PI_xJoyMap.py and it looks just like mine. One thing I do see, is that EHSI Map Range is written three times at the top using the same dataref and same name, but with minor adjustments. If you, like me, only use buttons, I would try to remove everything you don't use in the xjoymap.ini file (after making a copy of course), and see if that helps. It's a long shot, but worth at least worth a try ;o) I don't use XPUIPC, XPWideClient, Landing Speed, GroundTraffic or SilverLining, so I can't say if these are interfering in any way. It should be noted that I'm an X-plane newbie ;o) Found something on x-plane.org. Relevant? Hi Rich, Its just that xjoymap loads too soon and the crj plugin haven't had time to register its datarefs. That's a known issue that I have to correct some day. I have to add a configurable wait delay on the xjoymap files and code the feature. Since then, the reload is mandatory, sorry for that ;-P. Oh there's no need to reload python just use the xjoymap "reload config" menu item. Thanks for your comments. PD: Its not all my fault, others planes like x737 send a "I've finished loading" message that xjoymap can wait for.

Sure: EFASS, Gizmo64 (for iXEG 737), Python Interface (obviously!), SilverLining (Skymaxx), XPUIPC, XPWideClient, XSquawkbox, Landing Speed, GroudTraffic (Aerosoft) Files attached. The IXEG makes extensive use of LUA but I removed FlyWithLua plugin and it made no difference. Thanks in advance for your help!! PI_xJoyMap.py xjoymap.ini

Hmm, interesting. Could you share the script and what plugins you use? I simply installed the Python-interface plugin, and Xjoymap. Inserted the datarefs needed, and they popped up in X-plane custom commands under settings (xjoymap). Never experienced that X-plane removed the bindings. Are you sure that there aren't any LUA-scripts running and interfering with xjoymap? EDIT: Here is my config-file so far. xjoymap.ini

Hi Torbjørn, No success... XP still over-writes the saved buttons from XJOY The commands all still there but, for example, the button I select for "Landing Lights 1" reverts to just "Landing Lights" when I reload XP. Hmmmmm

Hi Kopelent. EHSI Map mode and range below. xjoymap will create reversed commands automatically. This is button-based. For axis/wheel, I found that there are several good examples in xjoymaps documentation. But I mainly use buttons, so I haven't looked at that. --code-- [EHSI Mode] new_command=EHSI Mode dataref=ixeg/733/ehsi/ehsi_mode_pt_act description=EHSI Mode values = 0, 1, 2, 3, 4 [EHSI Range] new_command=EHSI Range dataref=ixeg/733/ehsi/ehsi_range_pt_act description=EHSI Range values = 0, 1, 2, 3, 4, 5

Hi Torbjørn, Many thanks for this. I'll check the scripts and report back!

datarefs for EHSI Map range and map mode would be very helpfully for many user i think

Hi Jeremy, Taking the liberty to answer this. Check the python-script for any commands that remove the bindings. If its a template, usually it is one of the first commands. Several templates I have found, start the script by removing any bindings you already have. Luckily, I spotted it simply by chance after reading some feedback on the posters from another forum :o) I think the idea is that they "clear" out any problems before loading their own bindings. Torbjørn

Tobi, Thanks for the above - it's extremely helpful. I've used your 737 template as a starting point and am able to operate all the lights correctly using my VRInsight FMCU. (I use keymapper to assign various key combinations to the unit. I use pushbuttons for the lights - rather than toggles - so altered the values to reflect this.) I have come across an issue which seems to be related to the order in which the python script is loaded, however: my X-Plane Keys.prf is being over-written every time I load XP. The PythonInterfaceLog shows that the datarefs being referenced via Xjoymap are not being loaded in time so I assume that XP attempts to replace the relevant key combinations. I can manually reselect these key combinations from within XP but this gets cumbersome when there are so many of them! Any suggestions here???

EDIT: EHSI now working Okay, so been trying for a couple of days now... Some experiences so far is shared below. If anyone see something interesting or odd, please shout out. I'm more than happy to try out different approaches and ways to get all the datarefs I want to work :o) My goal is to provide a "complete" control-set for the most used switches, buttons and knobs for the TM Warthog. Landing Lights Turning the all on, no issue at all. Using a toggle-button on my hotas. Flip up; all light on. ;Regular Landing Lights all on, but cant turn off. [Landing Lights On] new_command=Landing Lights dataref=ixeg/733/lighting/land_light_all_act on_value = 1 off_value = 0 Turning the off is a different matter. I tried to solve this by taking the inboard LL first, as they are only two staged and makes things less complicated. The issue is however how to combine two datarefs into one command. There was some hints that I could first combine multiple datarefs, then set the value applicable for theese and different on/off values, and then combine these into one button, but I did not succeed. Inboard and outboard also contain different values themselves. Inboard is 0 and 1. Outboard is 0(off), 1(extend) and 2 (on). Finding a logical solution of combining them all in a good manner is quite challenging. Also after watching the wonderful video from Airline2Sim, it turns out that one doesn't extent the inboard lights on takeoff due to drag (same as with MD80) which was quite informative. So combining the datarefs for inboard lights is my priority. See failed try: ;Defining left light Combo6 [Landing Light Combo] new_command=Landing Lights Combo6 dataref=ixeg/733/lighting/l_inboard_ll_act ;Defining right light Combo7 [Landing Light Combo] new_command=Landing Lights Combo7 dataref=ixeg/733/lighting/r_inboard_ll_act ;Defining Command that combines nr 6 and 7 to one command "8" and sending it to X-plane [Landing Light Combo] new_command=Landing Lights Combo8 main_command=Landing Lights Combo6 main_command=Landing Lights Combo7 on_value = 1 off_value = 0 Taxi-lights. Quite easy. Simple on/off state. Flip a switch, they're on and visa versa: ;Regular Taxi Light On Off Switch [Taxi Light] new_command=Taxi Lights dataref=ixeg/733/lighting/taxi_lt_act on_value = 1 off_value = 0 Turnoff-lights (using spring switch) This was just for fun. The TM Hotas has two spring-switches with three values. 0(regular "off") 1(regular "on") and 2(spring). I wanted the spring-switch "2" to turn the lights on. Then when I did the same thing again, turn them off. Flick up to turn on and flick up to turn off again. The problem is that the the switch "springs" back, the light turns off (naturally). So finding some way to keep the value of the input, and then repeat it is something I'm looking into. Right now I'm not using the spring-value and simply use "0" and "1". Works fine for now. ;PROBLEM: Cant set spring button to set and forget [Runway Turnoff Left] new_command=Runway Turnoff Left dataref=ixeg/733/lighting/l_rwy_turnoff_act description=Runway Turnoff Left on_value = 1 off_value = 0 [Runway Turnoff Right] new_command=Runway Turnoff Right dataref=ixeg/733/lighting/r_rwy_turnoff_act description=Runway Turnoff Right on_value = 1 off_value = 0 EHSI increase by button Alright. This does the trick. xjoymap also creates a "reverse" command automatically. I now use the four-way mic-toggle to increase and decrease EHSI map range. Cool! [EHSI Mode Flick] new_command=EHSI Mode Flick dataref=ixeg/733/ehsi/ehsi_mode_cpt_act description=EHSI Test values = 0, 1, 2, 3, 4 This one is quite interesting. I'm able to move the rotating switch. But I can't figure out a way to limit the rotation. Say that button-click rotates the EHSI-knob once to the right, when you get to the last value and click it again, it actually rotates the knob beyond the limit and it returns a Gizmo-warning. The switch actually physically rotates beyond the limit as well ;o) So setting a fixed limit, giving each point on the rotation a value and making sure that increasing (or decreasing by another button) does not exceed that limit is something I simply can't figure out. Below is just an example of the multiple ways I've tried. ;Problem Limit is reached and return Console warning. How to set threshold ;[EHSI Mode Increase by one] ;new_command=EHSI mode increase by one ;dataref=ixeg/733/ehsi/ehsi_mode_cpt_act ;description=EHSI mode increase by one ;values = 0, 1, 2, 3, 4 ;increment=1 ;[EHSI Mode Decrease by one] ;new_command=EHSI Mode Decrease by one ;dataref=ixeg/733/ehsi/ehsi_mode_cpt_act ;description=EHSI Mode Decrease by one ;increment=-1 ;type=float ;repeat=True Other ways to program buttons The way as described above has its limitations. I looked at "Cosmopilots" lua-file (here) I was able to import this into FlyWithLua, but the script stopped "due to unknown character after then", but the script seems fine to me. It should probably use something else than FlyWithLua?

Hi gents...welcome. I've been a bit too busy to come play with you guys but will at some point. Once we get a few more features in and this things stabilizes, then I'll poke my head in here and we can discuss if any extra datarefs are needed. Thanks for jumping in. -tkyler

Puh! I started to fell somewhat stupid there for a second. This looks much better. Thank you so much Tobi. If this is the benchmark of the community, then my X-plane future is lookin' good! I will try to create a sensible Warthog Hotas config-set from all of this and continue with the control-sets. If you're building a cockpit yourself, please don't hesitate to share more info. It's always interesting to see what the experts are able to pull off. Sincerely Torbjørn

When i open the attached file "PythonInterface.ini", it contains: [DEBUG] DebugCallbacks = 0 CheckCallbacks = 0 The x737 was only an example file provided with the plugin, so i used it as an example on the type of file I'm looking for. You don't have to do another file for the x737 just for me :o) But I'm guessing you've attached the wrong file? Torbjørn

Hi Tobi! Awesome info. Thanks! We're are definitely heading in the right direction now. It seems that the file you attached only draws callback from the debug, but that might be intended? Anyhow, I can see a template for the x737 that is included in the plugin (.xjm file), but if you already have one on the way, could you share that one as well? Again, thanks for the help so far :o) Edit1: Tried adding a simple Taxi-light command: [Taxi Light] new_command=Taxi dataref="ixeg/733/lighting/taxi_lt_act" on_value = 1 off_value = 0 Works like a charm! Outstanding :o) Well, time to open a Redbull and get started creating some new controls. Torbjørn

LDG red lights have no connection with the engines at idle. Sent from my iPhone using Tapatalk

Pleez no! Too much work, too little gain.