Sekkha

Chris, could you by chance confirm that in PAX and ERF models RAAS is loading for you, too? In order to understand where the problem possibly is, could somebody maybe explain, how RAAS loading is triggered, is that any PMDG file which calls the module, or is the problem rather in the module itself?

Thank you !

I just wanted to report some little problems I am encountering regarding the Simulation and Aircraft options: 1) When line selecting any value to PANEL LTS DEFAULT LVL it is getting applied to FLOOD LTS DEFAULT LVL, and viceversa. I remember that this worked before the latest update 2) The option "AUTO SHOW VNAV CLB PAGE = NO" seems to get ignored. It will nevertheless switch to CLB page on flap rtr. This also worked before the latest update 3) "REALISTIC AP ENGAGEMENT" seems also not to work for me. This however cant be related to the latest update as I realized that just a few days ago befoe the update was released. I was hoping that the new install would clear the issue, but it remains. AP will engage it whatever flight /trim condition despite this option selcted to "YES"

Just to clarify, also here "not working" means that the module seems to not beeing loaded and thus not appearing in the PD3 Menu under Addons

Since the latest 744 update I seem to have a problem here with RAAS, which isnt working on the Freighter and BCF models, however it does on passenger and ERF models. Anybody else noticed that? I did of course completely uninstall the older version deleting all pmdg leftover folders and installed the new one then (twice now...) . RAAS is also selected as YES in options for all those models. Any glue?

Hi Cris, I dont get any false or not clearable messages on the EICAS, but I always get only "FMC" instead of "FMC MESSAGE", for example when MCP-altitude should be reset short before TOD.. Just curious, is that part of the same problem? I tried everything with default panel states and so....but cant get rid of it so far.... many thanks

hmmm....didnt solve it for me.... I still always get just "FMC" instead of "FMC MESSAGE" not a big deal of course, but strange..........

Hi all, i just noticed that there seem to be no minimum callouts if the mins are only dialled into the FO´s PFD.. Is this intentional ? Or maybe just a little overseen bug (wouldnt be surprised as probably not many people fly from the right side) best regards

It seems I am not getting any false "fmc message"- announcements any more, however my EICAS only says "FMC" now (instead of "FMC MESSAGE") when advising an message on the fmc... I deleted all custom panel states. All used panel states are based on the default ones . So something seems to be definitley wrong since the last update....

I imagined that this would be possible, however I dont know anything about LUA srcipts... that is what I am actually doing, but it would be great to have an option to deploy them gradually without having to change the view .. Thanks again everybody

Thanks Dan ! that sounds good, maybe time to buy a new controller.....mine has no extra slider...

Hi everybody, is there a way to have a key shortcut asigned for gradual extending and retracting the speedbrakes ? I couldnt find one, also not via FSUIPC.. Thanks a lot ! best regards

Had also some strange EICAS messages like the HYD... and also PILOT RESPONSE and some other oddities...But I also think it was related to having used a saved flight = an old panel state. After shutting down everything to Cold&Dark and the starting up again everything seems to be alright .... best regards

Dan, I do not doubt your best intentions, not at all And I agree with you that this procedure seems to have been designed by ...... :) But we are going in circles....I mean, there is no real need for me to learn any skills nor do I need to be encouraged to use them..... its just very easy to use other AP-modes - or even handfly, I can do that whenever I want without any problems, and its more, the vast mayority of years of my simming carreer I didnt even have VNAV and I always managed to fly my approaches with the most basic AP functions... The thing is just: Are the VNAV/LNAV functions modeled as good as it gets or is it improvable..? As I stated somewhere else I love this aircraft simulation. But there are also some things which I would love to see improved. One is LNAV (which seems to be reported already) and VNAV. And the other (I mentioned that in another thread already and I know that many of you wont agree, but thats OK) is generally speaking the pitch behaviour of the AP, which sometimes is very jerky, rocking up and down too much and to quickly (or jerkyly) on the speed-by-pitch modes...., this is a little immersion killer for me as it doesnt give the feeling of such a heavy aircraft....(But its not always happening, so I can live with it...) Its just that.......

Thanks Rudy for your comment and the link. Yes, communication is not always an easy task, especially not on forums and chats and so.... But anyway thanks to anybody envolved in this discussion ! Cheers

OK, so we could maybe conclude that for the mayority of you a VNAV misscalculation of 8000 ft due to a 180° turn in a procedure is just expectable and acceptable "dumbness of VNAV" I have certainly no problem with that at all, but I just do not agree. I think it must be possible to get that better....

Maybe I have to correct myself. KEA ist still 22NM to go on the 1. screenshot. So she did take that turn early.....maybe 10NM+ before reaching KEA...but that seems correct as it is prob the only way to get that turn right...and she is on the magenta line (what she didnt the last time)

Thanks Brian for coming back and taking your time to check that all out..Really appreciate that And I completly agree with you. But I probably didnt point out my problem clearly enough yet: I didnt start that topic to get that "YOU must fly the aircraft - lesson" because - believe me or not - I know that well. I am far from being a Pro-Pilot but around 21 years of simming left some knowledge also with me ( and I learned a lot from you guys out there over the years)...I was not surprised at all that she wouldnt make that turn before TOLSU at 266kts, but I indeed was surprised that LNAV was drawing that turn as an angle and not as a curve, and that she wouldnt start the turn before reaching that waypoint, and that overshooting it would cause the VP to jump up 2000 ft and as a consequence THR to engage (searched that in the manual but really couldnt find anything saying that THR could engage in VNAV DESCENT, but of course I didnt do a really extensive search, so maybe its somewhere) My point is that I have some indications that either something with my installation is wrong or the queen is really buggy on LNAV and VNAV. The purpose of that topic is to rule that out. The only thing which I started to doubt is if I had entered the lateral route correctly into the CDU. Therefore I asked you what exactly did I wrong there.... But to make my point a bit clearer : I got back to LGAV and flew the approach onto ILS Z 21R via the ABLON 1B arrival and IAF KEA again. Without doing any modifications to the FMC-route data the result was the following (sorry, by mistake I chose the wrong popup CDU with the progress page instead of the legs page for the screenshot, but as I said, I didnt modify the FMC-filed route at all) approaching KEA a few seconds later VP jumped down nearly 8000 ft (!!) . And this time she was getting the turn perfectly even with high speed and she didnt start the turn too early as she did the first time I tried the approach I personally find a misscalculation of 2000 ft (by the way, did that happen on your attempt also Brian? Would be interesting to know..) already excessive even allowing the VNAV to be dumb. But 8000 ft ????? I dont know you, but for me that seems to be a clear malfunction. So I will probably submit a ticket if after the announced updated and clean reinstall that behaviour persists....... I never had such issues while on P3DV3, and I made dozens and dozens of flights there with the queen

I always have them at IDLE during descent. But the problem was THR mode. Speed build up until I touched the throttles slightly to get it back to IDLE

Thanks Simon !

and I forgot: Any idea why AT switched to THR ? Is that normal ? I mean on my first attempt when I was surprised by that situation speed was going up quickly on THR until I took back the throttles to idle (not reflected on the screenshots as they were taken on my second atttempt).... Why does LNAV draw that turn before TOLSU like an 90° angle and not like a curve?

Thanks Chris, I completely understand that. But what I dont understand is why the FMC is giving me that vertical profile. Did I wrongly select the route on the CDU? I ask that mainly because as I stated before, the other day I came into LGAV via KEA and LNAV took a turn way before the drawn magenta line and the suddenly the VP jumped to 8000 ft (!!) below the aircraft. So obviously VNAV started that decent way too late (which is kind of similar to that case her, although more logic because the VP jumped down, here at LEMG it jumped up! why that?). But I beliefe I did enter the route correctly. I never had such issues with the Queen before the update to P3DV4...I wil try to make that approach again and take some shots. So I just have the feeling that I am having a systematic issue with VNAV calculations ......

maybe I should rename the topic to "strange behaviour of simmers on forums"...but honestly I also understand it a little bit. It must be hard for the Pros to have to share the virtual skys with such unknowing armchair pilots like me.I keep fingers crossed that not one day there will be a virtual-sky-police to take away my permission to fly around there...or worse, that PMDG or other devs come up with a mandatory checkride prior to be able to purchase their products.... But again jokes aside: Is there anybody else who would be so friendly to explain to me what I did wrong as I still dont understand it (without trying to make me pass an exam please!) And I would be highly interested in the following as well: -Why did Copper ask me data of both IAFs, when only TOLSU seems to be part of the procedure? Why should OMIGO be reflected in the CDU as he suggests ? -Where can I see the IAF speed limit for TOLSU? Why would the FMC not automatically use that speed limit if it is coded in the database? - What does he mean with "firming up the altitude/s" which he says I should learn but is not willing to explain THANKS A LOT IN ADVANCE !

yes, of course, that is what I meant, 1702, sorry for the mistake. The only thing I can say is that I got those charts from Navigraph while 1702 was current. So I have to assume is was the current chart at that time or Navigraph didnt update it.

Captain, you are really giving me a hard time.. I am not sure if am prepared enough for a checkride with you. And maths never have been my strength (that might be one reason why I am sitting here in front of a virtual cockpit on a monitor, in an armchair, in underwear and eating icecream...instead of wearing uniform with some stripes on the shoulders and being obligated to pass checkrides from time to time) But seriously: If you want to be helpful (what I suppose is your intention and what I really appreciate) please be so kind and just answer my following questions, because I really dont get your point (for example: why are you asking me the name of the second IAF if you can clearly see that I choseTOLSU ? etc....) You can find my complete route setup in the screenshot sequence and the charts I used below: (AIRAC 0217, also in the FMC) 1) What exactly did I wrong on setting up the route ? 2) Is it expected behaviour that FMC is filing that faulty route data (as you suppose) if I choose ILS Z 12 approach, PIMOS 1DCQ Arrival and TOLSU transition on the CDU? Or is there maybe something wrong with the database or the fmc-calculations (at least on my PC)? 3) Is approaching a fix with high speed (which 266 Kt obviously is for that segment) and then being unable to get the 90° turn right with the Vp jumping up 2000 ft the reason for the AT to change to THR-Mode while on VNAV descent ? Why not SPD Mode ? 4)Why did the vertical path jump up 2000 feet suddenly ? 5) Why did the AP not try to recover the rising VP by appliying thust in SPD-Mode instead of staying at IDLE/HOLD during 2 minutes afterwards thanks a lot for your help