CTD on Steam

Made a ticket post earlier, but updating that mine is operational as of ~0500 today (EST*).
(I was able to make continuous progress on the percentage by just bruteforce opening the game gaining 5-10% per launch, but I'm uncertain if it influenced it as it locked several times at 98% before later becoming functional.)
 

Support Luna

Customer Support
Frontier
I have done launches, jumps and dockings in-game, exited to desktop and restarted the game successfully, with no further attention to the fsave_optionsxxx file.

@sallymorganmoore - this may, or may not be the reason for the issue - but it deserves investigation by the Dev team. I still have the fsave-options file which was causing, or invoolved with the crash and can send it if required.
This information has already been passed on to the development team to aid in their investigation into what's causing this crash. Appreciate you flagging it nonetheless!
 
A suggested fix, which originated from Reddit user u/zappsr - This should only be attempted by you if you are confident with delving in to the files and folders within your PC.

"Go in that User>Appdata>Roaming>Frontier Developments> Elite Dangerous>Options and rename/delete the fsave-optionsxxxx file"

I suggest that you do not delete the file until you have copied it elsewhere, such as to the desktop, or backed it up to an external drive or to the cloud.
Once done and the options file is empty (or has a renamed fsave_options file) start up the game and try to get in-game.

I have done so and gotten in-game for the first time in over 24 hrs.
However, some reports on the issue tracker say that they experienced a CTD once in game when they went to do something.
So far, I have moved my ship from the hangar to the landing pad and launched and have remained in-game.
Another key test will be if I can close the game and restart it successfully without doing anyhting further to the fsave_options file.

Then there will be the question - Why did this file stop my game from starting?
Worked for me. Many thanks
 
I have not had to delete the fsave_optionsxxx file prior to each start of the game and have spent around six hours in-game today without any crashes. However, my experience may not be reflected in the experiences of all other CMDRs who were experiencing the CTD during startup (or very shortly afterwards). Fingers crossed that the short outage to the game from 5.30 pm BST today will resolve the issue for everyone affected.
 
Loaded the game after being away for a week, accepted three donation missions and all three, individually, CTD after making the donations. :(
I didn't send crash reports as I thought it was just me. Sorry Frontier, my bad.
 
Loaded the game after being away for a week, accepted three donation missions and all three, individually, CTD after making the donations. :(
I didn't send crash reports as I thought it was just me. Sorry Frontier, my bad.
Same here. Always i choose a donation, no matter what donation i choose CDT
 
CTD before the menu loads still happening for me

Update: Deleting the fsave_optionsxxx file (or moving to another folder in my case) worked for me, and now logged into the game, will see how well this session goes.

Update 2: Working great, building ship, engineering, take some passenger missions, no problem... hand in my first passenger mission and CTD, now back to CTD before menu everytime, bummer

Update 3: So deleting fsave file gets me back in game each time, and CTD when handing in missions seems to be only when selecting reputation reward
 
Last edited:
Same thing happening to me. Whenever I hand in a mission, it CTDs. This is on Geforce Now. Three missions, three CTDs. It doesn't seem to matter if it is a space legs mission or a ship mission. The first time it happened, I got a Blue Cobra error code, but not the other two times.
 
Back
Top Bottom