Hello to everybody!
I'm fresh of registration and new to this game.
After having spent some time in reading several threads about rules and howtos, I've decided to install the Discovery mod.
Just near to my first adventure in this server, I'm stuck at the entrance.. *sigh*!
The disconnection occurs immediately after the login, with the welcome message under the notice "The connection to the server has been lost. Either [..]. Please try again later.".
My installation steps:
- freelancer into "D:\FL";
- nocd fix;
- update to 1.0.1 (otherwise I cannot get my PID);
- discovery mod (4).88.1 into "D:\FLDS";
I've tried to use the character names: "j0e.it", "j0e_it" and "j0eit" and two different internet lines: 1st ping 60, 2nd ping 170.
What's wrong?
Really thanks to anyone will help me.
[source of the problems: sandboxed in Comodo firewall; solved: don't virtualize it!]
Check to make sure nothing in your house is downloading. That is my biggest issue if someone is downloading then I get booted off the server no ifs or buts.
Hi freelancer knux,
no other people (I live alone) or backgrounded programs (all crons cut off by habit) eating my bandwidth.
Anyway I could give a try with another kind of net line.
Thanks for your reply.
Is the problem OK?
If not, did you try to add an exemption for dscace.dll DSAce.dll to your antivirus? This kicking right after log reminds me that problem...
Hello Benoit,
also with my firewall off, no way to stay logged into the server.
Already managed to launch with administrative rights, too.
Then, checked through DSL line: still loosing connection.
Of course, reinstalled again.
In vanilla mode, I've been able to play more than 1 hour inside the hosted Freelancer Universe; exited just few minutes ago.
At this point, I don't have other ideas.
Hey J0e.
Little correction: it's DSAce.dll not dscace.dll... sorry.
You need to go to your antivirus, and check to see if that file "DSAce.dll" is in your quarantined list. Sometimes, your antivirus might do it without you noticing it. Tell your AV that this file is fine and add an exception. You can also add the entire discovery folder as an exception in addition to be sure as others suggested it at the peak time of the DSAce.dll crisis.
Then , launch DSLauncher.exe in your game root folder, restore the DSAce.dll file in the parameter tab and try to log.