Jump to content
Sign in to follow this  
dracer33

Possible post SP1 bug

Recommended Posts

Straight%20Face.gif what a perplexing situation. Well thanks for your help Leffe. Oh and yes if I manually press the LNAV button after takeoff it will stay lighted, it's just the after takeoff procedue that is giving me the trouble.Devin Mack

Share this post


Link to post
Share on other sites

Same problem happends over there, actually I disappointed from all those Flight-Sim payware addons.I have also expected gauges FREEZE in VC, seems like PMDG saving money to perform good QA.I work in software development Industry and I know exactly how those parts are working.It is disappointing to see how they brawely release SP1 with many bugs, and everybody says they're genious, maybe they just the best of worse but not more.I'm not familiar with real aircraft systems, but details of PMDG are really impressing, the only problem is a quality and bugs.

Share this post


Link to post
Share on other sites
Straight%20Face.gif what a perplexing situation. Well thanks for your help Leffe. Oh and yes if I manually press the LNAV button after takeoff it will stay lighted, it's just the after takeoff procedue that is giving me the trouble.Devin Mack
looks like a weird situation.first thing i wanted to suggest is to change the PFD display layout but you've already tried that.1.What happens if you set the autobrakes OFF (currently still RTO) and the landing gear the the OFF position?2.You're taking off with FLAPS 1 and when airborne they are 5 or do i misinterpret the screenshots?3.Are you able to reproduce this issue when using another route/SID ?

Antoine v Heck
---
Ryzen 5800X3D, 32Gb DDR4 RAM@1600 Mhz, RTX3090 (24GB VRAM). 2TB SSD - VR with Quest 2 via link cable 

Share this post


Link to post
Share on other sites

At least from what I know, only LNAV is armed on gnd.VNAV suppose to be engadged passing 400 AGL and it will be armed passing 400 AGL only.And light bolbs can be burned, FMA is the only place to look for what the AC is doingand his mode.

Share this post


Link to post
Share on other sites
And light bolbs can be burned
Not the issue here as he clearly states he can press it to come alive manually,The issue is why it doesn't appear lit automatically like the VNAV button

Antoine v Heck
---
Ryzen 5800X3D, 32Gb DDR4 RAM@1600 Mhz, RTX3090 (24GB VRAM). 2TB SSD - VR with Quest 2 via link cable 

Share this post


Link to post
Share on other sites
Not the issue here as he clearly states he can press it to come alive manually,The issue is why it doesn't appear lit automatically like the VNAV button
Didn't say this is the issue. Just said that when you fly, MCP lights are not where you should look tosee which mode is on.FMA is the place.

Share this post


Link to post
Share on other sites

Have the same problem - thought it was me but perhaps not.To add to the above.1. Pre - TO. Select LNAV on MCP - it arms {white on FMA}2. Post TO. LNAV engages correctly {green on FMA} but LNAV light on MCP extinguishes.3. Climb/Cruise. LNAV remains engaged {green on FMA} and follows correct route - LNAV MCP light remains out4. At any stage - press LNAV on MCP: LNAV disengages and AP reverts to CWSR5. Press LNAV again and LNAV re-engages and reverts to normal operation.As with the OP could not find this in FCOM or tuuorial so perhaps some of our experts could advise as they do not see it- is it something in my NGX set up?John Rooum

Share this post


Link to post
Share on other sites
looks like a weird situation.first thing i wanted to suggest is to change the PFD display layout but you've already tried that.1.What happens if you set the autobrakes OFF (currently still RTO) and the landing gear the the OFF position?2.You're taking off with FLAPS 1 and when airborne they are 5 or do i misinterpret the screenshots?3.Are you able to reproduce this issue when using another route/SID ?
Thanks for your ideas Antoine, sadly I tried them all and the event still occurs regardless of my takeoff config, local, or SID. Oh and the flaps had been different in the screen shot because in the original ones I took while on the ground with flaps 1 I had forget to take a screenshot in the air so I restarted the flight and changed the weights a little to set flap 5, either way the issue still persists. Doh.gif
Have the same problem - thought it was me but perhaps not.To add to the above.1. Pre - TO. Select LNAV on MCP - it arms {white on FMA}2. Post TO. LNAV engages correctly {green on FMA} but LNAV light on MCP extinguishes.3. Climb/Cruise. LNAV remains engaged {green on FMA} and follows correct route - LNAV MCP light remains out4. At any stage - press LNAV on MCP: LNAV disengages and AP reverts to CWSR5. Press LNAV again and LNAV re-engages and reverts to normal operation.As with the OP could not find this in FCOM or tuuorial so perhaps some of our experts could advise as they do not see it- is it something in my NGX set up?John Rooum
John it's comforting to know that someone else is having this issue as well, I just wish we could get someone from the PMDG team to give their take on it though.Devin Mack

Share this post


Link to post
Share on other sites

Same problem here (since SP1). LNAV mode _is_ active, but not lit. Switching LNAV off and on again during flight usually brings it back.Regards,Jörn

Share this post


Link to post
Share on other sites

I have the same problem, I noticed, thought it didn't bother me much, that if I engaged both VNAV and LNAV on the ground, that sometimes after I press TOGA, LNAV would extinguish.I would usually repress the button after takeoff, before I engage AP, but that would sometimes disengage VNAV (as I remember!). In the end, a click here and there would solve the "situation".But: sometimes it all went normal, 2 are on, two are kept on, and I only press AP.The situation I was testing was a saved flight from EGKK to LOWI, always the same config, and I always take care that I have right configuration on takeoff, along with correct trim and following the FD anyway possible, usually between 15 and 20 degree up. With the exactly same procedure, sometimes it happens and sometimes not. Maybe I am missing something, but I think not.

Share this post


Link to post
Share on other sites
Have the same problem - thought it was me but perhaps not.To add to the above.1. Pre - TO. Select LNAV on MCP - it arms {white on FMA}2. Post TO. LNAV engages correctly {green on FMA} but LNAV light on MCP extinguishes.3. Climb/Cruise. LNAV remains engaged {green on FMA} and follows correct route - LNAV MCP light remains out4. At any stage - press LNAV on MCP: LNAV disengages and AP reverts to CWSR5. Press LNAV again and LNAV re-engages and reverts to normal operation.As with the OP could not find this in FCOM or tuuorial so perhaps some of our experts could advise as they do not see it- is it something in my NGX set up?John Rooum
This is identical to the behaviour of mine as well!

Andrew Dixon
"If common sense was compulsory everyone would have it but I am afraid this is not the case"
 

Share this post


Link to post
Share on other sites

Just for the statistics: +1. Lnav light extinguishes but lnav keeps engaged.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

  • Tom Allensworth,
    Founder of AVSIM Online


  • Flight Simulation's Premier Resource!

    AVSIM is a free service to the flight simulation community. AVSIM is staffed completely by volunteers and all funds donated to AVSIM go directly back to supporting the community. Your donation here helps to pay our bandwidth costs, emergency funding, and other general costs that crop up from time to time. Thank you for your support!

    Click here for more information and to see all donations year to date.
×
×
  • Create New...