Nuckingfutz

It's like Bryan says, all in kgs. Based on the flight route, weights, FL, wind predections etc, the plane thinks (at departure), that there will be (e.g.) 5200 kgs of fuel left at destination. As the flight progresses, the plain recalculates a lesser value. It might be that Active Sky uses other wind data then PFPX (in of 10 cases). PFPX provides the wind aloft data for the fuel prediction during flight (only once, at departure if I am not mistaken). Active Sky provides the actual winds that are encountered during flight. In theory they should be identical, but perhaps this is a clue for this mysterious fuel disappearance. Question of course is, if potential differences in wind can explain this excessive fuel consumption. The fact that the issue is happening only 1 in 10, seems to indicated that Bryan is doing nothing wrong. Otherwise, the issue would appear 10 out of 10.

Hi Erich, Vatsim is great fun. Objective is to perform everything according to real procedures. Mostly serious pilots because anyone who is trolling will draw the attention of a supervisor and will be kicked off. To make it a great experience: know how to fly your airplane go observing some ATC for a while to get the hang of it (park your plane at a remote apron and dial into the ATC-frequencies) study the procedures and lingo of ATC have fun. In your first couple of flights, place the remark "Newbie" or something like that. Most controllers will have patience. Use valid flight plans (e.g. vat route.net) Don't do your first flight during an event See you in the skies. Alex

Saitek x52 pro, but changing to saitek pro flight yoke and rudder pedals in a couple of weeks

I think you mean that the liveries are gone? I installed the sp1 for the 200LR/F and had the same thing. Remedy: I closed FSX, restarted the operations center, selected the 200LR/F. It indicated by itself that liveries were missing and it asked if it should be repaired. After clicking yes, all liveries were again available in FSX. Kind regards Alex

The ease of use is great and also the model matching logic. However, every flight I get a Hresult 0xC000014B error every 20-30 minutes or so. Yesterday I did a 7 hour flight, starting with vPilot. I removed the IVAO C150 model, because there are some posts saying that this model has errors. However, after 20-30 minutes, Hresult error. In the windows logging there is no clue as to which module is causing this (' unknown'). The remaining 6,5 hours of the flight I used FsInn without any problems. Using the PMDG777, ASN, Aivlasoft, PFPX, all legal. So, for me it is FsInn, unless somebody can deliver the remedy :-) Alex

Whats really bugging me is the sound when a text message arrives which is not for me. Not possible to turn it off.

Hi, if you have entered the fuel load, pax load, cargo weight and have followed the correct flow for programming the FMC, then the FMC will give you an optimal height from a technical / economical perspective. As said before by others in this topic, you can also look at real world routes. Even though the technical optimum is for example FL300, the route prescribes a max of FL200 (e.g.) Also, you should also take into consideration that eastbound you need odd levels (FL330, FL350 etc), westbound you need even levels (FL340, FL360). The FMC will give you a warning if you enter a too high FL, but does not take into consideration East/West. Furthermore, as far as I know there are no FL-maximums on Vatsim. If there is a max, it definitely cannot be reached by the NGX. Kind regards Alex

Thanks LowwLugim, that seems indeed to be the problem. I tried making cold and dark the default load state, ended the flight, started again (thus loading automatically the Cold and Dark state). Started battery, APU and the fun begins. Within 1 or 2 minutes. However, strange that if you load a panel state after another, that it remembers some settings from the previous state. Kind regards Alex

Same problem here, loading the cold and dark default panel state. Turning on battery. Starting APU by holding the switch until it pops back. Nothing happens. Sometimes APU inlet opens, sometimes not. But no power. Waited also for 5+ minutes. Regards Alex