OnCourse Software

JohnY wrote:

I repeat. If my altitude was 7500' exactly, why was my co pilot reporting it as 8000? And before anyone repeats it, I was checking my altimeter all the way across especially when she was reporting the wrong altitudes! I eventually moved up to 8000' to get her to report my proper altitude of 7500' which she did.

None of the answers address the problem that she was also calling the wrong altitudes during the previous IFR flightwhen I was also checking my altimeter regularly and flying a different aircraft.

I did, see first post after your question above:

ThomasAH wrote:

JohnY wrote:

1. The last IFR flight I flew my co-pilot was reporting my altitudes 500' above my actual. With this latest VFR flight the same thing happened.

You were at an altitude of about 7790 feet which got rounded to Flight Level 8000.
Remember to reset your altimeter to 29.92 (or 1013.25) above the transition altitude (ATC will then say "Flight Level 75" instead of e.g. "1 thousand 5 hundred".
I assume your altimeter was set to something around 29.67.

Yes, well, I've just flown the Real Air Duke IFR from EBBR brussels to LOWS Salsburg, and the whole thing was working perfectly until I was being guided on to 'Approach' and inexplicably Windows 10 closed me down just as I was turning left beside the mountains!

I know it does this sometimes but its really frustrating after flying some 400nm only to be closed down some 20nm out!

I was quite enjoying the flight too. Very peaceful over nice scenery.

John

I'm not sure how good FSUIPC's autosave feature is with the Duke, but if this is fine, then use it and enable "Save Restart data every X mins" in PF3 Options #1.
I had some problems with FSX freezing on a sound card problem in the past and this was great help (and this received many bug fixes during PF3's beta )

Now I sometimes intentionally kill PF3 and continue my flight on another day.

I'll try that Thomas . Thanks.

But. sorry to be ignorant, but what are the steps to take to restart it?

John

Just start PF3. It will detect the PF3 save file, and a popup will appear and tell you everything
(something like start the sim, load the saved state, pause the sim, connect PF3 to sim, unpause, wait a bit until PF3 contacts you by itself)

ThomasAH wrote:

Just start PF3. It will detect the PF3 save file, and a popup will appear and tell you everything
(something like start the sim, load the saved state, pause the sim, connect PF3 to sim, unpause, wait a bit until PF3 contacts you by itself)

You shouldn't forget to mention that it only works when the PF3 process was killed in the Windows Task Manager instead of closing PF3 regularly. Otherwise the saved restart data would get lost - if I understood that correctly.

I wished we could have a more user friendly way of restarting a PF3-flight.
Maybe instead of deleting the saved restart data on closing PF3, save them connected to the flightplan and then when the same flightplan is opened again offer the option to continue with the saved restart data.

In respect of the never ending OOM-story restarting a flight is necessary sometimes.

I assume it is somewhere on the list ...

RALF9636 wrote:

I assume it is somewhere on the list ...

It is

I tried the PF3 restart process, but it appears not to work when W10 closes the whole sim' down ie P3D so you have to start from scratch again.

In any case, I have my Windows updates set for 0200 so I don't really think its that causing the occasional closures. The message something like; 'Windows has experienced a problem and is closing down and will try to rectify it' is meaningless because it doesn't close down. Only the flight simulator closes down. But it still makes the flight in process irrecoverable. The computer remains on and all the other stuff seems unaffected.

I blame the Gremlins!

John