Litjan

Hi Ramon, thanks for posting over here - I am hoping maybe a user with some experience along those lines, or even @tkyler or @Cameron have an idea what the problem here is?

I don´t see anything unusual in your log - I would doublecheck for latest drivers and no overclocking...but other than that - no idea. And it is not a problem I have heard of before :-/

That is good, why don´t you let us know, too?

You have (I believe) three activations - so you can use the IXEG on three computers. As soon as you try to activate it a FOURTH time, you will be forced to FREEZE one of the previous activations, rendering that machine unable to run the IXEG forever. So I can not believe that - in order to activate the license on a second machine - you have to deactivate the first one. You get three activations before that step is necessary. Did you maybe install the IXEG on other computers as well (like a traveling laptop or on another machine upstairs or so)?

Hi there, switching to Win11 should not cause any problems like this - but may the configuration of your joysticks is off center now and this will prevent engagement of the autopilot - just like in the real aircraft. The autopilot will only engage if the yoke is not deflected. Let me know if this helped? Cheers, Jan

Thanks for reporting this! I can confirm the problem with the packs - the cabin pressure should leak, but it appears to be almost completely airtight (resulting in 0 rate of climb with packs off), I will investigate the code! The FLT/GRD switch only works while the aircraft is on the ground, as soon as it lifts off, it is automatically entering flight mode.

It has taken a while for me to test this - and it works fine on my side using the default X-Plane AI traffic. If it does not work with Vatsim, they need to fix it on their side, it may be that they changed something and do not adhere to the X-Plane conventions for traffic indication.

Yep, disabling Zink should solve this.

Hi and thanks for the feedback. Your point about the engine starting speed is known - we are using the default X-Plane behavior and the initial ramp up to starter cutout speed is too fast, a fix for that is forthcoming. However I tuned the full startup to take exactly as long as the average start does in the real aircraft. Your last point is also a know issue and well described in the pinned post https://forums.x-pilot.com/forums/topic/8526-things-that-are-not-going-to-be-in-v15/ which I put up to be fully transparent to prospective customers about what to expect and what not to expect from our model (see the last point about the FMS). The other quirks you describe are unknown to me and may be a combination of third-party content (like your sound pack) and/or user error/hardware setup problems. If you could capture a short video of what is happening, I might be able to analyze what is going on - when you disconnect the autopilot there should be NO input to the flight controls whatsoever (except for the pilot´s inputs), so there should not be anything moving the yoke or interfering with your control at all. Cheers, Jan

Lol, we are not far away from the glorious future where chatbots will fight with each other...I will just have to teach ChatGPT to read these forum threads for me...now what am I going to do with all of that free time? (I certainly won´t have to spend it on developing the 737 anymore, because ChatGPT will find an excuse for me not doing it ).

Hi Joachim, thanks for the info - yes, they are a bit more weak than in 11... and the one on the tail is missing indeed, we intend to add it back! Cheers, Jan

Yes - this is not a flight phase annunciator, it it is the thrust limit annunciator and will indicate to what maximum value the autothrottle is allowed to set power to if it needs to.

Thanks for the heads-up, Dominik, I will doublecheck...

Hmm, that sounds weird...make sure the option in the default X-Plane flight setup window is set to "engines running" (checkbox checked). The only other reason I could think of is something wrong with your monitor resolution so that the mouseclick does not hit the right spot?

It should be possible to assign a button to "toggle reverse thrust" and then - after pushing it - the thrust levers will govern the reverse thrust level. Make sure you are at idle forward thrust when toggling this button, though - you can not invoke reverse thrust unless you are at idle (like in the real aircraft).

Hi, I also use a 4k display and agree - it would be desirable to increase the text size with rising resolutions. I hope to be able to get this included with a future update. Cheers, Jan

Thanks for confirming that, @SeaHawk14! It highlights a problem that not only we at IXEG but also Laminar Research has: Buggy add-ons that lead the user to report a "bug" to us (or Laminar). I wish that everyone would test their X-Plane (and our IXEG) without any other addons possibly interfering before coming to us (or Laminar) crying BUG!!!!

Thanks for reporting back. However, it surprises me that you were running Vanilla (+better Pushback) and that was crashing, however now you took out XPrealistic (which was not even installed on your crashing version that you sent your last log.txt from), and the crashes stop? It is pretty mysterious how programs install and uninstall themselves on your computer, unbeknownst to you... It also makes it pretty difficult to help you, if you and me both don´t exactly know what is installed and what isn´t.

Yep, it works totally fine. I am sure that you forgot to turn on the WXR power switch here: (Yes, the weather radar power switch is ALSO needed to enable the EGPWS terrain display, it is a retrofit for the 737 classic and piggiebacks on the weather radar symbol generator to generate it´s returns).

It is not known - and I believe not true...however I will gladly test this on my side today and let you know what I find out!

Huh, that is weird - I don´t get the bell at all when I use that switch. Maybe a plugin is interfering?

No, that should not be a problem - if you get too few (below 20) you would get into problems where the simulator time slows down as the flightmodel is depending on fast enough framerate, but too fast? However, it surprises me that you get such a good performance, are you running deliberately low with your graphical quality? I would expect you to get between 40 and 80 fps - unless flying in the middle of the ocean, of course.

Your hardware is certainly very capable - and it is a good sign that your total vanilla installation is stable. Now I know that people are using Better Pushback with no problem (do you have the latest version?) and I know that people use our IXEG with no problem.... I am not aware of systematic incompatibility between these two add-ons, but it would be interesting to find out if you suffer crashes when using EITHER only BetterPushback OR the IXEG? Another thing to consider is overclocking (you shouldn´t).

And I also doublechecked the engine start times in our latest version: Time from actuation of start switch to 25% N2 (fuel introduction): 20s Time to starter cutout (46% N2): 25s Time to stable idle run (21% N1): 55s I agree that the time from 25% N2 to 46%N2 is a bit too fast (this is a X-Plane problem that should be solved in the near future, I worked with Austin on this), but the total startup time is realistic.

I am not sure if you are using the IXEG or some other aircraft?? Here is the LIGHT TEST button, if you activate it, no sound is played: Here is the Firewarning test switch, if you toggle it to the right, the warning lights illuminate and the bell sounds: Here is the EFIS CONTROL PANEL with the VOR/ADF pushbutton, if you enable it, you can see RMI indications on the EHSI map: