Having to exit game via task manager

Just lately, about for a week or so, it seems the game is not quitting as it should and I'm having to use task manager to close it.

Of course, it's not every time so it is a little difficult to pin down. However, I did update my GPU drivers to (GeForce) 536.23 about 2-ish weeks ago - could this be the issue? There has also been a Win 11 update or two since then.

Not too big a deal but I wondered if anyone else is seeing this.

Thanks.
 
I've been experiencing this since my return last Feb. The longer I play, the higher the probability this will happen. A 5+ hour session is pretty much a guaranteed freeze on exit.

I just created a shortcut on my right screen named "Kill ED". If the game doesn't close after 30 seconds or so, I hit the shortcut. I also try to verify game files after using it, just in case.
 
I get it happen completely randomly, no pattern that i can observe, updating gpu or other drivers doesnt seem to be a trigger, long or short playtime doesnt seem to have an influence, well for me at least. If i were to hazard a guess its the server not telling the client that the "shutdown" process has completed and to exit to the launcher. purely speculation though of course.
 
The scenario that assures that I have to kill the task using Win Task Manager is:

On any given Wed night (for me) if I'm playing late enough to receive the in-game server broadcast message announcing the weekly down time, I ALWAYS have to kill the task. It does not terminate properly. This has been going on for a couple of years, persisting through Horizons 3.8, through Hor4 and into Ody & update 15.

Clearly, over such a long period of time, this has persisted thru a number of graphics driver updates as well (Nvidia in my case).

Over the time frame described in the OP, I have been online daily and have had just one such occurrence (not on Wed night) so it remains to be seen if this is a new regular for me. Will see again tonight (if I don't nod off and crash my ship into something). :) :alien:
 
Ive been occasionaly encountering a situation where you cant do any action (fsd charges to full but doesnt jump, main menu doesnt open...) and ive been told (poorly paraphrasing rn) that every ingame action including main menu is a communication with server and this happens when desync gets too bad.
Could shutting down have a communication element in it that could get stuck because of this? Resulting in the game not shutting down properly?
It seems to happen after longer sessions, especially when did put a lot of strain on my connection (watching streams, downloading in background...)

Are fdev perhaps rerouting their servers go go juice somewhere else? Is the game ending? Did i just become a doomer?
 
I have always presumed it is an amazon aws(that's where fd hire the main servers) peer to peer network packet going missing and pc waiting for a reply now lost...….
I think it is almost certainly a peer to peer network quirk
hence sometimes a force quit required that's just my guess
I think its basically the same problen as mission objectives sometimes requiring a log out in to get them to spawn correctly
 
Last edited:
Hmm. I seem to be getting a fair few black screens on vehicle egress which results in the exciting process f having to shut the game via task manager.

The last one had me donning lycra (not a pretty sight) for the 1/2K marathon back to my ship where the suddenly AWOL SRV I had been driving miraculously rematerialised on board.
 
Once the process of exiting the SRV has started, a disconnection will always send the SRV back to the ship. I'm thinking the server was never updated on the SRV's current position, so it puts it in it's last known position (the ship). The positional update may very well be the reason for the long pause when exiting the SRV in the first place. That issue seems more common with higher player activity in the current system. It only happened once during a 16KLy trip out into the black, and that pause was only 10 seconds.

I wouldn't be surprised if both issues were related. I would be very surprised if it's ever fixed.
 
Once the process of exiting the SRV has started, a disconnection will always send the SRV back to the ship. I'm thinking the server was never updated on the SRV's current position,
data packet loss
I wouldn't be surprised if both issues were related. I would be very surprised if it's ever fixed.
I cant see them switching to a client server either
 

Attachments

  • weak link.jpg
    weak link.jpg
    58.5 KB · Views: 51
Back
Top Bottom