You can switch focus to any running client from the launcher, or close it down. The launcher also keeps track of clients it has launched so you won’t accidentally launch on an account that is already logged.
The logins can be remembered between sessions if you want. You can set up logins to multiple accounts, and then launch multiple clients with one button click. This is somewhat simplistic, though – really all that is happening is you are selecting a settings folder to use for the client. A lot of the binaries and resources are the same between different servers so there is very little overhead in keeping binaries around for multiple servers.įor each client you launch, you can select a settings profile. The binaries are downloaded in a very similar way to how the resources are downloaded on demand in the client, using the same sort of CDN setup and the same shared cache. No more separate installs to run against Sisi or Duality.
This functionality if added to the launcher would PERFECTLY address the user requirements and alleviate the reported issue.Īny program that uses TCP to download data is by design going to saturate a network connection and impact other programs if otherwise unregulated.It supports launching against test servers Steam gives you the option of selecting a download rate, the ability to stop downloads while a steam game session is running, or for the rate to be in effect only at certain times. Steam is an excellent example of a program with application level configuration for download rates. Now to the second option, application level, or eve launcher configuration. Relevant ip addresses ( if a CDN is used, ip ranges, though if a CDN is used implementing at a network level with addresses will be technically more difficult and less effective if the CDN ip range frequently changes with network load )Īdvice on configuration to stay within the EULA ( so if my router does deep packet inspection to identify traffic and sets the download rate for those annoying station videos to 1b/sec that’s cool? great! ) Relevant ports(26000 is the eve client, but does the launcher download on this port also? Is it plain HTTP port 80 or HTTPS port 443?) Staying with the network level, or router based solution the user would have benefitted from some guidance on:. In neither case will updating the router firmware alter the behaviour of the TCP transfer between client and server unless there is a bug in the router firmware, which would mean programs other than eve launcher will cause connectivity issues. The network level ( which is the router ) or at the application level ( in this case, the launcher ) with a configuration setting. There are two levels in a network connection best able to address this. Saturation results in the chunks having a longer wait time for the cycle of sending, acknowledgment, and further sending of chunks, like cars stuck in peak hour traffic. On a saturated link, one program ( the launcher ) already using %100 of the bandwidth will have many more chunks acknowledged than a program that starts up after the link is saturated. To observers, this looks like a constant flow. If the programs in question use TCP for their connection, they are engaged in a process where the server sends a chunk of information, waits for the client to acknowledge the chunk has arrived, before sending subsequent chunks. The traffic from other programs may be able to reach their server but the response now has to be queued.
This symptom is very common with the prevalence streaming media services, where one program consumes %100 of Internet->Router bandwidth. The symptom described by the user was an impact to other program connectivity. This thread could have been moved to the feature request section right then and there. The user asked for an option to limit download speed. Someone with a information technology and technical services background I cringed at this unhelpful response.