Help. Can't stay connected.

[Veygaar]

So here's the issue I'm having. Hoping someone who's had the same issue can help. I have Windows 7 64 bit.

I've installed the update and log in. I can see the server. I can join the server. I see my list of ships and click on to jump into. I see my ship in-game for all of 1 sec then I get the standard Disconnect message.

Alley checked the logs and my DSAce is not communicating with the server.

I've tried adding exclusions to my Avast! AntiVirus for the DSAce.dll and DSAce.log. To the whole Disco Folder even. This did not work so I deleted Disco and the Original Freelancer. Uninstalled my Avast! AntiVirus, turned off Windows Firewall and restarted my computer. Then Installed Freelancer, Downloaded and Installed Discovery .88.1.

Ran everything as Admin.

Still getting same issue. Logging the ship and getting insta DC'd.

---

Veygaar for Admin Moderator 2013!!!

[Connor]

Have you tried logging in with any other accounts and characters?

---

[sindroms]

Are you behind a router?
Try setting port forwarding manually, just for the lulz.


These are the FL ones, not the FLServer ones.
2300-2400 UDP

EDIT: Though I suppose if it is something with dsace, that won't help.
Are you running the latest version of NET framework?

---

--------------
PSA: If you have been having stutter/FPS lag on Disco where it does not run as smoothly as other games, please look at the fix here: https://discoverygc.com/forums/showthrea...pid2306502
----------

[Veygaar]

I have the latest NET Framework. Re-installed it again last night to be sure.

@Snoopy: Tried multiple accounts. Tried creating a new account. Made a new ship. Logged in. Same issue.

@Spazzy: I haven't done anything with Port Forwarding... Alley said it wasn't a port issue. My Xfinity did have a Firewall so I turned that off and re-did everything again with the same result. DCing upon log.

Everything worked fine until this new update

---

Veygaar for Admin Moderator 2013!!!

[Alley]

Once again, until you test with a different computer using the same modem, we won't be able to know if the modem or the computer is the guilty one here.

---

Alley was right.

[Shaggy]

Alley alot of people are having this problem. I am, a few of the 5th guys are and a few LR- are that im aware.

---

[Cygnus7]

I also am on a Win7 64-bit machine, and was having similar issues yesterday.
I'd log in, see the character select screen, choose a character, and get to see about half a second of the docking bay interior before FL crashed to desktop. Happened repeatedly.
I checked my ping, drivers, .NET versions, discovery and FL install, etc and all were updated/clean.
I am using MSE for antivirus, and tried adding the entire Discovery directory (and DSAce.dll) to exceptions - but that didn't help.

Next, I tried changing the discovery launcher option from fullscreen to windowed mode...
Voila, worked like charm!
My problem seemed to be connected to running FL in fullscreen. No idea why.

I don't know if this will fix anyone else's issues, but it worked for me (so far at least).

[Grammaton]

Got the same problem. I tried everything from reinstalling to windowed mode. it just keeps on disconnecting me on every discovery server. i really have no idea what else to do. the server ping is 20. tried 3 accounts new ships and so on. nothing seems to work for me. even if i click on the launch to space icon fast enough. i get a loading screen and immediately the disconnect massage. i deleted all folders. completely downloaded everything again. didnt help. different graphic settings didnt have an impact. switching off the firewall didnt make a change either.

i dont want to give up trying, but i really dont know what do do.

[Traxit]

I had this sort of issue, always got disconnected after 1 second and getting banned if I continue to log in.

Surprisingly reinstalling my OS completely and formatting my hard drives did the trick and fixed the issue.

---

The best Video Game OST
Just Got Better

[The Savage]

Uninstalled my Avast! AntiVirus, turned off Windows Firewall and restarted my computer.

This might be the exact problem in here. I found out that certain AV software files are still present in the OS' guts and might be the issue, despite actual software being removed. You might need to format the system disc entirely and do a clean OS installation.

You may also like to avoid AV software in the future, having a passive scanner software instead - such as MBAM and do a scan every week. That's what I've been doing for nearly 5 years now, as I had bad experience with AV software which had been butchering my PC after three months.