Litjan

I am using the standard "50%" settings and that seems to work good for me.

I remember them being very dim at nights...but I will see if we can bump them up a bit.

Interesting... I will forward this to @tkyler he is the one that can see the Matrix read the xml database and will be able to see what the problem is. Thanks for bringing this up! I have already adjusted our starter strength to reach ca. 22%N2 on a hot day at Benito Juarez

Yes, this is due to new physics in X-Plane 12 - they are representing real world effects, but are probably a bit too strong in the case of our 737. Austin models the downwash of the wings making the air go "down" behind the wings - and if the horizontal stabilizer is in this downwash, it gets more effect (pushes tail down). So if the plane lifts the nose, the tail moves close to the ground into an area where the air can not "flow down" anymore (because the ground is in the way). It looses effectiveness and the pilot has to "pull more" to make the nose keep going up. Once the plane is out of the ground effect climbing, this effect gets re-established and you can "relax" the pull a bit. The real 737 has the same effect: You initiate rotation fairly easily, then the plane "stops" rotating when you reach about 10 degrees and you have to pull MORE to keep the nose going up (recommended is 3 deg per second rotation rate). Once the plane is lifted off and climbs out, you can relax this extra pull. Its almost as if there was a "resistance" to the nose moving up around 10 degrees pitch. It works the same on landing, the closer you get to the ground, the more you have to "pull" to keep your nose from dropping. This is more pronounced now in XP12 and one has to adjust the technique: When passing 50 feet, make sure to keep nose up at the same pitch! When passing 30 feet, pull nose up by 3 degrees and HOLD IT THERE. At 20 feet, pull power back to idle.

Yup, all known. Thanks for the report!

I am not sure, but I think it does not depend on if you upgraded or bought new. It seems to depend on other things like plugins installed and/or internet connectivity settings.

I have updated some stickied posts here on the main page, namely the FAQ post (with a link to the "known bugs" post) and the "what will not be in V1.5" post.

Yes, I know that the N2 is not sufficient at Mexico City - I misunderstood you and thought you also reported too little N2 at sea level. For the VOR interception I flew towards the radial with HDG SEL and VOR/LOC armed. When VOR captured (HDG green turns to VOR green) the plane banked to intercept the set radial. Is this not happening for you? If you look at the approach chart for Merida that you posted you can see that all these different approach transitions have IAF´s that are ALL called "DXX.0 MID". There are some with D17.0, some with D12.0 and some with D10.0 - that is why our FMS thinks that there are three different ILS approaches available, I bet. Separating approach transitions requires them to have unique names, if there are several that all start at "D12.0 MID" then our code can´t distinguish them.

Hi everyone! Thanks for everyone´s support and feedback for our initial launch of the IXEG 737 in XP12. This post will detail the bugs that were reported and confirmed by us. This post will be updated regularly and shall serve as a tool to check if something you observe has already been reported. Activation issues with the DRM that revolve around the "Level 2 check" failing - fixed Wiper switches not working - fixed for next patch Standby airspeed indicator drum not moving - fixed for next patch Bullseye windows on doors 3L and 3R too far outboard - fixed for next patch VRconfig.txt file missing - fixed for next patch Starter not strong enough at high density altitudes - fixed for next patch Engine start process going too fast - improved (total duration matches) but fix in LR´s court Wing illumination light not working - fixed for next patch Visual texture glitch on underside of left wing - fixed for next patch Taxi light a bit too dim MCP backlighting a bit too dim Window heat OFF logic reversed for right side windows - fixed for next patch No turnoff light for right side - fixed for next patch INVALID ENTRY message when trying to manually enter a V1 on TAKEOFF REF page - fixed for next patch Pitch up moment change during liftoff and landing too strong - fixed for next patch Idle fuel flow too low - fixed for next patch No CDU backlit keys - fixed for next patch. FMC / Gizmo crash when executing VNAV calc with only one waypoint in LEGS - fixed for next patch. ECAM gauge needles not lit up at night - fixed for next patch. Added four commands to command the fuel lever to idle/cutoff. For hardware binding to buttons/switches. Linked to default XP commands to connect/disconnect/toggle the GPU. Helpful for VR users. Cockpit door default to pen in the Turn-around mode Cockpit door occludes front galley lighting at night when closed. Fuel Crossfeed annunciator dimmer (less bright) when crossfeed valve open. Was too bright. - fixed for next patch.

This is a new feature to improve airflow in the cabin on flights where they serve beans or peas!

X-Aviation is working to fix this problem!

That is unfortunately correct

Some of these are already known and some will/may be implemented in the future. Some of your observations I can not confirm (LSKs, Econ Index, FMC background light (there is none))

Yes, there are several folks with a "Level 2 DRM check fail" in the log.txt in the X-Plane main folder. Can you confirm this is also the case here?

This is what the FMC defaults to. The pilot has to enter the correct values. You can see the actual trim setting in %MAC in the default X-Plane weight and balance gui. Set this value into the FMC and then set the resulting value on the trim wheel prior to takeoff.

@Vanadeo The taxi lights and turnoff lights in the real aircraft are just as dim. They are not meant to illuminate the taxiway, they are for spotting obstacles and mostly for people seeing you taxi. The cabin light spilling into the cockpit is a known problem and a side-effect of us using dynamic ("real") lights. It is a limination of X-Plane´s engine, most objects do not cast shadows or block dynamic light, unfortunately. One workaround is to dim the light in the cabin during night flying. We are looking into ways to make the lights go "out" if the camera is inside the cockpit. Which backlight do you feel too weak? Landings feel a bit different in XP12, you need to concentrate on not letting the nose drop as you approach the runway, raise it by ca. 3 degrees as you go through 30 feet and leave power on a second longer.

Ther is no green light in this version of the aircraft, it is modeled after the version´s I flew when I was an FO and later CPT on the 737-300, they only had amber OFF and amber OVHT lights.

Thanks for the nice words! As Tom said, we are not done "tuning" the flightmodel and I know that the plane feels a tad different from XP11. I sense that it reacts to the controls a bit more "briskly", but I tried reducing control authority but then found it lacking in some extreme cases (slow flight, forward CG, etc). So it may be a matter of tuning deflection times. The effect at lift-off is realistic, though. The real plane will pitch up readily at Vr, then hesitate notable at around 10 degrees and you have to "learn" to give it more elevator input at around 9 degree to keep the rotation rate smooth, then relax it as you near the normal pitch attitude after liftoff (15-20 deg). There is a bit of a "nose down" effect in X-Plane as you get close to the ground, it is a realistic effect, but maybe a tad too strong for a 737...it is a function of the plane´s geometry and we have no influence over it. The reason is the stabilizer being in the downwash of the wings during normal flight, but near the ground this downwash is stopped by the ground, so the stabilizer has less "nose up" effect (relative wind not coming from "slightly above" anymore).

Can you check if you maybe have another plugin interfering with this? I have not seen this behavior yet. Thanks!

Tried the VOR intercept and it worked fine for me - can you give me some repro steps on that, too, please? (you DID remember to set the course on the MCP, right? I think the NG will do this automatically, Classics won´t and once in a while you will have to buy a beer for your colleague when the plane does the wrong turn on the ILS intercept because you forgot )

Especially embarassing if you are standing in the way with 5 other guys waiting for pushback and you can´t taxi out yet because you have to do an ELAC reset

@CptIceman Hmm, I just tried an engine spool up at sea level and I am getting 24.8% N2 even at +25C. See attached pic. Also tried the "idle taxi" you reported and the plane will break free readily at 22% idle N1 and pick up speed briskly with a weight of 50t (110k lbs). I am wondering if you maybe have some sort of plugin that interferes with our IXEG? I also could not easily reproduce the lua error you got for the "erazing of approach", could you give me some further steps that helps me reproduce it? Trying VOR interception next...

Thanks for those two reports - especially the lua error is a super high priority fix! Keep `em coming!

Hi, first - lets try to stick with english here, so we can all understand each other. Second, thanks for your observations!