Hi all,

 

I am having an issue when mid-flight with my A333. Some 20 minutes after take off the engines will shutdown. Tanks are not empty and there are no failures. I am pretty sure I have programmed the MCDU correctly as well. The uncommanded shutdowns happen every single time I fly using the FP made with FSX's flight planner. I am not an experienced simmer so can someone please shed some light on this issue please. Many thanks,

 

Bren

Bren,

I doubt that the cause of your uncommanded shutdown is the flight planner. That said, there is one way to find out....if you can use another flight planning program and/or build the route manually (suggest going to flightaware.com and copying a route, hand enter it in the MCDU, enter the SID/STAR for the runways based on the TAF, then fly it and see what happens. If you get an inflight shutdown, it isn't the flight planner.

 

If it turns out that you are correct and it is the flight planner, then the alternative would be to use another flight planning program to build the FP, then hand enter the waypoints in the MCDU. If you don't hand enter the waypoints in the MCDU, the MCDU will go wonky on you and will not calculate your fuel burn or vertical profile with any accuracy.

 

If it is not the flight planner, then we have to start by process of elimination to determine what is causing the strange behavior. Two things come to mind: make sure you have a clean install of Wilco Airbus EVO. By clean I mean you have Airbus Vol 1 AND 2 installed first, then updated with Airbus EVO 1 and 2 installed in that order. The second thing that comes to mind is that if your computer resources are impaired by programs running in the background or (as in my case -- my CPU can't handle it any longer so I'm building a new machine that will go the next few years), try running the Airbus without any weather installed, then try different slider settings, the lower the settings, the lower the CPU resource required. If that solves it, then it is either your CPU or you have programs running in the background that are chewing up resources that FSX requires. I've had inflight shutdowns and other problems because of a tired CPU and not the program itself.

 

The last thing I will suggest is to make sure that you are running the latest version of FSUIPC, and make sure it is properly licensed. This is the key to third party applications working with FS and if this isn't right, everything else will be wrong. If after doing this you still have issues, then it could be a function of the program itself.

 

Then you go to Wilco/Feel There and get support. Their support is not the best, so be patient. It is important to undertake these steps first before you contact Wilco, because they will ask you questions about these very things before they will start looking into their own program and how it is interacting with your computer. This way, you'll have eliminated the possible reasons why you are getting a hiccup in the program so when you talk to them, you aren't spinning your wheels with them telling you to check all the things I've just suggested which will take you a while...

 

Best of luck.

Dave/speedbird034