Litjan

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!

Try a (hard) landing and see

@berilojr If you want to, post your vrconfig.txt here for now so people can use it in the interim until we can get the fixed version in. Thanks for your help!

Thanks for the tip - I think the goal is to have this working without the restart, but as with all things "computer" - a restart often miraculously helps (I flew Airbus for a while )

Use the command "Autopilot take-off go-around".

Thanks for the feedback and nice words!

I would debate "normally". They were an option but my impression is that they were the exception, rather than the rule.

Thanks for the feedback, everyone. Reading all posts, taking notes!

If you get stuttering when you modify the route in the FMS, make sure to exclude the X-Plane folder from Windows Defender live virus checking.

Check sound device settings for Windows AND also for X-Plane (sound menu). Restart computer also sometimes helps.

Hi @judeb, I think what is probably happening (I just tested this) is that the autopilot stay on when you override the modes (the green CMD still shows) but you revert to CWS (control wheel steering) modes (shown in yellow). You can´t disengage the autopilot by moving the joystick, it will only fall back to CWS and the autopilot warning light flashes (but no warble).

Hi @blondejfx I just tested this and for me the trim does not start to run if I ONLY use the Flight Directors.

I have had reports of the VRconfig file missing, I will doublecheck and fix if I can verify that!