Litjan

No, you can´t enter coordinates like that. Even the real FMC does not accep that, you would either have to make temporary waypoints (we don´t model that), or add them in a special format (so they only take 5 digits). We don´t model that yet. There are published coordinates for atlantic crossings, and those are supported. Cheers, Jan

No, you can´t Cheers, Jan

Hi Steve, I am not really sure what you mean with the red button autopilot error? Does the autopilot disconnect? Your route on the FMS looks good, but your descent path has two restrictions in it (230B and 100B) that our Vnav logic does not handle well (yet). So it might be possible that you run up against that. Unfortunately there is only one thing I can recommend in that case, and that is to fly the descent in an autopilot mode that is more under the pilot´s control, like FL CHG or V/S. Cheers, Jan

Without checking my wiring diagrams I would say that this is probably a bug. We fixed some stuff with regard to the standby power system, and that may have slipped under the radar! Thanks for pointing it out, I will add it to the bug base! Cheers, Jan

I have never seen this before... My guess would be that you are running some 3rd party add-on that is messing with art controls of X-Plane itself. Try to remove/disable all of those and then add back one by one to find the culprit! Cheers, Jan

For our aircraft there was the possibility to load the routing (it is called "company route") into the FMS - but no performance data or such. All that stuff had to always be entered manually - and then doublechecked by the second pilot, as putting in wrong weights is obviously pretty dangerous... Cheers, Jan

Hi sensfan, usually this is due to clickspots "overlapping" - try to move the view a bit to avoid that. Especially the TOGA button is really hard to press. I wholeheartedly recommend to map a button or key to the TOGA command (we use the default X-Plane command). Never had a problem with setting the autobrake, tough. Cheers, Jan

Hi Patrick, thanks for following up on this! I have no idea why "carb heat" would affect a jet engine...oh well. Happy that it works for you now! Cheers, Jan

Well, there is a certain fueling schedule to be adhered to (wing tanks first, then center tank) - and when fueling automatically, this is what you should see. However, we want to give people the chance to also experiment with non-standard fueling setup, or to see what happens when they don´t use the fuel in a standard way. You could theoretically use up the wing fuel (or one side of it) first. Or you may want to try to remedy an imbalance between the wing tanks, and to set that up it helps to set each level individually. Cheers, Jan

Hi Shabazza, you are right in that the fuel load does affect the CG. As does the payload. We - for the IXEG - try to simulate what the pilot does...which is regularly not determining how the payload is distributed, pax seated etc. The pilot simply gets a loadsheet which shows him the CG for takeoff (with the fuel being at take-off fuel level) and the CG for the zero-fuel-weight (which would be where the CG is after all fuel is burned). He (double-)checks wether this is "in limit", then enters the takeoff CG into the FMS and sets the trim accordingly. Thats it. So when you fly the IXEG 737, imagine that the "ground handling" guy gives you those figures (as a printed loadsheet). You simply punch in the numbers. I understand what you are saying - if you have a certain CG and NOW change the fuel, the CG should change...but think of it this way: You have an aircraft with at CG of 23% MAC at 100pax and 6.0tons fuel. Now you decide to take on another 2 tons - so now its 8.0. CG should change...but it doesn´t because suddently 20 pax from the back move to the front - voila, CG stays the same - even though fuel changed! What I am saying is that everything influences CG. Ultimately the pilot gets the CG for takeoff - and in our simulation you get to determine the CG yourself. It is not "calculated" by simulating fuel and weight distribution. Just like in X-Plane, you simply set it where you think it is. If you want to, you can use the real load+trim sheet for a 737-300 and figure the CG out for yourself, of course. Cheers, Jan

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