Hi, I've recently reinstalled Freelancer and dipped my toes into Discovery, mainly by scooting around on sparsely-populated servers to get a feel for it all again, and I reckon I'm ready to actually have a shot at the full-blown gig. The problem I've got is that every time I try to join/start my character on the main Discovery server (regularly got around 90/255 people on), I instantly lose connection and get a message that the server might be suffering connectivity issues and that the problem's intermittent.
This is how I ended up flying around on other servers, trying to work out if it was something wrong on my end, but I've got no problem connecting to most other Discovery servers, only the one that, y'know, has all the people on it. Help please?
Do you have any other mods installed apart from Discovery?
Did you use a vanilla Freelancer when installing it?
Have you tried to connect with different accounts?
Reinstalling everything might help, since it looks like you get autokicked for having a 'bad install'.
Quote:Discovery 4.86 is the only mod I've got installed and the only tweaking I've done is the gls workaround.
Which one is this? Is it the one that you edit the freelancer.ini file (this is safe) or the one that installs a dll into dacom.ini (this is not safe).
You're almost certainly being kicked by the anticheat.
For reference - it's not necessary to install the GLS work around for discovery 4.86 and installing it can/will cause problems.
If you reinstall discovery, I expect everything will just work.
Proud member of "the most paranoid group of people in the community"
Quote:Discovery 4.86 is the only mod I've got installed and the only tweaking I've done is the gls workaround.
Which one is this? Is it the one that you edit the freelancer.ini file (this is safe) or the one that installs a dll into dacom.ini (this is not safe).
You're almost certainly being kicked by the anticheat.
For reference - it's not necessary to install the GLS work around for discovery 4.86 and installing it can/will cause problems.
Ah, it was the latter, swapping out the .dll, which, in retrospect, might have been a little naive of me. So try and reset it to default?