Litjan

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

Yeah, the wingtip vortices where a "borderline" feature that worked ok in XP10 but caused some headaches for some people. We considered removing the effect altogether, and might do so for a future update. Happy you got it to work ok for you, cheers, Jan

Hi t4murphy, this is usually due to some other 3rd party program altering "art controls", like to get certain environmental effects, changed hue, colouring, etc. It could also be due to outdated graphics drivers. To troubleshoot, please disable all other plugins, then add them back one by one to find the conflicting one. Thanks, Jan

Hehe - at my real job I deal with roughly 800-1000 customers every day, and let me assure you, sometimes the customer is a total idiot . Now to elaborate a bit more in relation to this post: I don´t think that Shobhan Nandy falls into that category. But I think he is victim of false expectations. I think he is really really REALLY fascinated with the details of the FMC and I must say that we did not develop this aircraft to be a training tool for FMC technicians. What does the term "study level" entail? Well, there are different perceptions, but I don´t think that any software exists (and that includes all LEVEL-D simulators) that can truthfully simulate the real aircraft´s behaviour in all circumstances. I am fully aware of our FMC´s shortcoming (although I never even knew the " version, revision and update version no. " of the FMC when I flew the real aircraft). We have placed emphasis on recreating the experience of flying a 737-300 in a realistic, "close to true life", fashion. I don´t even know some of the features that Shobhan is talking about (capture mode? Agility tuning?). We get good feedback on the areas that matter to me as a pilot (flight model, system modeling) and we are planning to work on the FMC some more in the future. I am not happy with the speed of updates myself, but it is what it is, to quote someone I know . Study level? Certainly not for the FMC, I agree. I can´t say if the Zibo mod is better than our aircraft, haven´t tried it myself. Cheers, Jan

Well, here is all I want to say about the OP´s post: You are entitled to your opinion. Cheers, Jan

Hello Phillipp, here is the link to the original thread with the problem. fabiosko seemed to be able to trigger this one fairly reliably, but I am not sure how much he still experiences this. I will also PM you with some info on this. Thanks for helping us out, Jan

Hi shabani, I don´t think the problem lies with x-aviation or that they can do anything about your sound problem. We have our own IXEG custom sound engine providing the 3D-sound for our add-on and there is a chance that a combination of sound chip/hardware properties and/or other add-ons could cause your problem. At this point it is unlikely that we can fix or help you with your problem, especially since you are the only one who has reported it. I am sorry that you have a degradation in sound quality, but we can not recreate the problem and therefore not fix it. Cheers, Jan

Thanks, Ben - I dare not to tinker too much with my router settings. I remember an unfortunate attempt a few years ago to open some specific ports and that went really not well at all. I prefer the "get the long LAN cable out of the basement and run a bypass" solution . Cheers, Jan

Update: Finally got it to work, and I am posting how here to help other people with the same problem and X-Aviation in troubleshooting the problem. This is how my computer is connected to the internet: 1.) The signal (DSL) enters the house and goes into a WLAN router. 2.) The line goes from the WLAN router into a second WLAN router (in my office), type Netgear WGT624. 3.) The line goes from the second router into my computer. This configuration did not work with the download. However, when I plugged my computer directly into the first router (bypassing the Netgear), things worked flawlessly. Off to some winter flying! Jan

By using a conversion table - and now look at that: It is mounted right in the cockpit for your convenience. Gee whiz! Jan