Litjan

Hi NZWW, thanks for the kind words. Most of the things you mention we are well aware off and agree - they are on our list of improvements to do! Some things are harder to whack - i.e. the GLIDESLOPE warning is realistic - its just that in real life there is no reception of the glideslope as you use the opposite runway to depart on, hence no warning. I do get that nuisance warning in XP as well. That being said, I am not sure which SOP´s require setting navaids for immediate return - all the SOPs I am aware of require to set navaids for the SID, instead. The autobrake works fine for me (and most people) - make sure that your thrust is really idle upon touchdown. The deceleration rate is default X-Plane, but I did some measurements and found the values to be pretty much in the ballpark for the real 737´s autobrake. The "cockpit lit with seatbelts off" is a X-Plane limitation - it is actually the cabin light "bleeding" through the rear cockpit wall. To avoid that, just keep the belts ON. You can see the dome or emergency exit lights in the cockpit illuminate (fixture is bright) when they are lit, so you can confirm it is neither of them. I have to check the climb N1 again, but I was pretty sure it gradually washes out to full N1 during the climb... Cheers, Jan

I go from about 3 degrees pitch to 6 degrees pitch. This is a change of 3 degrees. If you are coming down on a -3 degree glideslope and want to go to a 0 degree flightpath, this is the minimum amount of degrees that you need to change your pitch to enter level flight. Plus you need to another degree or two for a short time to "decelerate" your sinkrate. This is called the "break". It is not a "significant" rotation, it is the minimum needed on any aircraft to change the flightpath by the corresponding number of degrees. Just like Morten said above: It could be that the Zibo is an .acf file that was never saved on the newer XP-version, so the new pitch-down does not take effect (Laminar has implemented an opt-in model, you need to resave your aircraft for the new aerodynamics to take effect). Otherwise I do not see how the zibo mod would not be affected. Last but not least - if we had a chance to "deselect" this nose-down effect, we still could not do it - without it the plane would lift off by itself during the takeoff run. In fact we had an artificial "nose down" effect before XP11.10 to avoid the plane rotating early - its effect was limited to "on ground", only, though. If you want to go and harass Austin to "soften" the effect, please be my guest - I would not mind a small reduction, but overall the effect is realistic and needed for the airplane to perform correctly during takeoff. Jan

Happy you got it sorted out! Jan

I am really not sure what the problem is for you folks experiencing lack of elevator control or "sucking down" effects - make sure that you have upgraded to the latest version of the IXEG 737 (1.21) and the latest version of XP11. I have made a little video to show that things work perfectly fine on my end - with plenty of elevator authority remaining during landing. Cheers, Jan

Hi Sylvain, you would turn ON the autothrottle ARM when entering the runway for takeoff. Not earlier, so if you accidentially touch the TOGA buttons while taxiing around the airport you don´t want the engines to go to takeoff thrust. The autothrottle should ALWAYS stay in ARM (never turn if OFF) during the whole flight. This guarantees that it is ready to jump into action when needed (pressing TOGA, getting too slow, going to MCP SPD when changing the pitch mode, during ALT AQC, for example). The autothrottle will automatically revert to OFF 2 seconds after touchdown, not pilot action needed. Recently this was changed: Boeing now allows to turn the autothrottle to OFF if the pilot does not want the "combined modes" - for example when capturing the GS or when going to ALT AQC, the autothrottle will automatically engage in MCP SPD. This requires the pilot flying to command "disengage SPD mode!" to the pilot monitoring repeatedly, so Boeing allows to turn the autothrottle to OFF when flying manually. It is undesired system behaviour, so to say. Cheers, Jan

Hi Sylvain, the autothrottle system is very complex and can´t be explained in a few words. Google for a real 737 FCOM (there are plenty out there) and read up if you want to know the whole story. If you just want to know how to use it "normally" I would suggest watching and re-flying the tutorial videos I made for the 737. Cheers, Jan

I think mfor is right - when the right IRS is being fed by DC only (you should see the corresponding amber warning light), you will get a horn sounding - it is the same horn that sounds for the low-airflow warning if the equipment fans aren´t running. To avoid this, always enable AC power supply before aligning the IRS units. If you operate the plane according to the book, you will never hear that horn. Cheers, Jan

Here is my assessment: You are doing something wrong. If you can post a video of the mishap, we may be able to tell you what. Cheers, Jan

Eventually, yes. But I can´t say which ones and when. Cheers, Jan

Hi Jim, I tested in IXEG 1.21 with XP11.20b3 and can not corraborate your findings. Everything works normal for me. Often people have had their joystick settings hosed during updates, I suggest to re-check your calibration and axis setup. Cheers, Jan

Hi Chris, thanks for the letting us know! I didn´t get around to checking with the latest beta, yet! Viele Grüße, Jan

Mmerelles has it right. The indication will be "on centerline" if you are on centerline, no matter what the CRS is set to. However, the autopilot needs the CRS information initially to make the correct turn when capturing. You can try and deliberately set the course "a little bit" wrong, maybe 20 degrees - the plane will still track the centerline perfectly. The principle is the same as if there was a strong crosswind. Cheers, Jan

This may be a case of erronous axis setup and alignment in X-Plane. Cheers, Jan

Hi Sylvain, are you using HDR? It is required for the lights on this aircraft to work correctly. Cheers, Jan

Thanks for verifying that! Jan

Hi Bill, thanks for reporting back! This is really odd - but we have had our share of weird reports regarding the "IXEG custom views" and in my opinion they are kind of redundant anyway with the way that X-Plane natively allows saving views... who knows, maybe we will remove them in the future to avoid weird stuff like you experienced... Cheers, Jan

I wouldnt know which file to get. Try at another airport, maybe? You are the only one with this problem so far, so it must be something unique to your setup. What strikes me odd in some of your pictures is that the standby horizon is tilted...did you open the standby power switch on the overhead? That would explain why the navradio 1 is not working, its connected to the standby bus. Jan

Hi, I just checked and the VOR is getting tuned just fine on my installation (XP11) Make sure that you don´t have any custom nav data files interfering on your installation of X-Plane (in the Custom Data folder). Also make sure that your nav-radio is not "failed" (this can happen if you enable random failures). Otherwise I have no idea why you can´t receive the VOR, everything you set up seems correct. Cheers, Jan

Yep! Grüße nach München, Jan

Oops, I missed that - sorry. You can just move the pilots viewpoint in planemaker. Open up the 733.acf file in planemaker, go to "standard" then "viewpoint" and adjust the "lat arm pilot´s viewpoint" (change the negative number to positive). That should work. Cheers, Jan

We will investigate if the artifact is still there with the upcoming Beta 11.20. If so, we need to report it to Laminar Research. We have had similiar reports, usually related to other plugins that affect the shaders/colouring etc. in X-Plane. To isolate that possibility, it would be necessary to run the IXEG 737 as a standalone plugin with the latest graphics drivers. As for nitpicking the 3D model, I think Cameron has good advice in not getting too obsessive. We (I) like to hear about obvious omissions (like the pitot tubes for the elevator feel system), but on the whole it will never be possible to get to 100% accuracy, especially with subjective assessments (that looks just a tad too slim...) and it is easy to forget to see "what is there" vs. "what is not right". I experience a similiar effect myself when a game or add-on I use is slated for an update. I tend to not play it at all anymore, because I think: "well, its getting an update, so it must be faulty, so I am not wasting my time with something faulty..." I understand the desire to help making a good project even better, but there is a fine line between constructive criticism and "counting peas", as we say in german . I am married to a perfectionist, and trust me, I learned about the downside of perfectionism... Thanks, Jan

Hi Amirello, so far we have not started to adapt our model to the new VR possibilities in X-Plane. VR is not even in beta yet, we will start adapting the model once VR is final. I am not sure what is needed to move the default view in VR to the First Officer - it can be done for sure, as one can see on the default aircraft in X-Plane . I think for now you can maybe start the plane sitting far left, then move your chair over to the right side? Cheers, Jan

I have no idea, I am not a programmer. As far as I understand, the Lua Garbage Collector running is a necessity. Ben has added a way to tweak the values for that in the Gizmo preferences, so you can go for either short, frequent, or longer, infrequent burst of GC activity. Cheers, Jan

Thats a good video, thank you! We had to add the capability to do successive trips later and it turned out surprisingly difficult! Lots of internal variables that need to be reset, and I think you may have found some of those. Added to bug base! I guess a workaround would be a reboot or reloading the aircraft before the second trip, but I think it should work ok without doing that. Thanks, Jan

The latest version is 1.21 - you should see that on the FMS INIT REF page in the plane. The latest version of X-Plane is 11.10 - but running on a VR alpha or soon 11.20 beta version should not affect the FMS calculation. If you just recently (after February, 8th) purchased the plane, you should be running the latest version. And roger on the video, looking forward to seeing it and getting the bug stomped. Cheers, Jan