Litjan

Ok, let me know what you find out - I just doublechecked on my side and all lighting in the steam gauge version seems to work as it should. Cheers, Jan

Hmm, are you running any scripts or other plugins that change the way that X-Plane looks? Things like "better nightlighting" or Reshade or such? These have been known to change lighting intensities so that is the first thing I would suspect and remove (temporarily) to rule this out. Cheers, Jan

Hi Karsten, unfortunately I am no guru regarding online flying and comms. I have checked the website of VATSIM, there seem to be various ways to connect - xPilot, xSquawkbox,...possibly different versions. Did you investigate an alternative or check with the devs and other users there? https://www.vatsim.net/pilots/download-required-software I don´t know what we are doing different - as far as I know the datarefs that we use for our radios are standard... Cheers, Jan

Oh, there is one more thing coming to my mind - if one side of the aircraft "drops offline" as you lift off, this might hint at you forgetting to switch the electrical source from the APU to the engine generators. The APU can power both buses while on the ground, but as soon as you lift off, one bus will drop offline...

Hi, not to my knowledge - there is no random failure simulation on the IXEG 737 (yet), you can trigger some failures (like the hydraulic ones) through the IXEG menus, and some of the default X-Plane ones will also work (like engine or APU failures/fire). So I really don´t know what happened there for you - if it happens again, maybe go to the (default) failure menu and click the "fix all systems" button and see if that clears things up. If it does it would be a strong indication that you are getting random (default) failures somehow. Cheers, Jan

Hi Dave, your previous purchase should still be valid and you should be able to simply download and install the latest version. Cheers, Jan

Hmm, I really have no idea what could be causing it, sorry. It seems to work for pretty much everyone else :-(

Ok, does it follow the FD eventually? You wrote "asap" - there is sometimes a bit of delay between the plane reacting to the commands of the FD...

Eventually we want to move to FMOD... however if your sounds are playing too quietly now, there may be something else wrong. I know that sometimes sound level settings from other aircraft carry over - so maybe doublecheck that you load up the 737 first (no other aircraft) and that all sound levels in X-Plane are really at maximum? Cheers, Jan PS: You can use the "test" button of the EGPWS to test the sounds.

Hi, I remember hearing about this problem before... but I don´t remember the solution :-/ For me the sounds are fine. Maybe you can browse to the sound folder of your IXEG installation and try to play the corresponding .wav file in Windows? Is the volume ok that way? Cheers, Jan

Hi Torbinator, yes, I can see those oscillations... The pitch oscillations are new to me - I have not seen those before...and really have no idea where they are coming from, especially if you say that they disappear in other autopilot modes. The VNAV pitch mode targets the the vertical deviation bar - and that one is not moving (at least I can´t see it in your video), so I don´t know where that input is coming from. It would be interesting to see where the stabilizer position (trim) is. It could be that it is at the limit of autopilot trim, so the autopilot keeps pushing against it? The LNAV oscillations in turn are looking similiar. We used to have a bit of those since turns are really just a segment of straight lines, we tried to dampen that out, though. I don´t recall seeing it this obvious on my end, I have to check again (sometimes one gets blind to these things!). Thanks for your report, Jan

I was never rated on the 737NG but I know there are some substantial differences between the NG and the Classic as far as the autopilot/flight-director system is concerned. Especially with regard to VNAV and but also some things like "arming" LNAV before takeoff and others... Cheers, Jan

Hmm, this sounds odd. Note that you should not use VNAV if you experience any problems with it - it does not work right in some circumstances (and never in a missed approach). Make sure that your framerate is sufficiently high (> 25fps) to avoid autopilot oscillations. Other than that you can also watch my tutorial videos on how to operate the autopilot system correctly - since you are the only one reporting these problems I am inclined to think that it must be something out of the ordinary you are doing ;-) Cheers, Jan

Ok - I don´t know why your power is "pushing back and forward" because your autothrottle is completely off. I see the flightdirector bars being completely centered - this is odd, because it looks like the plane is following its commands (the flight-director bars are actually always getting centered by the autopilot, because it flies exactly like the bars indicate). Did you "push" the ALT HOLD button? You have to be aware that the ALT HOLD command will maintain exactly the altitude at which it was pressed - not the altitude that is selected in the window. If you push it in a rapid descent (or climb) it will "go back" to that exact altitude, but it will take a second because otherwise the acceleration loads are too uncomfortable for the passengers. Cheers, Jan

I would need to see the whole panel - well, at least the EADI (with the green writing on top) to begin at guessing what you did wrong ;-) Cheers, Jan

Yes, I wish I could have told you otherwise... When Tom put up this thread in April we were trying to "take stock" of which datarefs people were still looking for. We did not know if earlier requests were still valid or maybe if people moved on to other projects. We did get almost no replies to this query, so exposing more datarefs slipped down the priority scale. I did add quite a few commands, but naturally this isn´t the same as datarefs which cockpit builders need. Cheers, Jan

The AP P/RST caution (red) light is: ixeg/733/caution/caution_ap_rst_ind But that is the only dataref I could find - I think the other ones haven´t been added yet . Sorry, Jan

I think so. Look for the IXEG/733/caution/caution_ap_... datarefs (light, pushbutton) and the /caution_at_ and the /caution_fmc_.... datarefs. There are also several commands for those buttons (look for ixeg/.../instrument_panel/... Cheers, Jan

Currently this is possible "sometimes" . In my experience the VNAV code obeys speed limits inherent in the procedure quite well, and it will probably also adhere to manual changes...but you should do them as early as possible (ideally before taking off). The current VNAV code does not react very well to changes made during the flight. A workaround would be to disengage the autothrust (turn if off completely) and use the thrust levers to manage your speed manually - VNAV would still follow the path. Naturally we hope to fix all that in the future... Cheers, Jan

Hi Splash, you are right, once the lua error screen comes up, the rest of the code is on shaky ground and may be erroneous, a reboot of Gizmo is the only way out. I am sorry that you had this error, while speed and altitude inputs in the LEGS page are not being honored by our VNAV code right now, at least they should not cause a lua error! So to save yourself the trouble and potential lua error, for now I would refrain from editing the route heavily with constraints. At best this could serve as a reminder for you, but the VNAV code will not attempt to meet your restrictions. If restrictions are read from the database, you can leave those untouched, of course. Cheers, Jan

I don´t recall what the MEL says exactly, but usually it has a modifier that says "unless it is needed for the type of flight/approach intended". So technically you can fly without CATIIIa capability, but it wouldn´t be smart to do so when going to an airport that is fogged in. I am not sure what the MEL says on the 737 Classics still flying today - but as far as I know it is not mandatory to be RNAV5 capable in Europe yet. You may not be able to fly in free route airspaces, or maybe you can and would get vectors in that case. Same goes for RNP arrivals - often there are backup procedures or ATC would offer vectors - or you simply can´t go to an airport that mandates use of those procedures. My company still flew A320s (before Covid) that had no GPS on board - they couldn´t fly RNP1 or GPS approaches, either. Cheers, Jan

Hi, yes, we always had to fly the RNAV approaches in V/S mode - VNAV mode was not certified on the 737-300. The 737NG and other more modern aircraft can fly these approaches in LNAV/VNAV - but you can also fly them in LNAV V/S or LNAV FPA (flight path angle). You have to do so, for example, if the temperature is too cold (as you would fly too low in VNAV). I know that technically the 737-300 was able to fly in VNAV as well... I tried it once in the real aircraft . In our aircraft (IXEG) it is possible, but you can not adjust the speed correctly, I think it will fly 150kts hardcoded. Cheers, Jan

No, development is not dead, it is just taking a pause because Tom is busy with something else. That is the way it has always has been, I wish we could do this full-time but this is not economically feasible. So we have to pursue other avenues of making a living that sometimes preclude us working on the 737. The plan to implement/improve VNAV, holding and a slew of other features has not changed, but as always we can´t provide an estimate or much less promise when it gets done. We are fully aware of our customers waiting for these features and will endevour to complete them as soon as we can. For VNAV and Holdings I made videos that show how to "get around" this functionality missing. https://forums.x-pilot.com/forums/topic/17872-ixeg-videos-13-and-onward/ This is not an excuse to not do them - but the real aircraft´s FMS is covered by the MEL, so you can actually fly it in regular passenger service withouth the FMC working (I have done this once in my career in the late 90s.). Cheers, Jan