I'm a registered user of FSF with FSX and I'm experiencing some problems which I can't sort out. If I've missed something obvious, please accept my apologies. The first thing relates to the traditional logbook. There are only three entries in it so far, but all indicate some night flying time aswell as day flying and this is inaccurate because I haven't flown at night with FSF yet? I'm flying from EGNV in the UK so is the program using US time or something? Also, and perhaps more significantly, FSF has started to disconnect in the middle of my flights because it claims to have detected a time of day switch/alteration. I don't access any menus or anything whilst the programme is running so this is also incorrect. The information, and my progress, in the full logbook is being ruined by these stop-start sessions and is no longer a cohesive representation of my efforts. Can you help?

Oh, whilst I'm here, could I make a suggestion? Would you make it possible as an option, in some future update perhaps, to have full control of the initiation of each flight phase without the programme trying to second guess what we're doing? It's very inconvenient to have to reign your examiner in when he's 'jumping the gun' so to speak! I'd much rather have full-control over what I'm doing and exactly when. Nice programme! I hope I can get it running properly.

Thanks whatever the result, Ian.

Intel Core2 Duo 6300, Windows XP full updated, Nvidia 7300GS, FSX: FSUIPC4(reg), RealAir SF260, Scout packages, FSF.

Could you send us all the files in the PilotRoster folder? Just zip them into one file and either send them to this forum or email them to us if this is easier for you. 

>> I'm flying from EGNV in the UK so is the program using US time or something?

This should not be an issue - we will investigate based on your files.

>> Also, and perhaps more significantly, FSF has started to disconnect in the middle of my flights because it claims to have detected a time of day switch/alteration. I don't access any menus or anything whilst the programme is running so this is also incorrect. The information, and my progress, in the full logbook is being ruined by these stop-start sessions and is no longer a cohesive representation of my efforts. Can you help?

Of note is that you've reported that this "has started to disconnect". So we understand that this worked fine and only then, currently, became a problem?
If so - can you imagine any recent changes made to your system around the same time?

>> Oh, whilst I'm here, could I make a suggestion? Would you make it possible as an option, in some future update perhaps, to have full control of the initiation of each flight phase without the programme trying to second guess what we're doing? It's very inconvenient to have to reign your examiner in when he's 'jumping the gun' so to speak! I'd much rather have full-control over what I'm doing and exactly when. Nice programme! I hope I can get it running properly.

Thanks for the kind words about FSFS.  
Your point is well made and others agree. We are looking at offering the pilot the choice between having FSFS auto-detect the various flight modes, or not. During beta testing, a large body of users requested this feature - some love it, others prefer to do it manually.

Jeff Preston ('Squadron Leader') - FSFlyingSchool Publisher & Lead Developer


FSFlyingSchool 2023 for Microsoft Flight Simulator
FSFlyingSchool 2023 for X-Plane 12 & 11
FS Instant Approach 2023 for X-Plane 12 & 11 (Windows)
FSFlyingSchool PRO 2020 Prepar3D v 5
FSFlyingSchool PRO 2019 FSX, FSX-SE, FS2004
FSFlyingSchool USA for Microsoft Flight Simulator
FS Instant Approach 2019 for X-Plane 11 (Mac)
FS Instant Approach for Microsoft Flight Simulator
FS Instant Help for FSX, FS2004


Winner of 5 consecutive PC Pilot Magazine 'Classic Product' Awards

Fly like the Pros with X-Plane, Flight Simulator and Prepar3D!

If you wish to unsubscribe simply reply to email with the word UNSUBSCRIBE in the SUBJECT line.

I've sent my PilotRoster.zip for perusal at your convenience by email so hopefully you'll get that shortly. If you'd rather continue the help here at the forum please post accordingly. I'll pop-in regularly to view. Some additional info is contained in the mail.

Cheers, Ian.

Thanks for emailing the zip. We don't see it yet at any address - but will keep looking and would certainly want to continue this issue in the forum as it may be of help to others.

Jeff Preston ('Squadron Leader') - FSFlyingSchool Publisher & Lead Developer


FSFlyingSchool 2023 for Microsoft Flight Simulator
FSFlyingSchool 2023 for X-Plane 12 & 11
FS Instant Approach 2023 for X-Plane 12 & 11 (Windows)
FSFlyingSchool PRO 2020 Prepar3D v 5
FSFlyingSchool PRO 2019 FSX, FSX-SE, FS2004
FSFlyingSchool USA for Microsoft Flight Simulator
FS Instant Approach 2019 for X-Plane 11 (Mac)
FS Instant Approach for Microsoft Flight Simulator
FS Instant Help for FSX, FS2004


Winner of 5 consecutive PC Pilot Magazine 'Classic Product' Awards

Fly like the Pros with X-Plane, Flight Simulator and Prepar3D!

If you wish to unsubscribe simply reply to email with the word UNSUBSCRIBE in the SUBJECT line.

Cheers, Ian.

>> ...The last entry in my full-log was a full flight from taxiing & take-off onwards but FSF aborted whilst I was sitting nicely on the glideslope/localizer on final. Resigned to the fact that I had lost the previous data I tried to capture some data for landing by reconnecting mid-flight and forwarding the phase but it didn't recognise the glideslope info and just scored the basic landing (I'm not sure if you can do this anyway?)

You certainly can do this, but you need to make sure that when you start your mid flight session you're, in general terms, at least about 1000 feet AGL (above ground level) and a good few minutes out from the runway, and of course have your NAV1 radio set to receive the GS and LOC and your NAV1 OBS set to the intended runway heading.

We do this all the time to practice landings during testing.

>> Note the night entries but all my flights were around noonish? Yes I did have a couple of normal sessions prior to this time/cut-off error. Could FSUIPC4's sync time with FS, or the default latitude & longitude co-ordinates in the 'General' section be the cause? Mine's set to Northern Eastern?  I'm sure I didn't touch anything else. I'm out of ideas. I'll post in the forum too.

Sorry - I'm not following the specific points yet - I am very interested to hear in detail about any part of the config of FS or FSUIPC you have changed. I am also very interested to have your opinion on whether the two could be related - in other words can you recall when this problem started and did you change or update FS or FSUIPC around the same time?

Also - just got this from your log -
AFOX piloting SIAI-Marchetti SF.260 G-AERO ended 12 July 2007 at 00:38
This flight was very good all around with a good landing. Is it correct to say that the disconnect problem does not occur with every flight, since it started happening?

And - did this flight really end at 00:38? This would be night time - was this merely the real-world time of day or was it also the simulated time?

Jeff Preston ('Squadron Leader') - FSFlyingSchool Publisher & Lead Developer


FSFlyingSchool 2023 for Microsoft Flight Simulator
FSFlyingSchool 2023 for X-Plane 12 & 11
FS Instant Approach 2023 for X-Plane 12 & 11 (Windows)
FSFlyingSchool PRO 2020 Prepar3D v 5
FSFlyingSchool PRO 2019 FSX, FSX-SE, FS2004
FSFlyingSchool USA for Microsoft Flight Simulator
FS Instant Approach 2019 for X-Plane 11 (Mac)
FS Instant Approach for Microsoft Flight Simulator
FS Instant Help for FSX, FS2004


Winner of 5 consecutive PC Pilot Magazine 'Classic Product' Awards

Fly like the Pros with X-Plane, Flight Simulator and Prepar3D!

If you wish to unsubscribe simply reply to email with the word UNSUBSCRIBE in the SUBJECT line.

As far as I can remember, I made no alterations to FSX's cfg after the FSF install - I have FS set-up pretty much as good as I can get it presently so I'm fairly certain I made no changes. I installed FSF and it seemed to be doing what it said it would do 'on the tin', so to speak. I haven't had the programme very long though so I can't be certain it was operating correctly in the first place.

I did notice several rather abrupt phase changes at peculiar times on different flights (it switched to landing-mode whilst I was still climbing out on one occasion and to take-off-mode whilst I was taxiing on another. No-I wasn't taxiing that fast!) but at the time I just assumed it was my fault and my novice handling of a new utility. This prompted my request for full-control of the phases in a possible future update.

Before it later began to disconnect itself during my sessions, I had noticed that it was recording night flights in my logbook (these night entries weren't recorded in FSX's default logbook and were FSF unique. My flights were all flown round about the same time, noonish in the UK. I wasn't sure whether FSX was somehow causing a time-zone confusion so I checked everything but couldn't find anything. I tried changing my default co-ordinates in FSX's General section from Northern Western to Northern Eastern (the only thing I changed) but I think now they're just for map display purposes and inconsequential. Finally, my registered copy of the latest FSUIPC4 has a setting which has remained constant since I installed the utility some time ago. It think it synchronises flightsim to my PC and wondered whether that might be causing a conflict? I haven't altered anything since I installed FSF so this is probably unlikely also.

The key issue for me is that FSF disconnects because it detects drastic changes which I'm not initiating (I make no changes whilst the programme is running), in this case a time of day change, and this fits with the time anomolies in my traditional FSF logbook (and as you pointed out 00.38??? in my full log book). FSF is getting it's time data from somewhere but I can't find it anywhere on my PC (it's internal clock is synched with Greenwich).  I'd better stop this post now it's already an essay, sorry.

Ian

I've just flown using the programme again (I've sent the data in another PilotRoster.zip) and it stayed with me all the way without disconnecting (it disconnected three times in prior successive sessions so I just aborted the sessions).  I didn't use my old saved situation at EGNV this time and set everything up to fly from nearby EGNT instead. I had no problems during the flight and rather enjoyed it. When I got down to the runway, however, I was more than a little miffed to hear my instructor telling my I wasn't anywhere near the centre-line and I when I was sitting on it!! Even with a crosswind I was on rails all the way down and very pleased with myself until he dropped that bombshell and marked me down... If the SF260 had built in passenger ejection he would have been long gone... Your examiners are a little too ruthless at times! (on that note I think you could greatly increase the time between repeated instructions;

'..you're below the glideslope let's intercept it..'   '..yeah, I'm on it..'

'..you're below the glideslope let's intercept it..'   ' Yeah. I'm on it. '

'..you're below the glideslope let's intercept it..'   ' Don't push it, buddy.......' 

Less frequent repeats and more patience would be most welcome when your struggling with a bit of weather or something. He can always railroad you at the end when he's scoring so long as he doesn't make it up like he did about the centre-line!

As you'll see from my traditional logbook, a night time entry has mysteriously appeared again but the full logbook's time is correct on this one. The earlier 00:38 was invention!

I love this programme, it's improved my flying already and even after so few flights and after a few system problems or whatever I've already had my money's worth out of it!

Cheers, Ian.