I had originally posted about this in the update thread, but I decided to break it out into a separate thread.  I'm having two separate issues with v1.4.

I'm running P3D 4.5 HF3 with NGXu 2.91.0387 with FS2Crew v1.4 voice control.  My installation of v1.4 coincided with a complete reinstallation of everything fresh: simulator, NGXu, plugins, etc.  The reinstallation has at least one oddity that I'll discuss later.

First problem.  During descent checklist, FO reads back Autobrake level two as RTO.  I have a video demonstrating this issue happening.  You can see in the video that the switch is set to "2" but the FO says "RTO".

Second problem, the lower display logic is completely broken.  It now presses "SYS" and then "ENG".  This has different results depending on how your lower display is set, but it never ends up where it should be.  For the oddity I mentioned before, the NGXu LONG and NGXu SHORT states now default to the lower display being blank and the engine data being on the upper display.  Previously, these states started with engine data on the LD, but since the reinstall, it's been LD blank, engine data on UD.  When the engine start sequence is triggered, the hydraulics information appears on the LD, then the engine data disappears from the UD.  If I switch the displays so that the LD contains the engine data, the beginning of the engine start sequence will first switch to hydraulics data, and then immediately back to engine data.  In both cases, the results are identical to what happens if you press "SYS" followed by "ENG".

I do not have a video of the second issue happening, but I will get one next time.  It is 100% consistent.

Here's the promised video of the second problem.  You can see after I call the start sequence, the system page displays, followed by going back to the engine page on the LD.  It should only be pressing the "ENG" button once, but it is pressing the "SYS" button beforehand.

4 hours ago, shrike1978 said:

Here's the promised video of the second problem.  You can see after I call the start sequence, the system page displays, followed by going back to the engine page on the LD.  It should only be pressing the "ENG" button once, but it is pressing the "SYS" button beforehand.

We do that deliberately as a way to try to ensure ENG shows up in the lower display.. because we can't actually "see" the state of the lower display.

Again, we're "blind" in this one area of the plane...

1 hour ago, byork said:

We do that deliberately as a way to try to ensure ENG shows up in the lower display.. because we can't actually "see" the state of the lower display.

Again, we're "blind" in this one area of the plane...

Perhaps this is a failure of expectation on my part, but if you are trying to have ENG on the lower display, why are you pressing ENG twice after engine start and clearing it off completely?  The old way made sense to me.  ENG on upper display during engine start, then moving it to the lower display afterward.  And as I recall, that what is, or at least was, in the manual.  Now, you're starting with ENG on the LD, going through a weird hoop to keep it on the LD, and then clearing the LD once the engine is running.  Is this actually the expected behavior?  And is there a way for me to just tell it not to futz with the displays, because no matter what state I start it, it screws me up.  It either leaves me with no engine monitoring during startup, or none afterward.

What's your thought on the other issue?  The FO saying "RTO" when the switch is set to level 2.

23 minutes ago, shrike1978 said:

Perhaps this is a failure of expectation on my part, but if you are trying to have ENG on the lower display, why are you pressing ENG twice after engine start and clearing it off completely?  The old way made sense to me.  ENG on upper display during engine start, then moving it to the lower display afterward.  And as I recall, that what is, or at least was, in the manual.  Now, you're starting with ENG on the LD, going through a weird hoop to keep it on the LD, and then clearing the LD once the engine is running.  Is this actually the expected behavior?  And is there a way for me to just tell it not to futz with the displays, because no matter what state I start it, it screws me up.  It either leaves me with no engine monitoring during startup, or none afterward.

What's your thought on the other issue?  The FO saying "RTO" when the switch is set to level 2.

I can't reproduce RTO during the descent brief.  It worked fine for me.

Eng on lower display:  As mentioned, we can't make everyone happy on this one.  If I change the system back to the old way, then some people complain.

You can always manually set Engine to lower display.

 

1 hour ago, byork said:

I can't reproduce RTO during the descent brief.  It worked fine for me.

Eng on lower display:  As mentioned, we can't make everyone happy on this one.  If I change the system back to the old way, then some people complain.

You can always manually set Engine to lower display.

 

At this point, I'd just be happy to have the option to tell it not to touch the displays like we can tell it not to touch the trim wheel.  It can't screw them up if it doesn't mess with them.

The autobrake issue is 100% reproducible for me.  Happens like you see in the video every single time.  Was working fine in 1.3.

Edited August 17, 20205 yr by shrike1978

We'll add an option in a future update for setting ENG to lower display.  I think that's the best way because as I mentioned it's an area the PMDG SDK provides no control over.

I just updated the PMDG to the latest version...  however, in the Descent Checklist in Button Control the FO said "Level 3" and the switch was in Level 3.

I still can't reproduce your issue.  The autobrake is read via the PMDG SDK.

Nothing has changed in this area.