WHAT CAN BE IMPROVED! 777 PMDG!

Поділитися
Вставка
  • Опубліковано 27 чер 2024
  • There will be many discussions about the next steps for the 777! But here is my 2 cents for an easy NORMAL flight!
    One tip for improvement and one AP misbehave that NEEDS correction!
    Hello! Welcome to LEVEL CHANGE by Claudio Fonseca!
    I'm a real pilot, currently flying the Boeing 777. Stay tunned for aviation videos.
    My Setup: • My Setup
    Instagram: / level_change_by_claudi...
    Discord: / discord
    Become a member for exclusive content: / @level_change
    If you have a specific subject, I will be more than happy to create a video to discuss it! Just let me know!
  • Ігри

КОМЕНТАРІ • 44

  • @judebrad
    @judebrad 27 днів тому +3

    Thank you for your observations. Hoping that these changes will be implimented.

    • @LEVEL_CHANGE
      @LEVEL_CHANGE  25 днів тому

      Thanks!
      Apparently the fix will be there soon! The tip for the checklist, is not coming (most probably).

  • @coriscotupi
    @coriscotupi 22 дні тому +1

    Speaking of what can be improved, the 777 V/S button does not respond to the standard FS2020 joystick bind event ("Toggle Autopilot VS Hold"). Most other standard joystick bind events do work on the 777, but V/S does not. Oddly, it does work on PMDG's own 737, as well as in many other FS2020 airplane autopilots.

    • @LEVEL_CHANGE
      @LEVEL_CHANGE  21 день тому +1

      I use SPAD.next and the related PMDG buttons instead of the in sim standard commands. Make sure to open a ticket about it if you wish them to fix it!

  • @inverterrace
    @inverterrace Місяць тому +5

    FLCH changing VNAV PTH/ALT to ALT plus speed window open is corrected for version 35 (not today's micro). Co.pletely undocumented feature. You were the one reporting this yes?

    • @LEVEL_CHANGE
      @LEVEL_CHANGE  Місяць тому +2

      Yes, it is my ticket! My PMDG ops center was showing version 32 for me! If this is corrected I make other video when I’m back from vacation! 😉

  • @BigJohnson911
    @BigJohnson911 Місяць тому +4

    please open a ticket with pmdg for all of your recommendations.

    • @LEVEL_CHANGE
      @LEVEL_CHANGE  Місяць тому +1

      Hello!
      The FLCH issue I reported on a ticket to PMDG after my first flight (even before I was able to show the airplane here on the channel). They are working on it for sure! Just wanted to show you guys… in case you have to deal with it!
      About the checklist I got I reply from staff that they cannot change … I will try to clarify in the future if this change would go against the agreement they have or not with Boeing (because they were able to replicate the mouse position on the P3D).
      If they cannot… maybe we can push Boeing a little bit to allow them this specific change (which is actually only the implementation of a real airplane button). Maybe I’m over optimistic about push a big manufacturer like Boeing, specially with something related to flight sim… but as they have a very specific license agreement… they may think this is important!
      Cheers!

  • @ech0tang0
    @ech0tang0 Місяць тому +2

    Great idea on the checklist button. I hope they can implement this feature.

    • @LEVEL_CHANGE
      @LEVEL_CHANGE  Місяць тому

      Looks like there is a license agreement issue.
      I’m not a lawyer and I also do not have access to the information in “black and white”.
      So… apparently it is not happening, but I will try to push for more details once things settle down!
      My opinion is that they wouldn’t change the checklist from Boeing, but only activate a real button on the airplane.
      Maybe if more people ask about it… they can try to solve this issue with Boeing or give us an official report saying they cannot do it.
      So… no good news for now!

  • @lactoese
    @lactoese Місяць тому +3

    They need to fix that engine pylon

    • @LEVEL_CHANGE
      @LEVEL_CHANGE  25 днів тому +1

      I see many people reporting… should be fixed soon!

  • @PauloGomese11
    @PauloGomese11 Місяць тому +2

    Valeu comandante Fonseca, obrigado pelo vídeo....abraço comando

  • @dmatthieu2
    @dmatthieu2 21 день тому

    They can create the auto checklist upon completion..C'mon as a programmer, this is easy, and its a mouse event where onclick do some action. The question is, what's the priority

    • @LEVEL_CHANGE
      @LEVEL_CHANGE  21 день тому

      Hello!
      Yes… it is possible!
      But the real airplane does not have this feature!
      Actually… it has for some items and those are simulated by PMDG. If you have your parking brake ON… when you open the Preflight Checklist, this item is already marked!
      So… it is there as the real plane!

  • @ichgacer4091
    @ichgacer4091 26 днів тому +1

    for the app is there any way that speed slow down automatically every flap setting or do i need to reduce with the knob every time i set one degree of flaps ?

    • @LEVEL_CHANGE
      @LEVEL_CHANGE  25 днів тому

      You have to set manually on the triple seven! There is no automatic speed selection for any kind of approach!

  • @yaqoobalaskari
    @yaqoobalaskari Місяць тому +5

    Hi Claudio, thank you for the good stuff you are passing to the community on B777 . I am retired Airbus pilot. My question is on North to South rout (RJTT/YSSY) if I put on the Leg page N30-10 should the FMC calculate all Latitude to the end of the route OR up to the Quater and stop (Airbus go all the way to end of the route)

    • @LEVEL_CHANGE
      @LEVEL_CHANGE  Місяць тому

      It should calculate all the way! Including points along the STAR and APP! Not sure how is modeled on this airplane so far! But by your question I can assume it is not! 🤣
      Let me know!

    • @yaqoobalaskari
      @yaqoobalaskari Місяць тому +1

      @@LEVEL_CHANGE Yes sir it is not modeled correctly on PMDG 777. Same with the Longitude FMC calculation stop at Dateline (east/west) route. Appreciate 🌹

    • @LEVEL_CHANGE
      @LEVEL_CHANGE  Місяць тому

      ​​⁠It was modeled like this for the previous simulator (Prepard3D). We can open a ticket, but I think it will take a while as they have more serious problems right now!

    • @yaqoobalaskari
      @yaqoobalaskari Місяць тому +1

      Quite agree my friend, thanks

  • @kutyafal
    @kutyafal 22 дні тому +1

    Very informative video. I have a question: why some PBD or LAT/LONG custom waypoints won't allow the entry of speed or ALT restrictions (resulting in "invalid entry")? Here is a sample flight plan where altitude restrictions can not be entered for the two custom waypoints after IMSIL: HLLT N0486F250 WLD1C WLD J615 GS M999 KHG L604 LXR M999 JDW G650 RIBAM L677 NABAN IMSIL 1533N04409E 1531N04411E SN504 OYSN
    The custom PBD waypoints above are: SAA302/5.3, SAA291/2.4
    Is there a rule that prevents this in some situations?

    • @LEVEL_CHANGE
      @LEVEL_CHANGE  22 дні тому

      Hello!
      Once the PBD or LAT/LONG waypoints are on the LEGS page you can work with the vertical profile (speed and altitude) as any other point.
      Just note that for any point:
      - Speeds only are not allowed (unless at Cruise Altitude).
      and
      - Altitudes are not allowed at Cruise altitude (unless they are defined as Step Climbs - with the appropriate S after).
      Please… tell me which constraints are you trying to input and if this is before TOC or after TOD.
      Cheers!

    • @kutyafal
      @kutyafal 22 дні тому +1

      @@LEVEL_CHANGE PBD 210/9000 for SAA302/5.3 (Sanaa VOR) which is 1533N04409E entered during cruise results in "invalid entry". Same for the other one. In some other flight plans it works fine.

    • @LEVEL_CHANGE
      @LEVEL_CHANGE  22 дні тому

      @@kutyafalare you able to confirm the waypoint names created by the system when you execute these two points?
      Looks like you know what you are doing… and the airplane is not accepting!

    • @kutyafal
      @kutyafal 22 дні тому

      @@LEVEL_CHANGE SAA01 and SAA02 are created. Before takeoff, on ground and before arrival/appr is defined restrictions can be entered. Once arrival RNAV SN500 R36 via SN502 approach is entered and disco cleared it won't allow restrictions for those below the preset 170/12800 for SN502. I suspect that is the issue. Since /12800 is preset for SN502 which follows the custom waypoints it won't allow to set a restriction below that.

    • @kutyafal
      @kutyafal 22 дні тому +1

      If no approach is defined or disco before approach is left in place then it works. So I guess that's the way around it? The VNAV calc to approach must be preventing going below VNAV path via an ALT constraint...

  • @vrotate8324
    @vrotate8324 Місяць тому +1

    Boa, comandante! Os seus conteúdos estão ajudando bastante. Uma sugestão: Um vídeo completo e técnico do FMC, explicando a ordem de preenchimento, sobre as páginas do Vnav em voo, diferenças sobre os modos LRC e ECON, PROG page em voo, como usar a page ALTN, como alternar na prática, Forecast winds e descent page (como fazer certinho), se existe possibilidade de inserção de pontos de notificação ao longo da rota, e se sim, como fazer isso em um long haul... Etc, etc. Seria um conteúdo interessante, eu particularmente estou estudando bem o 777 e estou em busca deste tipo de conteúdo um pouco mais avançado, específico do FMC, e seria muito bom aprender isso com quem já voa a aeronave. Apenas uma sugestão, abraços e obrigado pelas dicas já passadas.

    • @LEVEL_CHANGE
      @LEVEL_CHANGE  25 днів тому

      Olá!
      Já existe vídeo em português e inglês sobre a preparação completa do FMC.
      Alguns pontos que você procura em voo… como PROG, ou alternar… estão cobertos nos vídeos sobre alternados ou mesmo nas duas lives de acesso antecipado que fiz (em um eu alternei e o outro foi mudado a pista - a fim de explicar esses itens).
      Infelizmente não consigo trazer um vídeo com todos esses detalhes (a não ser que eles tenham que ser usados durante a live).
      Lembrando que eu dou mentoria particular e aulas em grupo de tempo em tempo… onde essas dúvidas podem ser sanadas.
      Um abraço

  • @mgking777
    @mgking777 Місяць тому +1

    Good to know, thanks for the video! One more question about Vnav and FLCH: I recently saw somebody in a stream, who was in a climb, and both Vnav and FLCH were illuminated on the MCP, but FLCH SPD was shown as active in the PFD and Vnav was armed. Does this work so, that you are in FLCH mode until you reach the Vnav path again and then it switches in to Vnav mode?

    • @LEVEL_CHANGE
      @LEVEL_CHANGE  Місяць тому +1

      Hello!
      No! VNAV and FLCH would cancel each other! And VNAV PATH only happens in climb for LEVEL SEGMENTS. All actual climbs on VNAV mode are in VNAV SPD.
      If you remembered the livestream link, let me know! I can check!
      Cheers!

    • @mgking777
      @mgking777 Місяць тому +1

      @@LEVEL_CHANGE ​Hi, i found the Livestream and the timestamp, but i think youtube doesn't allow me to post a link in here, or anything that looks even close to a link :D It was on twitch and the channel name is "Grizzle". It was about 3 days ago and the VOD of that Livestream is to be found under the name "Maiden 777 Flight: OMDB -> LGAV".
      Timestamp: starting at 1h 19min 45s
      His vnav seems to have never been activated after takeoff, it remained armed.

    • @LEVEL_CHANGE
      @LEVEL_CHANGE  Місяць тому +1

      You are completely right! VNAV never engaged at 400’! The thrust also remained in HOLD until ALT was captured at 5000’ (it was supposed to change to THR REF at 400’ as well).
      Don’t really know the reason for it. I did not had time to follow all the cockpit preparation he made (I’m starting a 7 day vacation today), but it looks like a system misbehave… MCP state and FMA annunciations were all correct until LNAV engagement at 50’!
      Let’s see if we see this happening in the future!
      If it happens again, at acceleration altitude (by PMDG default and Boeing training recommendations should be at 1500’) push FLCH, increase airspeed, make sure you have climb thrust and retract the flaps on schedule. I would also de-select VNAV and try to re-engage only when the flaps are up and the flight path is stable.
      Cheers!

    • @mgking777
      @mgking777 Місяць тому

      @@LEVEL_CHANGE Thanks for the answer and have a great vacation!

  • @togasimulations245
    @togasimulations245 Місяць тому +1

    Eu acho q algo que com certeza poderia ser melhorado é o Barulho dos motores na hora que aperta o TOGA. De 20% até os 55% é filé, dps começa a cagada

    • @LEVEL_CHANGE
      @LEVEL_CHANGE  Місяць тому

      Preciso prestar mais atenção!
      Mas não sei nem dizer como é na real.
      Minha preocupação na decolagem é escutar barulhos diferentes … então o motor estando mais alto, mais baixo, mais agudo, mais grave… não influencia na vida real. Aliás, o 777 pode decolar com uma potência tão diferente de um voo para o outro, que tentar achar um padrão é complicado!
      Mas vi muita gente com a mesma opaque você! Muitos tem reportado a PMDG!
      Vamos ver o que acontece!

  • @yfig7020
    @yfig7020 Місяць тому +1

    I think visually it looks real but from my recent flight next to the engine, the pmdg texture of black lines hightailing the different parts of the engine are too visible it shouldnt be like that the fact that it looks like one part from a distance, i dont understand how the team didnt notice how bad the cartoonish lines look on the engine hope they fix it.

    • @LEVEL_CHANGE
      @LEVEL_CHANGE  Місяць тому

      Hello!
      I’m pretty sure PMDG would love to receive a ticked about with some screenshots showing your point!
      They will be doing a lot of corrections on the next couple of days!
      Don’t miss the opportunity to report!

    • @yfig7020
      @yfig7020 Місяць тому +1

      @@LEVEL_CHANGE i did but they didnt respond thats why i sent it here i hope you could point it out i sent an email to them with images

  • @Robsoncwb86
    @Robsoncwb86 Місяць тому +1

    Saudações , lembro de vc GRU QTR .. forte abraço

    • @LEVEL_CHANGE
      @LEVEL_CHANGE  28 днів тому +1

      Claro Robson!
      Não está mais lá?
      Troca tudo direto por aquelas bandas… então ficamos meio perdidos!