Litjan

Oh, sorry - forgot that part: That is not normal - the license will need to be "refreshed" every two weeks. You can set it up to refresh "silently" every time you run the plane, so you don´t have to do anything. Check the right-side popout menu for the "Gatekeeper" settings and play with those until you like the result. We have different options because people want different ways to handle this - some want to only refresh "manually", some want a notification, etc. So you can set that up. We allow to fly for those two weeks without activating - in case you go on vacation and are offline, for example. Cheers, Jan

Hi novato, what you are seeing is correct. Oil quantity can vary wildly, depending on when it was refilled last, its temperature, if the engine has been stopped or running for a while and so on. The pressure is the same, especially when the oil is cold or warm, etc. For takeoff it needs to be in yellow band at idle, and in green with takeoff power applied. Variance between engines is perfectly normal. Cheers, Jan

I suggest to watch the tutorial videos I did - I believe this is covered in depth with my constant chatter as a backup to those with weary eyes . Cheers, Jan

In fact the fuel is getting "sucked" into the engines by the engines fuel pumps through a dedicated set of bypass lines - however, this fuel is getting sucked out of the wingtanks, only. So if you have fuel in the center tank, and BOTH of the center tanks pumps fail, you could be in a difficult situation: The center fuel becomes unusable, and you may be getting into trouble with your trim - using the fuel from the wings only will drive your CG forward, possibly out of limit. So even if your fuel remaining in the wingtanks is high enough to reach a comfortable alternate or even your destination, CG considerations may require you to land much sooner than that. Jan

Also keep in mind that depending on the camera angle the "clickspots" for the TOGA buttons can be hidden by other clickspots. So when you move the levers to get 40% N1, you usually need to move your camera up and front to get a good view of the TOGA clickspot. I absolutely recommend setting a button for it. The TOGA buttons are also needed to succesfully trigger the automatic flight system go-around functions, you don´t want to look down and try to hit the TOGA buttons with the mouse when you are trying to go-around from a low altitude situation. Cheers, Jan

You have observed the scavenger fuel pump working. Whenever you turn a center fuel pump off, you trigger this scavenge pump. Its a small electrical pump that will run for a short while and attempts to drain all remaining fuel out of the center tank into the left tank (iirc). It is possible to trigger this pump again and again (not recommended) - the last bit of fuel will slosh around the center tank and depending on the attitude the scavenge pump may not get it all... Jan

Hi, this may well be the case - the "draw vortices" was a GL hack that we tried - but while it seemed to work ok with XP10, there are problems with XP11...so we will most likely take the "draw vortices" option away in a future update. Thanks for helping to troubleshoot this, Jan

All log files can be read with a simple text viewer. There are two different log files getting saved in the main IXEG 737 folder ending with .txt and there is a GizmoLog.txt file in the main X-Plane folder. Cheers, Jan

I think we had a similiar report a while ago...and I don´t quite remember what the solution was . Either an outdated graphic driver version or some third-party plugin changing X-Plane art controls (to change the appearance of the sky, for example...). Anyone remember? For what it´s worth, "normally" this is not the case. Cheers, Jan

I never heard of this problem before - the only "bell" that we have on the 737 is the fire warning bell - if you have random failures on, it could be the case that your engine is burning. A reload of the aircraft should stop that problem, though. If this happens ALL the time, something else is wrong - possibly another plugin interfering? To really see what is going on, we would have to see a video of the flight, so we can see the steps you do, listen to the sound, and hopefully find out that way what is wrong. Thanks, Jan

It is most likely due to inadvertent pressing of the rudder pedals (toe-braking). This is default X-Plane autobrake behaviour, and we have not changed that. The real 737 will also disarm the autobrake, but only if you apply a certain brake pressure over a certain amount of time. X-Plane does not mimick that. Try this: Display the rudder application (using data out option) onto the screen. Your values for left and right brake should be 0.0 if you don´t touch your pedals. If they are not, chances are that your rudder pedals are not calibrated right. Next try to land with autobrake, but keep your feet of the rudder (to avoid any accidental brake application). Does the autobrake still disarm? The last problem could be that you are seeing unwanted "brake-helping-in-turn" application by X-Plane. We have seen some reports of that - you can fix this by changing a value in planemaker, read this post to find out how: Hope this helps, Jan

The DRM will detect that you run gizmo from a new computer. It will prompt you to activate the 737 on that new computer, and if you are already at your maximum number of devices, it will ask you to "FREEZE" (= never use again) one of your devices. Since you are getting a new PC, you can just "freeze" the old one, that you will not be using anymore. Cheers, Jan

These lights will activate when you pass over the respective marker beacon (white= inner, orange = middle, blue= outer). These markers are becoming very rare in the real world - they are supposed to alert the pilot to a certain phase of the approach, but are now being replaced by DME or RNAV positional indications. In the real cockpit you can test them by pushing the buttons itself - but we have not implemented that. If you want to see them work, you can fly the ILS 04R at KBOS - it still has OM, MM and IM beacons! Jan

Try to output datarefs 25 and 26 to screen (throttle commanded and throttle actual) and see if they react when you move your throttle. Also make sure that your joystick throttle(s) is set to Throttle or Throttle 1 and Throttle 2. I HAVE HAD some quirky behaviour when using a custom joystick profile (instead of the default one), that is also something to rule out. However - grabbing the throttle with the mouse or using F1/F2 should work regardless... Cheers, Jan

Wow, that is really puzzling. Did something happen yesterday that you can put your fingers on? Like a windows update, maybe? Or an update to X-Plane? In flying planes they taught me: When the engine quits, remember what the last thing was that you did (like move the fuel selector, lean the mixture etc.) and rule out that that is the problem... We certainly haven´t changed anything at all (yeah, I know...) over the last weeks, and I am also running the latest beta 11.25b1 and windows version (I also have the Warthog HOTAS throttle) and everything works a-ok on my end... Lets see if someone else has an idea... Cheers, Jan

Hi Josh, can you post your LOG.TXT file (you will find it in your main X-Plane directory) after running the IXEG 737 and then shutting down X-Plane? Maybe that will give us a hint. If all else fails, delete all your preferences https://www.x-plane.com/kb/deleting-preferences/ and see if that helps? Other than that, I am totally out of ideas... :-( Maybe you can find someone really tech, hardware and X-Plane savvy that could take a look? I am sure it is something easy that we are missing, but its very hard to diagnose this sort of thing over the forums. Good luck, Jan

Very strange indeed, especially since it is working with other aircraft! We are not really doing anything "custom" with our throttles - except for when the autothrottle is engaged, at that time control of the thrust levers is taken from the hardware, but that should only come into play if you actually engage the autothrottle in a command mode. I would also try to click the "Reset to Defaults for Saitek Pro..." option shown on the screen, and also do this for the Joystick and Rudders (if you have them) - this is to rule out that you have some other axis set to interfere with throttle control (like reverse thrust or the like). One last thing to try: Disconnect your throttle and joystick and try to use the default keys to move the thrust levers - F1/F2, if I remember correctly. See if that works. I am sure it is something specific to your setup, since this is the first time we have had that problem in 2 years of selling the product - and there are many people using your hardware as well... Cheers, Jan

Hi Josh, I just doublechecked on my installation with 11.25b1 and my Thrustmaster Warthog Throttle - this is the way I have it set up and both thrust levers work independently with this: Doublecheck that no other input device is interfering, especially some plugins like "fly with lua" and such have a history of doing magic - sometimes in an undesired way . Let us know how it goes, we will stay with you until it works! Jan

We don´t really drive the engine oil temperature, it is default X-Plane. We have overriding this on our list, but so far we are just taking the default X-Plane value (which is obviously a bit high in XP11). Just ignore the high temp for now, it won´t hurt your engine at all. Cheers, Jan

We haven´t heard that one before, but it may be possible that you are assigning the throttle to some wrong throttle command. Try browsing the list, there may be another, more generic throttle command. I can´t see what you selected, due to the poor quality of the video, can you tell me which command you assigned to your left and right hardware throttle? If some other axis is assigned to throttle, it is likely that you can´t move them with mouse or keys at all. Cheers, Jan

Hi Baron, thanks for the kind words! To answer your questions: 1.) When we built the plane, there was no scroll wheel manipulation in X-Plane yet, that is why we didn´t implement it. It is on the list of things we plan to add. 2.) I don´t think the book will be offered on the XA store, but you can buy it from Mike Ray directly. We worked with him on making that book and it is indeed a good companion! 3.) I don´t own the Go Flight Panel, but others have used them as well, so if you have any questions, make sure to post them in the hardware forum and I am sure others may help you there! 4.) The ACTUAL CG of the aircraft is only shown on the "load and trim" tab that pops out of the left-hand screen. It also shows the correct stab trim setting for take-off. You can enter that one into the correct field on the FMC for the take-off values, and the (same) stab trim settings will show. The cruise CG is actually only a performance planning value for the FMC, it is not taken into account yet, and also real pilots will only enter it if the cruise CG is at an extreme (otherwise it´s influence on actual fuel burn is very small). Cheers, Jan

I think (knowing Tom) that he is aware that -290 is below 0K. However, an application should not crash or show other weird behaviour, even if a user is putting in data (even using DRE, which IS a tool supported by Laminar) that makes no sense. Furthermore, I think that Tom´s discovery could help solve the "teleport to E46 bug" - so pointing out that -290 is not physically possible is beside the point. Its like making an addon plane that crashes to desktop if people bank it more than 30 degrees, and then saying "well, airliners shouldn´t bank more than 30 degrees, so don´t do it!" Jan

I can´t open your Log.txt for some reason - but if your X-Plane crashes it is usually a combination of plugins that is causing it. The normal troubleshooting sequence is to remove all plugins except for the ones needed to run the IXEG, then add them in one by one to see which one is causing the problem. Regular problems are flywithlua, xenviro, and any other plugins that alter art datarefs or such. You can also try to fly with the "show vortices" option disabled, that helped some people with crashes. Cheers, Jan

Friday. Jan

We definitely will - its pretty far up on the list of visual improvements planned! Cheers, Jan