FEAR: Extraction Point: "Disconnected from server"

[lufia22]

I'm on the level Leviathan trying to go to the next level. Every time it loads, it gives me a "Disconnected from server" error. I had this issue once before. It took me a few tries and a restart, but I got it to load the next level randomly. I can't get it to work this time.

I've tried using the maphole command. Doesn't work. Any suggestions?

EDIT: Well, I set the game to minimum graphics and it loaded. Whatever.

[MechaEmperor]

Same. Fixed it by reducing the resolution to 800x600 right before the level ends. Saved, and loaded again with higher res.

[eartahhj | GamingHouse]

Just want to be of help for anyone like me who will come here looking for an answer
I think I found a way to FIX this. At least it worked for me.

I basically tried to change some display option. I switched resolution from 640 to 1280 but I don't think this is it.

---->
I think the real workaround here was when I changed "Force Restart" to ON because I suppose there must be a problem on loading graphic engine when the new level starts. So THIS forced the graphic engine to restart every checkpoint and every start of an interval. It loads newly textures and so on. Its the only thing making sense to me so far, since to receive a "disconnected from server" error is quite weird on a Single Player match... Usually on Multiplayer it happens when a Mod fails loading or you don't have some files, or you ping too high, so this on FEAR likely happened because of a graphic engine failure. I suppose. This worked for me I didn't encounter this problem anymore between interval 4 and 5 and I could end Extraction point. Hope this helps.
<------

Someone suggested to start a new game, skip cutscene, and then load the savegame before the disconnection. It worked for me sometimes, but not always, sometimes it kept giving me the problem.

My rig if anyone is having the same problem:
Windows 10, R9 290X TriX OC, i7 4790k, 16GB RAM Corsair Vengeance Black DD3

[Knocked Loose]

Confirming that Force Restart method worked. I also used the lower res and reset it after it loaded in. Thanks! ]

twitch.tv/tenfoura played it here :D

[Hiramaky]

Just tried all suggestions here - no effect. Tried maphole, verifying files, changing resolution, activating force restart. Still the same result every time, sometimes it gives me a "pure runtime error". This is pissing me off - the original F.E.A.R. had no issues with this, and Perseus Mandate had it too, but to a lesser extent. I know this is necroing but this is something that timegate should have sorted out a long time ago.

[NemesiS]

Rhesus... I was having the same problem and nothing worked for me either... I tried using low resolution, maphole, force restart, even compatibility with Win XP... But there was only one thing that worked... Before entering the hospital I went to "settings > performance" and lowered everything to minimum (one of those things may be the problem, textures perhaps, I don't know) then in the game I enter the hospital, it loads for a while and miraculously begin to work properly... Then I just did a quick save > increase settings to maximum again > restart the game... And when the game loaded it started working perfect. Hope it helps.

[Hiramaky]

Only one way to find out!

[Wolvyreen]

I know this is old but I can confirm this fix. Running Windows 10 with Nividia GTX 980Ti and the ONLY thing that worked for me was to drop ALL gfx performance to ground level, try again and quick save and reload the game and set all performace to the max again.

[joao01paulo01]

The only way that worked for me was to decrease all settings at least, including the graph.

I also had the "disconnected from server" problem before entering the hospital.

AMD FX 6500 3.5 Ghz, GTX 960, 8Gb ram

[Wolvyreen]

I tracked it down on my PC to be the Texture Resolution. I dropped that to minimum and the problem went away. I increased it again and the problem was back.

[Hiramaky]

Considering how close it is to the end, I've more or less gave up on it, since everything I did results in failure.

[Schlendi | #LV426]

I experienced the same error at the location, where you go into the subway cars and then the game loads into the Orange Line. I fixed it with turning on "Force Restart" and the game works fine until now.

I have the same issue in Perseus Mandate before you start Interval 7. When i turned on Force Restart there, the screen goes black and the game crashes.

My rig is the following one:
i7-8700K
GTX 1080 SC
16GB DDR4-3200 Ram
Windows 10 Pro 64 bit (v1803)

[Schlendi | #LV426]

Originally posted by Wolvyreen:

I tracked it down on my PC to be the Texture Resolution. I dropped that to minimum and the problem went away. I increased it again and the problem was back.

I finished Extraction Point yesterday and experienced some disconnect bugs and one C++ runtime error (code R6025) before you enter the hospital.

With this fix, I was able to finish the game. Thanks for this :)

[Black_Stark]

Thanks a lot guys. I had the same problem, but i dropped everything to the minimum (literally, because when i left two things in medium, it didn't work) and it worked.
Sadly, the Force Restart solution didn't work for me either.

[no_malarkey]

dropping everything down to minimum helped. force restart did not

[Reppy07]

Confirming that dropping graphics options allowed me to load the level.

Running with a 1080ti and 1440p monitor. Force restart and lower res didn't help.