On ‎3‎/‎12‎/‎2021 at 7:16 AM, Tailwinds said:

That's where we differ. I never use the Save function. That's an immersion killer right there. Saving the flight and then if you get a CTD just load the save. For me personally, I wouldn't bother continuing on with a flight once the flight continuity has broken, the damage has been done already to spoil the flight.

Each to their own, I guess. But at the end of the day, you do realise this is a bunch of coloured pixels moving about on a 2D screen, not a real aeroplane..! :)

On 3/11/2021 at 12:48 PM, Elvensmith said:

Not sure as I haven't got FSUIPC for MSFS installed. However it's easy enough using the default mechanism - Esc, Spacebar then save the file.

Saving and reloading is a complete joke. Most of the time it sets the loaded flight's weather to clear skies, wind 270 at 3, and altimeter 29.92. And for some idiotic reason, it is impossible to change the weather in a loaded flight file to anything other than clear skies.

An integrated auto-save function is way too much to ask for. I mean, it's only 2021. Maybe Microsoft can at least charge $25 for a quick save key that would probably take developers about 30 seconds to code.

Edited March 14, 20215 yr by NightOfDreams

25 minutes ago, NightOfDreams said:

An integrated auto-save function is way too much to ask for. I mean, it's only 2021. Maybe Microsoft can at least charge $25 for a quick save key that would probably take developers about 30 seconds to code.

This. I have been saying since the start that the lack of an auto-save is a bizarre decision. Personally I don't need it, since I have had a single CTD since August. But from Asobo/MS's perspective, such feature would at a minimum lessen the negative comments from aggravated customers.

 

27 minutes ago, Turpentine said:

This. I have been saying since the start that the lack of an auto-save is a bizarre decision. Personally I don't need it, since I have had a single CTD since August. But from Asobo/MS's perspective, such feature would at a minimum lessen the negative comments from aggravated customers.

I've had very few CTDs in 7 months of MSFS, but even the risk of one is enough for me to want to save the flight periodically. I enjoy long flights, particularly with a successful landing, and can't justify spending 4 hours with even a small chance of CTD. So I needed a work around.

I used to save the flight every 15 minutes through the 6 step process (by pressing Esc, Save flight, Select file, Overwrite, Esc, Esc). Now, instead when I cross a waypoint I write down the time, altitude and fuel remaining. This way if there's a CTD I can start a "new" flight where I left off by selecting the last waypoint as the departure; then I can resume the flight with the same weather settings I had before the crash.

An autosave with weather reloading capabilities would be much simpler, but Microsoft already has my $60 so they don't care.

Edited March 15, 20215 yr by NightOfDreams

Oh I agree the Save function isn't perfect, AFAIK the FMC is still likely to lose your flight plan as not when loading on the big jets.

However for VFR in the hedge clippers, the interruption to the suspension of disbelief taking a few seconds to save now and again, is worth the otherwise frustration of losing your progress.

8 minutes ago, Elvensmith said:

Oh I agree the Save function isn't perfect, AFAIK the FMC is still likely to lose your flight plan as not when loading on the big jets.

However for VFR in the hedge clippers, the interruption to the suspension of disbelief taking a few seconds to save now and again, is worth the otherwise frustration of losing your progress.

I can save somewhat fast using the shortcut keys, but how hard would it be for them to implement a quick save function by allowing the user to press a single key to save, like in P3D??? Maybe someone can sell a 3rd party program for quicksaving and charge $30 

On 3/14/2021 at 8:42 PM, NightOfDreams said:

An autosave with weather reloading capabilities would be much simpler, but Microsoft already has my $60 so they don't care.

+1²  (what he said)

BTW, I am the OP of this topic and see a lot of references to CTDs.  Would like to clarify that in my situation the issue is the G1000 and GNS freezing up.  Not the sim.  Not CTDs.  The GPS gauges tend to freeze along with AP functions if I go into the flight plan or Proc pages more than a couple of times during a flight. And simply reloading the flight is a maybe/maybe not proposition.  Most often I must first restart the sim itself.  It is certainly robbing time and joy when I can fly the same flights with RXP in FSX SE with full nav data without interruption or loss of valuable time.

I am using the latest mods for both the G1000 and GNS.  If few others are experiencing this issue then perhaps I should focus on the Navigaph Beta I am also using.  But I need the more complete compliment of published instrument procedures that the Navigraph Beta provides over and above the MSFS default navdata.   Quite a number of the regional GA airports I fly to have only one or two published approaches in the default.  I fly real-time, real-weather and often encounter IMC conditions at my destinations.

Does anyone know if the autosave function is present yet in the MSFS compatible version of FSUIPC?

Edited March 17, 20215 yr by fppilot

Never had any freezes or CTDs in MSFS so far. Lost countless hours, days even, due to freezes and CTDs in FSX and P3D over the years. Never thought of quitting though.

1 minute ago, Tomaz Drnovsek said:

Never thought of quitting though.

Never said anything about quitting.  When I need to reliably complete a two hour or longer flight I just go back to FSX SE.  MSFS for me right now is a VFR, joy of scenery simulation.  In IFR conditions I cannot see the ground anyway......

9 minutes ago, Tomaz Drnovsek said:

Never had any freezes or CTDs in MSFS so far. Lost countless hours, days even, due to freezes and CTDs in FSX and P3D over the years. Never thought of quitting though.

I had the opposite experience. P3D for me was rock solid. I could count the CTDs on one hand in over 7 years of use. Until I installed the CTD Vaccine in MSFS , I averaged about 35-40% CTDs on my flights. After the Vaccine, zero  CTDs in a week and a half. Now it is as reliable as P3D was for CTDs. The other issue however which started with last update is the 5 FPS in certain areas. 

Edited March 17, 20215 yr by Bobsk8

2 minutes ago, Bobsk8 said:

I had the opposite experience. P3D for me was rock solid. I could count the CTDs on one hand in over 7 years of use. Until I installed the CTD Vaccine in MSFS , I averaged about 35-40% CTDs on my flights. After the Vaccine, zero  CTDs in a week and a half. Now it is as reliable as P3D was for CTDs. The other issue however which started with last update is the 5 FPS in certain areas. 

Interesting. I fly VFR and IFR in MSFS, the longest flight being about 4 hours - not a single CTD yet. And I run with settings mostly on high and ultra. *Knocks on wood*.

I got countless CTDs in FSX and P3D v2 and v3. P3D v4 was rock solid for me too. 

I also get the FPS bug now on almost every flight though but since the areas where it appears are pretty small and I got lucky I never got it on approach, I try not to bother about it too much. I do hope they sort out this issue soon though.

On 3/12/2021 at 2:16 AM, Tailwinds said:

That's where we differ. I never use the Save function. That's an immersion killer right there. Saving the flight and then if you get a CTD just load the save. For me personally, I wouldn't bother continuing on with a flight once the flight continuity has broken, the damage has been done already to spoil the flight.

I am curious about your statement that using the Save function destroys your immersion experience. You are sitting in a chair in front of a computer in your house or other structure on terra firma, are you not? And do you routinely manage long flights with no interruptions from start to finish? I would argue that this is actually unrealistic. Even in the real world, airline pilots periodically need to take breaks from the cockpit -- which are "interruptions", are they not? I am also big on immersion, and get far more of it in MSFS than any other sim, but don't see how taking 20 or 30 seconds to save a flight is an "immersion killer" or that it "spoils the flight".