Litjan

Yes, it is fairly easy to get into trouble doing this - keep in mind that on the 737 classic NO autopilot or autothrottles modes will be used or armed while still on the ground! The autothrottle should be "armed" while lining up on the runway and then pushing the TOGA buttons will actually trigger the take-off modes for the flight-director (if they are on) and the N1 (full takeoff power) mode for the throttle. Happy landings, Jan

Hi Simon, welcome back! I personally haven´t really tried the "other" free add-on - but I keep hearing great things about it and anything that furthers our hobby is good in my book. And as they sometimes say - with the money saved on the Zibo, go ahead and buy the IXEG . Happy landings, Jan

Hi Irargerich, hmm, those are odd problems - maybe some other plugin you have running could be interfering. However the autothrottle can also take control of the throttles on the ground - that is why they are "armed" only shortly before entering the runway: If a pilot touches the TOGA buttons, the autothrottle will engage and set takeoff power! The little lights are indeed "marker beacon" lights. There used to be radio markers associated with ILS approaches, sometimes we still have them these days. When you "overfly" them, they will make the lights flash and a beeping sound - this tells the pilot that he is a certain distance from the runway. Cheers, Jan

Hi Irargerich, thanks for your kind words! Lets see if we can shed some light onto this... 1.) This usually means that the autothrottle took control of your throttles. If the autothrottle logic does that, we remove control of the throttle from the user, because normally users do not have a throttle that can "move" (it has no motors). The autothrottle will take control if the user tells it to - like if engaging a certain autopilot mode or autothrottle mode. But sometimes the autothrottle also jumps in to save the aircraft if the user tries to fly too slow - this is a reversion mode. To get out you need to increase the commanded speed by 15kts (and be fast enough to not get into reversion again) - or you need to turn off the autothrottle and then "regain" control by using the ghost-throttle symbol to align your hardware thrust levers to the virtual thrust levers. I recommend watching my tutorials on autopilot use here: https://forums.x-pilot.com/forums/topic/10746-training-videos/ but also this: https://forums.x-pilot.com/forums/topic/18101-faq-for-new-users/ 2.) Make sure you "turn on" the avitab, there is a little button on top of it on the CPTs side - we default it to "off" when starting cold and darke 3.) We use the "normal X-Plane" braking system. To help you troubleshoot you can display the "gear and brakes" status on the "DATA OUTPUT" tab, this will show you small green numbers on the screen that indicate the status of your brakes. It could be that you use the autobrake or the parking brake is still set... Cheers, Jan

Bom dia, We will not sell on Steam - and even if we did, the conversion rate to Brazilian Real would be the same that as you face when purchasing with credit card from X-Aviation. The plane would not be "cheaper" on Steam. Adeus, Jan

Hi, I have never used VATSIM, but I am sure it is possible with the IXEG 737 or we would have heard about it before... Maybe someone else can chime in with how to set it up? Cheers, Jan

Thanks for the heads-up!

Hi, we already changed it once to be more in line with the true-to-life reference we had for the retrofit winglets for the 737 Classic (keep in mind that those retrofits are very rare and not to be confused with NG winglets) and I don´t think we will change them again. Cheers, Jan

Hi, this sounds (haha) definitely weird. The starter of the CFM56 is a turbine that is powered by compressed air (usually from the APU) - so it should be a loud "woosh" as if someone punctured a highpressure gas bottle. Definitely not a lawnmower... There is a "sawtooth" sound at low RPMs that is emulating the grating and low-freq vibrations you can feel when the engines just start turning. I have to doublecheck the sound in the cabin - I have not done so yet, I think - only listened to the startup from the cockpit (try with the windows open!) and from the outside camera. That being said - we are in the process of moving sounds to FMOD (from OpenAl) and that should cure a lot of the "sound curiosities" we still get from time to time. Cheers, Jan

Hi Alessio, Hmm, they should be working - just assign the corresponding axis to "left toe brake" and "right toe brake" in X-Plane as usual. I don´t have the Saitek G pedals, so I don´t know if there is anything special involved to get those working - but we are using the basic default X-Plane function for brakes, so there is nothing special to the IXEG 737 here. Let me know how it goes? Cheers, Jan

Hi Sandpatch, the original Classics (when I started to fly them in the 90s) didn´t have a GPS at all. They navigated by IRS which was corrected with DME measuring for position accuracy. It would not have been possible to fly a GPS approach with them. Later they decided to put the EGPWS into it - which required more precise location accuracy - so it came with a GPS receiver. Boeing then "slaved" this GPS card into their FMS to update the FMC position more accurately than the DME (0.1 NM accuracy) could do it. So the 737 Classic only has one GPS receiver. It can do GPS approaches, but there is no redundancy. Cheers, Jan

Hi! I am not familiar with the interfacing of X-Plane to real cockpit hardware, I will ping Tom on this (he coded it) and maybe some of the other cockpit builders can chime in? It must be possible, I think. Cheers, Jan

Hi hazii, - I agree that this could be improved. I will talk to Tom about those lights (also reflecting of the ground a bit more)... Cheers, Jan

Hi Tomas, normally you can assign extra axis to "reverse 1" and "reverse 2". I have just tried on my end and it works fine. Please note that there is an incompatibility with some versions of XPUIPC, so if you use that, you may have to find an older version that works...but if the forward thrust works for you, this should not be a problem. Cheers, Jan

Glad you got it to work - sorry for the long response time, I had to fly a (real) simulator checkride the last two days and wasn´t on station as much as I usually am. Let me know if anything else crops up, Cheers, Jan

Hi Chris, this does work, of course - the commands to map are ixeg/733/autopilot/AP_disengage and ixeg/733/autopilot/AT_disengage. The trimming works fine because we use the "default X-Plane" commands for that. I do not know why you don´t see the ixeg commands in your command list - I also use a Thrustmaster HOTAS setup and it works fine for me (and everyone else). You may have to have the IXEG running while trying to bind those commands (as they are supplied by the plugin), maybe that is the problem? Let me know if this works? Cheers, Jan

Hi Dipperdolphin, I am not quite sure what you are seeing - keep in mind that the VNAV descent path is still not working reliably in all situations - it is one of the parts that is only working under certain circumstances. Here is a complete list of what is still "under construction" as of now: https://forums.x-pilot.com/forums/topic/8526-things-that-are-not-going-to-be-in-v133/ I did not see our aircraft "oscillate" while on the path, though (it is either working quite well or totally off the beaten path ) - a slight variation of rate of descent would be quite normal, though, to adhere to the calculated geometric path. There is also other functionality where the plane will add bursts of power in case of higher than calculated headwinds, etc. If you want to post a video of what you are seeing, I might be able to diagnose it better. Cheers, Jan

Hi Mizra, your observation is correct, we did not model the elevator column trim cutout - I have it on my list of things I would like to add...nothing is ever perfect . Thanks for your nice words, Jan

Well, this would be up to the user - I can offer a command to map for the GRD CALL - then the user has to map that to a button and also map the same button to the "Request pushback" command. This would be a "dual mapping" which is normally not a good idea, but I think it would work in this case. One can try if it works by taking one of the commands that are already implemented, maybe (ixeg/733/...) Cheers, Jan

Hmm, I could make a command for the grd call button so that you can map it to a joystick button - then you can map the same joystick button to a better pushback command (if they have one)... Cheers, Jan

Hi guys, yes, this is a known bug - it is caused by a computational issue with the gizmo code and will be fixed with the next gizmo version. For now just use the APU to power both buses - or accept the left bus being offline, it does not power any critical systems that you would need during turnaround (some fuel pumps, etc.) The default view is not lined up with the yoke because it is adjusted to give you best visibility of as much of the instrument panel as possible. If you prefer it to be lined up differently you can either (easy) set a new position in X-Plane and save it to "custom view" (CTRL-Numpad) or you can adjust the viewpoint in planemaker. I take the liberty to provide this link to the "bug reports" section, where exactly this issue was already discussed: https://forums.x-pilot.com/forums/topic/19423-elec-bus-issue-after-shutdown/ Cheers, Jan

Hi Mike, we do share that feeling! The years on the 737 were the best in my airline career, flying the 747-400 was nice...but you rarely ever flew it. Maybe from OM to touchdown . They sent me on to the A320 in 2012 and I still miss my 737 every time I fly with a FAC or SEC... Please keep the feedback coming, we are currently in the big "VNAV rewrite" - it is a complex beast and the initial attempt (as you found out), fell short of the target. Our last big push fixed a lot of problems with the lateral procedures, especially with entering and amending them...and we feel we have reached a fairly stable state with those. To get there with VNAV is our declared goal. Cheers, Jan

Hi Mike, About your observations - first, those are very welcome. I have flown the 737 for 10 years, but only the "Classic" variants. I stopped in 2012 (after being CPT for 4 years on it), and we modeled our aircraft after the variants I flew back then - so they aren´t incorporating any newer enhancements, updates to the FMC version or other airline options. The horizontal flight-director bar was modeled after videos I took of ours during the takeoff run. It stays on the bottom of the EADI until about 80kts or so - then move up swiftly to 15 degrees - you are obviously not supposed to follow them at this time, only after liftoff will they give valid guidance to stay at V2+15 (adjusted for any subsequent speed changes within a certain range). The VNAV options for descent are not fleshed out yet - we are still working on it. What kind of "works" is an unencumbered descent with no horizontal restrictions, anything else will likely not work and I encourage to use more basic modes along with "old fashioned descent planning" to manage your descents. Here are some links to what to expect from version 1.33: https://forums.x-pilot.com/forums/topic/8526-things-that-are-not-going-to-be-in-v133/ https://forums.x-pilot.com/forums/topic/17981-version-133-known-bugs-and-workarounds/ Cheers, Jan

That is weird - it should only have an effect on the way the autopilot behaves in the IXEG 737. Make sure you don´t change the joystick setting in the default X-Plane joystick menu - only in the IXEG preferences menu that comes up when you bump your mouse on the left side of the screen.

Right where I wrote it is. (The slider is called "Joystick CWS deadzone" and it is in the "Miscelleanous" field of the Preferences). Cheers, Jan