For the ones who will need to patch manually :
click on it at/after downtime

http://cdn1.eveonline.com/376700/EVE_Online_369870-376700_win.zip
or
http://content.eveonline.com/376700/EVE_Online_369870-376700_win.zip

I am using the Launcher and the patch downloading is on the way ! 46.6%

mine patched ok but when the game launches it says Inferno 1.0 Client Update #1 is advable and starts downloading but always freezes at 89% any clue how to get past this

Today was my first launcher failure ever. I fixed mine as detailed below:
...
As part of my debug I saw a 404 file not found error. If you're not seeing that then the Windows Firewall trick may not work for you.

Having same problem as ^

Downloaded both patches and extracted to eve folder. But the launcher tries to download the whole 'combined' patch from the server instead of 'creating' it from the already extracted .patch files.

Tried extracting just the first (1 gig) patch and launching. Still tries to re-download the whole 'combined' patch. :S

Do you guys have a tool to merge two .patch files together? Because I really don't want to re-download the whole 1.1gig on this connection.

Was posting in the other thread about my issues with an update loop. I was directed here and downloaded the right patch (376700-377452) but the launcher is doing a download again...

[IMG]http://i.imgur.com/kqWXo.jpg[/IMG]

I don't think this is right...

Hi guys,

I don't know what is going on here in my launcher... but look the name of the patch im downloading:

http://i.imgur.com/T698B.jpg

"EVE_Online_376700-369870_win.patch"

It's like I was doing a downgrade!

Since the released version, I have downloaded the complete executables in this adress:
http://community.eveonline.com/download/?fallback=1&

The files:
Executable
Payload 1
Payload 2

The versions that i downloaded was: 376700, 377452 and 377968.

The 377968 i downloaded now. And in these 3 options I got the same problem.

Can someone help me to resolve this problem?

Renaming patches is possibly the worst thing that can be done to get yourselves in game, although I can fully understand why you would want to do it. The patches contain a series of changes that must be applied to files in your installs, and what you're doing by renaming them is to trick the launcher into thinking it's up-to-date when in fact you're actually missing the latest bunch of fixes.

This could lead to anything from crashes of the game, to missing ship assets, corrupted graphics and all manner of strange behaviour.

Wouldn't have done it if the launcher was working in the first place. Perhaps make the launcher to able to recognize all *.patch files based on their actual size, MD5 checksum, etc.. (regardless of their different names). Worry not, maybe I won't need to do that again now that I realized that the launcher actually has export function to 'force' it to recognize patch files properly.

Having MD5's of patches would work if we were sure that everyone's installs were identical, however, we've seen that many people have corruption issues, leading to malformed assets on their clients, meaning that a patch between version A and B on your install might differ to a patch for version A and B on my install.

I'll look into improving the logic though, since it should be preferable to pull what usable data there is, in the patches provided before heading to the internet to download what's missing.

I also want to thank you for working with us on this. I know that it's incredibly frustrating to have these issues, and I can only stress that it's my number one priority to resolve these and other Launcher issues, so that we can all benefit.