viperlid

Thank you! ticket submitted.

I noticed that in both 747s 400 and -8, the fuel flow decreases all the way to 0.6 on each engine even when N1 is at max. Approach, somewhere between 2.5 and 3.0. Fare, idle decreases to 0.8 to 1.0. Touchdown, full reverse, fuel flow goes to 0.6. I'm sorry but this is not normal. Any chance to look into this? Thanks Alfredo Hernandez

Evening gents Im experiencing this exact issue in the 747-8F as im writing this. anyone else had experienced this in the -8 version? regards Alfredo Hernandez

why there isnt any -8F previews?? isnt the freighter in the expansion pack?

hum, weird, i didn't say that.. on the contrary, im on your side on this.

ever thought CLX cargolux flights??

mine crashed P3D when clicked DEP ARR button.

solved. Only way I could solve this issue was to download the unique manual file from navigraph and install it directly without the use of the navigraph manager. FMC is now showing current airac.

i pointed the installation manually to where you said, (my user of course), still nothing.. FMC shows airac 1709

First of... load the maddog directly from the begining. Do not load a default plane then choosing MD. if you keep loading default plane first, bad things are prone to happen. are you saving your flight planing BEFORE loading it into the Maddog at p3d???? saving meaning clicking either in the GREEN arrow or the circling WHITE arrows.

I second this post ALL external non avsim links are dead. any fix or alternate link ? thanks!

I have this same problem... KevinMM could you elaborate your answer? yet my FMC shows cycle 1709 thanks in advance

evening gents I dont know if its possible, but my Maddog is crashing my P3Dv4.2 , so far, exclusively in orbx's KSAN, with ALASKA airlines livery from GLC textures. I did a flight from Seattle to San Diego and got 3 CTDs while approaching. I mean, crash, auto save recovery, crash again and so on until I landed. Today I loaded the maddog into San Diego again with Alaska livery and crashed within 3 minutes without touching anything! Relaunched P3D and loaded default AA livery, and its been going about 20 minutes without touching anything and is still running at the moment. I havent tried other airports but, my flight went perfectly fine up until apporaching KSAN, other liveries seem not to be affected in the area. Sounds weird right?

I had this problem too in P3Dv4.2. Problem was that I was loading F22 into the sim and then selecting the MD. Solution for me: load the MD DIRECTLY from the menu where you select airport time season wx etc etc. Then click Fly. Cold & dark state. everything should be normal worked out for me!

I agree, but that doesnt justify the CTD anyway.

ok.... I finished my test flight, no minimizing 4:40 flight. no CTD soo,... yeah, minimizing is the problem

Noup, ive tried the same with pmdg 744 only and never had any problems. since T7 and 744 are the only ones i use for long haul. for short hops I use NGX and FSL320 and with those i minimize the sim without problems. of course very few flights are longer that 3 hours. I rarely use default aircraft, and certainly not for 3 hours.

Hello all Somehow P3D v4.1 is crashing when minimized and 3 hours into the flight with B777. Ive tried two different flights. BIKF-KSEA and KSEA RCTP. SEA TPE being native addon scenery. the first flight was succesfully recovered with fsuipc autosave feature. I did not minimized P3D for the remaining 4:30 hours and I was able to complete the flight. Second flight happened again exactly 3 hours into the flight, again the sim was minimized. This is strange because I do minimize the sim with 744 long hauls and everything goes perfectly fine. why do I minimize the sim? because the GPU eases down and core temperature drops, also the fan slows down making less noise. Any one experienced this before? also,anyone does minimize the sim??? thank you! Alfredo Hernandez

The normal procedure to disengage the autopilot in both aircraft is by pressing the disengage button ON the control column. you can map that button trough the FMC options. in the 747 you RIGHT CLICK the screw just above the FD switch. If your vnav disappears then something on your lateral revision is causing a reversion. check your FMC legs page to ensure everything is ok. on climb the FMA should read VNAV SPD

This is also not the correct way. if the 737 engages in ALT HOLD when reaching cruise altitude set in FMC, this means that your climb was performed outside vnav. the 737 should also read VNAV PATH when reaching cruise altitude. Make sure you have engaged vnav on the MCP panel.

thats odd.. I remove it in a daily basis without trouble

now you have to uninstall KB4041676 it should work

We are all wondering the same thing..... it is has not been released, and there is no release date in the foreseeable future. sorry :(

v/s is as good as the other to modes. Difference is that V/S disregards speed.. you have to be very careful not to exceed Vmo/mmo or VFE. in many cases if you are high on your descend profile, is better to slow down and configure than using speed to maintain a high rate of descend. Even is this gets you even higher on your profile. Remeber, the number one enemy for being high on your approach is speed, not altitude.

guys I believe for now the ONLY solution is to remove KB4038788. Ive been flying 747 for the last 10 days or so this way and it worked every single time. I dont care if windows stays behind on its updates, as long as my plane works. But sure this has to be definetly fixed in some manner