6 minutes ago, JimBrown said:

Hey! You're right. I've always used the Steam client (system tray icon) to start MSFS and have yet to see the Safe Mode prompt. Just for giggles, I went and found the flightsimulator.exe file and created a desktop shortcut for it. What do you know, every time I use the shortcut, I get the Safe Mode prompt.

How interesting. Looks like a bug in the Safe Mode implementation.

I wonder if all those that get it continuously are using a shortcut?

...jim

 

Yeah that a strange one. Too bad as i'd prefer using the shortcut instead of the client. But hey, maybe this gets sorted out at some point.

Guys having issues might try using the client...maybe this is of help at this point.

Happy flying!

1 hour ago, ThomseN_inc said:

1. Start Sim

2.Open Dev mode and hit "Save Settings"

3.Close Sim via "Quit do Desktop"

4.Start Sim

5.Exit Dev Mode

6.Restart Sim

 

This did it for me. No more questions at startup.

Yes that did it for me, many thanks  🙂

38 minutes ago, JRBarrett said:

Simply closing the window is not the correct way to exit the sim. There are open files that need to be closed, virtual drives that need to be dismounted, and other shutdown housekeeping that will only occur if you exit by using the “quit to desktop” option on the main menu.

Exiting MSFS by closing the window would be the equivalent of exiting a running Windows 10 session by simply turning off the computer’s power switch. Doing that would be a good way to corrupt your OS installation.

 

 

I am always shocked and dismayed about the amount of people who seem to have nothing better to do than to try and blame the users for every little issue that pops up.

 I myself have absolutely no idea why the Safe Mode issue occurs, however what I can tell you is that closing and application by using the “X” button is not only an acceptable way of closing an app on PC products, in most cases it is the ONLY way of closing Microsoft Software. They have built an entire culture of using the “X” button over many, many years and quite frankly trying to suggest that it shouldn’t be used is laughable.

 Even if using the “X” to close MSFS2020 is actually the problem, then it can (and should be) simply removed, like 100’s of other PC apps and games which do not have it.  Either way it’s an issue that Asobo can sort out.

14 minutes ago, flibberflops said:

I am always shocked and dismayed about the amount of people who seem to have nothing better to do than to try and blame the users for every little issue that pops up.

 

 I myself have absolutely no idea why the Safe Mode issue occurs, however what I can tell you is that closing and application by using the “X” button is not only an acceptable way of closing an app on PC products, in most cases it is the ONLY way of closing Microsoft Software. They have built an entire culture of using the “X” button over many, many years and quite frankly trying to suggest that it shouldn’t be used is laughable.

 

 Even if using the “X” to close MSFS2020 is actually the problem, then it can (and should be) simply removed, like 100’s of other PC apps and games which do not have it.  Either way it’s an issue that Asobo can sort out.

 

sigh, you still dont get it smh. Nobody is blaming anyone. Just because we can close certain program with the x doesnt always mean its the right way. Like the poster ho you quoted said, the sim has to do its tidying up and there are virtual drives that the sim creates which has to be shut down also

6 minutes ago, devgrp said:

sigh, you still dont get it smh. Nobody is blaming anyone. Just because we can close certain program with the x doesnt always mean its the right way. Like the poster ho you quoted said, the sim has to do its tidying up and there are virtual drives that the sim creates which has to be shut down also

guess  users  are in a  rush  to  shut  down to get  some  where  else 🙂  doesnt  take  that much longer  doing  it  the  right  way

As a dev, I am always wary of allowing a program to close by using the X button...  not from my point of view, but all pressing X does is force a windows event called Application.Exit().  Whilst this is fine for a stand alone program..  if you have any other program connected to it when you force close..  the connected program can be either corrupted, or corrupt the close...   so in this case.. if you are running MSFS stand Alone, then you are probably OK as it will be a standard Application.Exit().. however.. if you are running anything connected to the sim such as external programs, peripherals etc..  then you should shut everything else down BEFORE hitting the X button to be safe.  

I would imagine that some who are seeing the Safe Mode implementation are seeing it because something external (Navigraph, Axis and OHHS, simconnect, peripherals,  OnAir, whetever), tried to do an update as the sim was closing so the opening data is not what was expected.

A quit to desktop will not do this as it is a program controlled exit which will correctly shut everything off before doing the close..  or at least will do it in such a  way as to not try to change the MSFS data files as it closes, and no it is not possible in standard programming to properly intercept the X button and drive it through the normal application close procedures 🙂  That has been tried many times.

That's why most programs of this complexity prefer to run in full screen mode where X is not available.

Graham

Edited September 9, 20214 yr by Moria15

Almost all PC games are designed to run full screen where there is no X button at all. Like MSFS they have a close program option on the front menu system. I am not sure why people are running MSFS in windowed mode as they are wasting so much screen space.

CJ

23 minutes ago, devgrp said:

sigh, you still dont get it smh. Nobody is blaming anyone. Just because we can close certain program with the x doesnt always mean its the right way. Like the poster ho you quoted said, the sim has to do its tidying up and there are virtual drives that the sim creates which has to be shut down also

If the programming team have left the "X" button in place, then it is considered a correct way of closing the program. If it is not the correct way then any programmer can remove it in 60 seconds. Like I said this is a Asobo issue not the user. If it is been left in then you cannot specify it is the incoorect way of using it.

14 minutes ago, CJ1045 said:

Almost all PC games are designed to run full screen where there is no X button at all. Like MSFS they have a close program option on the front menu system. I am not sure why people are running MSFS in windowed mode as they are wasting so much screen space.

CJ

MSFS has not been designed to run full screen... It has been designed to run full screen or Windowed.

 You don't understand why people don't use full screen simply because you cannot see the way people use the sim beyond the way you do. There are many reasons why you would want to run windowed, Inc VR when the monitor is not your primary display.

 

20 minutes ago, flibberflops said:

I am always shocked and dismayed about the amount of people who seem to have nothing better to do than to try and blame the users for every little issue that pops up.

 

 I myself have absolutely no idea why the Safe Mode issue occurs, however what I can tell you is that closing and application by using the “X” button is not only an acceptable way of closing an app on PC products, in most cases it is the ONLY way of closing Microsoft Software. They have built an entire culture of using the “X” button over many, many years and quite frankly trying to suggest that it shouldn’t be used is laughable.

 

 Even if using the “X” to close MSFS2020 is actually the problem, then it can (and should be) simply removed, like 100’s of other PC apps and games which do not have it.  Either way it’s an issue that Asobo can sort out.

 

I am not trying to blame anyone. I am trying to help the OP resolve his problem.

Yes, all Windows apps can be closed by X-ing out, and in many cases that is perfectly OK, but whenever an app has a dedicated “exit” function, I always use that on the assumption that the developer created a dedicated close function for a good reason - especially if the app in question works with files.

I have written several Windows apps for my own use over the past 20 years with both Visual Studio and Delphi, and if the app accesses files on disk, I always include a dedicated exit function which closes any open files, as well as freeing up any reserved memory that may have been created using malloc() or calloc().

Neither function (closing open files or freeing dynamically allocated memory) is guaranteed to occur if the app window is simply closed.

Even before the new safe mode feature was added to MSFS, if I exit the sim by simply closing the window, the administrative event viewer will contain an entry “Drive (x) was surprise removed”. The “x” will be a number, and the drive in question is a virtual drive created by MSFS when it runs.

This very same event will appear if the sim crashes unexpectedly. The “surprise removed” event does not appear when exiting the sim by using the “return to desktop” function.

The fact that the new safe mode feature specifically mentions that the sim “did not shut down properly” as the reason for why the safe mode option is being offered, should probably be taken at face value.

Assuming the x buuton is the issue then Asobo still need to be highlighted to the issue and remove it.... not telling users not to use it.

11 minutes ago, flibberflops said:

If the programming team have left the "X" button in place, then it is considered a correct way of closing the program. If it is not the correct way then any programmer can remove it in 60 seconds. Like I said this is a Asobo issue not the user. If it is been left in then you cannot specify it is the incoorect way of using it.

There are only 2 ways to remove the X button...  and both of them also remove the Minimise and the fullscreen/othersize window button.

Unless you completely re-write the windows form programming, you do not have the option of just removing the close button.

Potentially the easiest is to run the window as FormBorderStyle.None and then add a menu bar to the screen to have your own close system..  kinda like a "Quit to desktop" button 🙂

Graham

Personally I was using X to close for almost all the apps including MSFS and I did not face any problems about this for years, yet. 

Explanations are both correct, maybeit is better to close the sim with a proper way (quit to desktop) but if there is windowed mode and if X(close) was working fine before, I just wanted to keep that.

Edited September 9, 20214 yr by kt069

no Asobo have absolutely done the right thing here and given the EU a choice of which action to take, the fact it doesn't time out is a none issue imo.

 

 

Full-screen mode here. I just press Alt+F4. Can't this action trigger a shutdown routine as done in P3D, FSX... or even FS9?

Yes, I'm bothered, specially since yesterday I wanted to take a quick spin in MSFS, and had to wait half an hour until it finished updating. I fired up another sim instead...