SquadronLeader (1/24/2011)

---

"(Oh, and how to tell FSFS a Cub doesn't have flaps? Setting everything to 0 doesn't seem to work)"

What happens if you let FSFS autodetect the settings of the aircraft? (Make sure no FSU file is in the aircraft folder for that plane).

AndiD (1/25/2011)

---

Now the instructor is pestering me the entire flight about raising gear... (and complaining about flaps AND spoilers in the log)

What is the exact name of the folder which contains the aircraft's

aircraft.cfg

file?

Who made the simulated aircraft? 

Please email the aircraft.cfg file to

support@fsflyingschool.com

so we can examine it in detail.




About the other problem, I'm throughly puzzled now:
- Indeed it seems that FSFS is not getting the runway. I tried to deliberately shoot a good number of degrees to the side during descent and did a last minute correction to the runway below 100ft (fun in a Cub at 50kn ), same landing score of 25ish.

- However, passing 500 AGL I don't hear anything, not a thing about a runway, either positive "runway 13" or negative "don't know which runway". Runway 13 is set in the FSFS window. Every time I'm hearing (correct) glideslope OBS heading 125, no localizer (so visual approach) and waypoint reached. That's it. And for a short time I can glimpse a message "Landed at: []" in red text on green in FSX every time I land.

- In terms of alignment, how much margin of error in terms is there in terms of heading? Cause it seems that for rwy 13 @ KETB the OBS setting is 125 but the actual heading I need for visual alignment (GPS track) is close to 130.

First - can you tell me (or remind me ) what version of FSFS you are using? 

- The most curious thing is that my flight report above says "* Heading aligned with runway." among the positive stuff and "Poor alignment with runway on visual approach - line up and stay there. [0%]" which I suspect is a follow-up error to the "without proper approach" thing. How's the first thing possible without the second?

Heading aligned with runway means that you where pointing down the runway when you landed. "Poor align on approach" (etc) or "without a proper approach" means poor alignment before landing.

Should I send you a flight saved right before the landing phase?

Please email your HTML log book to

support@fsflyingschool.com

so we can examine it in detail.

Please include a note giving the runways landed at in the most recent problem landings in the log book.

I'd love to go back to circuit training (where I left in 2008 (?)) but can't without a sufficient landing score beforehand...

Try landing with no flight plan or with ILS. What results do you get?

SquadronLeader (1/26/2011)

---

Hi

Thanks for the files.

I see that NAV1 is set to "GSH"

Is thisGOSHEN at 113.70? Can you check what your NAV1 radio frequency is set to?

Is it some other frequency? It could be some other NAVAID called GSH.

Also - the aircraft.cfg file contains settings for flap positions (???) and it is this information that we read when we have to figure out facts about an aircraft.

You should be able to create an FSU file (save your own custom user data) with no flaps and no gear and whatever you want - have you tried this per the instructions in the manual?

AndiD (1/26/2011)

---

I swapped to the C172 in-flight to check the radio stack and I believe yes, it is 113.7. (Third value in the row of four values on the upper Bendix radio - not too familiar with all this radio stuff yet). No idea where these settings come from. (Radio stack stays dark when cheating and putting a radio stack as [Window10] into the cub panel so I had to switch aircraft.)

This is something we are looking at - when an aircraft does not have a NAV1 radio, FSX is still providing NAV1 data to FSFS and this can lead to odd situations.

Can you try some landings in the c172 (or just some stock FSX plane which has a NAV1 radio) while making sure that the radio is not picking up a NAVAID (it is not picking up a signal). You can check this by telling the radio to let you hear the morse from the NAV1 radio and if there is no morse it is not tuned to any NAVAID.

It would be most helpful if you could try this both with and without a flight plan when you are landing and please make sure you are all lined up and in landing mode when you descend through 500 feet above ground level (which will NOT be the altitude on your altimeter).

NAV1 OBS is getting overwritten by the correct runway heading in FSFS during approach (correct heading is displayed on Ctrl+Shift+D, checking this every time). I also remember this from 2008.

Understood.

I simply copied the stock Cub FSR file after I got the correct name from "Save user data". No flap stuff doesn't seem to be recognized even if all is 0 (and I tried removing the 0 as well, still there). Should I try and see whether I get the flap message when landing the stock Cub?