Report Bugs Here

[Matthew King]

Welcome to FSX, remro88!

In order to get FSFO, and A LOT of other FSX/FS2004 related programs, you need to download and install Peter Dawson FSUIPC. The program comes in two varieties, both freeware and payware. You only need the freeware version. Feel free to email me if you have any questions...

www.schiratti.com/dowson.html

[mamush]

Greetings i'm new here,how can i add pmdg 777 200 and 300 to the checklist,it's not there.

Mamush

[Matthew King]

Hi mamush,

I don't own that airplane; so, I didn't include that checklist. However, you can create your own; checkout page 31 of the manual. If you do create one, could you post it here?

[ronnieb]

Hi Matthew,

Thank you for your gift to our community. I have been using FSFO for about a year and a half and find it to be a great product.  Everything was working great until six months ago, then I took a break from FS and since returning, I've had an ongoing issue.  My system is FSX (SP2) with the freeware version of FSUIPC running on Windows7 64b.

My problem concerns the automatic features.  Taxi and Before Takeoff checklists execute automatically and work flawlessly.  When I take off, I know at 1000' AGL whether or not I have a problem.  If the copilot calls, "Climb Power," then every automatic feature will work throughout the flight.  If there is no call, then the following anomalies occur:

1.  Flaps retract on schedule but no CP callouts until, "Clean speed, flaps zero."

2.  The After Takeoff checklist will not be recited.

3.  The copilot does not tell me to turn off the landing and taxi lights passing 10,000 feet.

4.  At FL 180, the copilot does not call "Transition Altitude" and does not reset the altimeter.

5.  Descending through FL 180 gets no copilot callout and I'm not told to turn on my lights at 10,000 feet.

6.  On approach, the flaps are not extended and the Approach checklist is not initiated.

7.  The After landing checklist is not triggered as I slow down.

This seems to happen with all planes but the default A321 is the worst; almost always.  I thought perhaps it was unique to version 2.3, so I reloaded an old version (2.0 or 2.1) and it was the same.  It must be something that I'm doing but I can't find my error.  I hope that I explained this well enough.

Thank you for your attention and thanks again for this excellent program.

R-

[Matthew King]

R.

I'm on the road this week; however, I'll look at the code and get back with you on Friday. From your awesome description it appears the main thread maybe caught in a loop. Yet it was working fine for you for over s year. Can you try to delete your user profile and recreate?

[ronnieb]

I deleted the user.cfg file and made a new one but nothing changed.  I may have another helpful bit of info but it is weird.

The problem seems to happen most often at two airports: 89TE and MNMR (MN0B in FS9).  That makes no sense to me but perhaps it is something.  both of these airports feature one paved runway with no taxiways or buildings.  I start a flight parked in the grass, beside the runway, about midfield and backtaxi to the takeoff end of the runway.  All checklist have performed on schedule during startup and taxi and the Before Takeoff checklist executes as I near the end.  At that point, I must pull off, into the grass, to turn around.  During the takeoff roll, the V-speeds callouts always execute but once I leave the ground things go awry.

I believe that some flights from 89TE work okay but I can't remember a successful flight from MNMR. Thinking the problem might be caused by taxiing on the grass, I started flights at other small airstrips but those were successful.

It has occurred to me that some background might help.  I do most of my simming while using FSEconomy.  In the game, I own FBOs at 89TE and MNMR.  The problem surfaced, when FSEconomy started directing A321 flights into and out of these two airports.  To facilitate these larger planes, I had custom scenery designed for these airports: buildings, parking ramps, and ILS -- no taxiways because the real-world counterparts don't have them.

As part of my troubleshooting, I removed the new scenery *.bgl file from the Addon Scenery folder.  It makes no difference with or without this scenery.

I hope this is helpful to you.  If I'm the only person experiencing this bit of weirdness, then please don't spend too much effort on it.  I get along fine executing the checklists manually.  Thanks for you work.

R-

[Matthew King]

R, I think I have a workaround for you; it's kind of an emergency catch to ensure the automated checklists get called. I'll include it in 2.4

[ronnieb]

Thank you again for your attention to my problem. I added a post to the "Feature request" thread with a possible solution.

R-

[ronnieb]

I have a development to report; it may or may not help you Matthew.  It occurred to me that while two planes were experiencing this problem on almost every flight (A321 and B727),  one bird (FSX default Kingair 350) worked flawlessly with FSFO Ver. 2.3.  As it happens the KA350 was the most recent aircraft configuration that I had defined for FSFO.  The A321 and the B727 had been configured long ago, probably when I first got FSFO (Ver 2.0 ).

So I deleted (moved to another folder) those FSFO aircraft config files and built new ones.  They are the same as their ancestors but I was more careful with my weights, pax counts, etc.  I have flown two flights with each of these planes now and FSFO has performed perfectly from preflight to shutdown.  Now four is not a great number but it is enough to give me hope.  I will concentrate on flying these two planes for the next few days and let you know what happens.

FYI -- I'm using the original checklist files and TOLD files for the A321 and B727 and they work fine with the new A/C files.  I saved the old config files if you would like to see them.

Thanks again for your work.

R-

Jul 5, 2015 13:10:04 GMT -5 ronnieb said:

Hi Matthew,

. . .

My problem concerns the automatic features.  Taxi and Before Takeoff checklists execute automatically and work flawlessly.  When I take off, I know at 1000' AGL whether or not I have a problem.  If the copilot calls, "Climb Power," then every automatic feature will work throughout the flight.  If there is no call, then the following anomalies occur:

1.  Flaps retract on schedule but no CP callouts until, "Clean speed, flaps zero."

2.  The After Takeoff checklist will not be recited.

. . .

This seems to happen with all planes but the default A321 is the worst; almost always.  I thought perhaps it was unique to version 2.3, so I reloaded an old version (2.0 or 2.1) and it was the same.  It must be something that I'm doing but I can't find my error.  I hope that I explained this well enough.

Thank you for your attention and thanks again for this excellent program.

R-

[ronnieb]

Never mind!  The next two flights in the A321 both failed in the same way as before.  Sorry; I'm discouraged.  I thought I was on to something.

R- 

[Matthew King]

R, is this happening on consecutive flights? If so, try restarting FSFO on every flight. BTW, do the same problems still exist? I tried duplicating the following:

3. The copilot does not tell me to turn off the landing and taxi lights passing 10,000 feet.
4. At FL 180, the copilot does not call "Transition Altitude" and does not reset the altimeter.
5. Descending through FL 180 gets no copilot callout and I'm not told to turn on my lights at 10,000 feet.

These features work each and every time. I'm unable to duplicate these errors, especially the landing lights. Concerning the transition altitudes, can you you check to see if there a transAlt.cfg file located in the FSFO NavData directory?

I'll try to roll-out 2.4 in the next few weeks; right not I'm pushing FSFO Lite, which will be payware.

Don't worry, we'll get this sorted-out...

[ivanrk]

Hi Matthew

I have been trying for over a year now to get the gear to automatically retract on the default Boeing 737_800 with no luck.  Everything else works ok including the lowering of the gear.  I noticed way back several other Users having the same problem.  I am using your latest Version 2.3 (1 May 2015).  I am running on Windows 7 64 bit with the free version of FSUIPC.  Several of the other actions depend upon the gear being up before they will activate so if we could get this automatically working it would be great.  I have considered purchasing your LITE version hoping that might work but I noticed from the one review that has been posted that particular User also has the problem with the gear not being retracted upon takeoff with a positive climb.  Admittedly he was using a more advanced aircraft (PMDG).  I know you checked the logic of this before and stated that the logic was very simple so I guess it could be something I am doing wrong but for the life of me I cannot see what I could be doing wrong.  Your help would be appreciated.  It is still an excellent product which I use all the time and as I said the only thing I have to remember is for me to retract the gear as soon as I am airborne.

Ivan

[roadrunner505]

Dear Matthew,
I really like your addon - especially the voices do not sound too artificial.
But I have an issue with the re-activation of checklists:

When I activate it, it´s all normal. The announcement is i.e. "Throttle" - the answer is "idle". Next announcement is i.e. "Gear Lever" - the answer is "down". So far, so good.
But when I deactivate and re-activate the checklist the whole thing sounds like a remix. It starts with the first announcement, i.e. "request clearance", but then come about five answers in a row like "checked, down, idle, set, checked". Then follow announcements in a row like "parking brake, thrust levers, flaps" and then again a row of answers.
What am I doing wrong that the checklists only work when I start them the first time and and unmarking and marking them again I get this Remix?

[Matthew King]

Hey roadrunner!

Just to be sure we're talking about the right product, are you referring to FSFO v2.3, which is freeware? If its the latter, I'll try to duplicate the problem and get back with you. Hopefully, it's something I can walk you through; if it's a bug, I won't be able to correct it. I lost my v2.3 files long ago. I think I'm going to write a new freeware version and only charge for 3rd party aircraft. The latter really does take a lot of time to program.