Litjan

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

Yeah, its still a major nuisance and I am sorry that you experience these crashes. I am not quite sure why you get hit so hard, for the most part these crashes have dwindled down to almost zero, it seems. I will try to recreate the crash you reported and then we can fix it for the next update. In the meantime you may be able to avoid this issue by going a slightly different way about entering the alteration, maybe changing the runway first, then the STAR/transition or the other way around. If there is a way you can determine which exact sequence causes the crash, that would be helpful, too. Since it seems to happen to you basically on every flight, maybe you can catch the occurance (with the keys you are pressing) on a short video, these are usually priceless in hunting the problem down. Are you using Navigraph or Aerosoft nav-data? Sorry for the trouble, Jan

Hi Fesi, to avoid this happening: Don´t load the aircraft in a setting with really cold ambient temperature or really cold temperature in the cabin - the AUTO mode may overshoot the temperature limit. If you get the warning, set the temperature controller to full cold (auto), then press the trip reset switch If you get the warning again, set the pack mix valves to full cold (manual mode), then press the trip reset switch. Now set the temp indicator to DUCT, then slowly feed in more warm air (to avoid overheating the duct again). Check PASS temperature from time to time and once the temp is >5C you can go back to AUTO For what its worth, I never get the pack trip warning when flying - so there may be something unusual about the way you operate the pack controls. Cheers, Jan

Hmm, ok - at least we figured out what the conflicting add-on is. Just wish that they would both run together without problems...for what its worth I haven´t seen the "leaking decals" before, so maybe this is just of temporary nature... Cheers, Jan

Hi Antares, you are right, the TACAN (DME) and VOR should also be displayed at ranges 10-40. At 80 and up only "high altitude navaids" are being displayed. This is with the EFIS NAVAID switch being on (tuned navaids are green, unused cyan). When the switch is off, only the used navaids are shown in green. Try to "tune" SY on the VFH radio and see if it displays in green then. I am unable to verify this right this second... I will add the bug you found to our database. Edit: I just checked and ALF isn´t showing when tuned, either :-( Cheers, Jan

This is what it looks like on my end:

The "engine age" should not affect climb rates and cruise performance at all. You would see different EGT and N2 for the same N1 in a differently "aged" engine, but the certified performance will not change. If you find a regime where the plane does not perform as you would expect, I would ask you to specify that, including a screenshot with a stabilized climb, showing dataref output of: weights temperature altitude airspeed engine thrust so I can take a look at that. Thanks, Jan

Hi, yes, I can see that in your pictures. Can you make sure that you run the latest graphics-card drivers, please? I don´t see this on my end - not sure what could be causing it. Are you using any third-party programs that could affect this (changing/enhancing textures, colouration, etc.)? Let me know if those two suggestions helped any! Cheers, Jan