Jump to content

Wise87

Member
  • Posts

    20
  • Joined

  • Last visited

Posts posted by Wise87

  1. I think I see where my user error was with the MCDU but you you are correct, even if I enter the incorrect information into the MCDU, it should say NOT ALLOWED and not crash the MCDU. I'm use to other FMC/MCDU to where I simply enter a speed/altitude and just select the RIGHT LSK next to that point. My error on the A310 was entering 250/130 and hitting the RIGHT LSK and when the direct entry didn't work I selected the LEFT LSK next to ONDRE when I should have hit the RIGHT LSK first. I'm glad this will be addressed in a future update. 

    • Like 1
  2. Sure, I can duplicate it each time. I was flying from KDTW to KATL in the Delta A310. I was about to start my arrival into Atlanta on the ONDRE1.HAINZ arrival. I was programing the MCDU to cross ONDRE at 250/130. Being a FMC guy I used the RIGHT LSK on ONDRE to ENTER 250/130 but nothing changed. Then I used the LEFT LSK on ONDRE and the next window open. I see VIA GOTO [   ]/[       ]. I enter 250/130 in the keypad and select the LSK. Noting populated in the [   ]/[       ] window and this is when everything stops working. I can repeat this every time. I did it two more times just to confirm but I did not take off from KDTW. I simply loaded the plane ready for takeoff, imported my flight plan, added my SID and STAR and then went directly to ONDRE to add my crossing restriction  as if I was in flight. As soon as I did all the buttons stopped working. The flight controls still worked but the instruments were reading funny and buttons stopped responding. When this happens in flight and I push the yoke down to descend, again only the flight controls work, the long needle will move but the small needle on the altitude guage stays frozen. Hope this helps. 

  3. 4 minutes ago, Sam said:

    Hello all,

    Please could you log out of the iniManager, and log back in and let us know if this resolves the issue.

    Many thanks.

    Doesn't work. I even reinstalled the iniManager earlier just incase it was that. I made sure the iniManager folder was also removed before the reinstall.

  4. 1 minute ago, lowpolybutt said:

    Could you share a screenshot of your iniManager path settings?

    The path were it is installed?

    "C:\Users\Dan M\AppData\Local\iniManager\iniManager.exe"

    My MSFS2020 directory in the manager is correct.

    D:\MSFS2020\Community\

    Nothing has changed when I installed KLAX on release day. 

     

  5. Myself and others have been doing flights between LAX and SFO all day and no one has reported your issue. Have you checked your content manager and verified KSFO is installed? You could reinstall it or check for scenery conflicts with a third party add on. Only Asobo LAX was required to be removed. 

  6. 1 hour ago, Sam said:

    Hello,

    We're looking into this now. The actual files available through the manager are v1.03, however, it just seems the version number is stuck.

    If you uninstall and reinstall the scenery, you'll download v1.03.

    Thanks, that worked for me for the time being. The manager still shows 1.02 but I verified the manifest.json as 1.03.

×
×
  • Create New...