F.E.A.R.
What Zombie? 10 OCT 2012 a las 10:53 p. m.
Disconnected From Server
I have researched this problem - no one ever came up with a real solution other than "It started working". I have tried since yesterday, verified the files - I get the same results with any of my previous 9 saves WTF? Disconnected From Server in single player mode? Yet I can start a new game and throw away 8 hours of game time - BS. This is FEAR not the expansions, I started exstraction point and it ran fine.
< >
Mostrando 1-13 de 13 comentarios
Mister Biztos 7 ENE 2013 a las 9:00 a. m. 
It happened to me when I've uninstalled F.E.A.R, or maybe you deleted a file wich was important ?
What Zombie? 7 ENE 2013 a las 9:40 a. m. 
Nope - none of the above, but something corrupted the save game files. I just finished playing through the entire game from start to finish, this time no problems. I would suggest that once you make sure at least one saved game file per level works and do not erase it until you have verified a working file on the next level. At least you should have a better chance of only having to go back a little way if the other files get corrupted.
foomanchoo25 22 ENE 2015 a las 4:42 a. m. 
HI guys IF no one has a fix yet try this!! IT works.
start Fear > go to the load save game option> select the saved games at the bottom should still point out saves from the beginning chapter at point of origin, if you usually quick save and dont do full save> load that stage> play around until the first checkpoint then press escape and select your latest quick save or auto save and continue to play where you left off. :D
Última edición por foomanchoo25; 22 ENE 2015 a las 5:01 a. m.
eartahhj | GamingHouse 10 ENE 2016 a las 5:20 p. m. 
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
foomanchoo25 12 ENE 2016 a las 5:48 p. m. 
Publicado originalmente por eartahhj:
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


-------------------------------------------------------------------------------------------------------------------------

Thanks for this mate, will try it :)

By the way, your rig is almost exactly like mine :D

Win10 pro R9 290x Sapphire, i7 4790k, 16 GB ram Cosair vengeance Red DDR3 1866mhz
𝕯𝖊𝖚𝖘𝓦𝖔𝖑𝖋 5 MAR 2019 a las 8:25 p. m. 
3
4
1
The screwing-all lil' nasy bastard is hidden in PERFORMANCES---> ADVANCED GC SETTINGS---> GRAPHICS---> TEXTURES RESOLUTION. Put TResolution on"minimum", load your game, then :

Just put your settings back to the top and kick it.

<:spacewolves:>
Última edición por 𝕯𝖊𝖚𝖘𝓦𝖔𝖑𝖋; 8 MAR 2019 a las 2:59 p. m.
GrrImAFridge 8 FEB 2020 a las 2:50 a. m. 
Publicado originalmente por Ðeus ✠ Wolf:
The screwing-all lil' nasy bastard is hidden in PERFORMANCES---> ADVANCED GC SETTINGS---> GRAPHICS---> TEXTURES RESOLUTION. Put TResolution on"minimum", load your game, then :

Just put your settings back to the top and kick it.

<:spacewolves:>

Just thought I'd say that this did the trick for me. I'm currently playing through the Perseus Mandate expansion and was getting the error every single time when transitioning from Interval 4 to Interval 5. Cheers. :)
~ First time i see this error messing that way even after the fix : there is also another way to do it, but less effective : do this fix, then fast-save meters from the transitory point. It also works, but randomly : u may have to try several time for this one to work.
Everytime you retry, move slightly closer from the transitory point and do fast-save just before reaching it.

Worked for me when i didnt use the main fix, but, as i said, it might take several tries.
McToffel 6 JUL 2021 a las 9:13 a. m. 
Publicado originalmente por Deus ✠ Wolf:
The screwing-all lil' nasy bastard is hidden in PERFORMANCES---> ADVANCED GC SETTINGS---> GRAPHICS---> TEXTURES RESOLUTION. Put TResolution on"minimum", load your game, then :

Just put your settings back to the top and kick it.

<:spacewolves:>

This solved my problem at Interval 8. Thanks! :cozybethesda:
patrixilentius 5 OCT 2021 a las 4:17 p. m. 
Publicado originalmente por 𝔻𝔢𝔲𝔰🔸𝕎ᴏʟꜰ:
The screwing-all lil' nasy bastard is hidden in PERFORMANCES---> ADVANCED GC SETTINGS---> GRAPHICS---> TEXTURES RESOLUTION. Put TResolution on"minimum", load your game, then :

Just put your settings back to the top and kick it.

<:spacewolves:>
None of this works for me.
Player333676 6 OCT 2021 a las 5:53 p. m. 
Allow the game to use more RAM (old games were limited to low RAM) by using Large Adress Aware[www.techpowerup.com] on the FEAR.exe

Here are all possible solutions for "Disconnected from server": https://www.pcgamingwiki.com/wiki/F.E.A.R.#Crashes
Última edición por Player333676; 6 OCT 2021 a las 5:54 p. m.
Varga 21 NOV 2022 a las 8:42 a. m. 
"Force Restart - On" fixed it
mcgt 9 NOV a las 11:09 p. m. 
Publicado originalmente por 𝕯𝖊𝖚𝖘𝓦𝖔𝖑𝖋:
The screwing-all lil' nasy bastard is hidden in PERFORMANCES---> ADVANCED GC SETTINGS---> GRAPHICS---> TEXTURES RESOLUTION. Put TResolution on"minimum", load your game, then :

Just put your settings back to the top and kick it.

<:spacewolves:>

Tranks you,
< >
Mostrando 1-13 de 13 comentarios
Por página: 1530 50