Issues, Workarounds & Localization

edit 2: OP follows but you can skip to my TLDR a couple posts down

---

This is the second patch day in a row my patch failed and I was asked to run repair.exe; here are my repro steps, as best as I can recollect them

edit: win7 x64

Open launcher, launch client
Leave client running overnight connected to TQ the day before patch day
Leave launcher open too
Upon cluster shutdown, client displays dialog 'TQ has shutdown, kthxbai' has 'Quit' and 'Restart' buttons

Note - I don't remember if I clicked Quit or Restart here

I am 80% sure I clicked restart; which brought me to my still-running launcher to re-enter my password as my auth token had expired. It is also possible that I quit and switched to my already open launcher window. I don't think I closed and reopened the launcher.

Anyway. After typing my password correctly the launcher launched the client without executing any patching (as far as I remember anyway?). I got to the client's splash screen (where it used to show sexy graphics) with an error 'Build incompatible protocol' and a message 'A 6Mb patch is available, you want to download it?'

I click yes, a patch downloads and executes (in the old school patcher, not the launcher), and fails.

I have not run repair.exe yet. I will find and attach whatever logs are around before doing so.
My launcher remained open through the patch process.
Right now the launcher says "Launch EVE ONLINE as: username" and has a play button (i.e. it remembers my correct password.)
Right now my launcher displays version 2.1.571330 in title bar.

Unable to find the patch log, I clicked 'Play' in my launcher a second time.

Again this launched the incompatible(protocol) version of the game.

This time the message says 'The update has been downloaded. The client will now close and the update process begin. Press 'OK' to continue.'

At this point I started a logserver. No lines appeared. The patcher opened, redownloaded the patch and got to step `7/7 Applying patch: Initializing...` and failed again.

This time I got the log for you:

Traceback (most recent call last):
File "patch_win.py", line 126, in module
File "zsync\zsync.pyc", line 407, in RestoreFolder
File "zsync\zsync.pyc", line 464, in ReconstructFiles
File "zsync\zsync.pyc", line 498, in ReconstructFile
WindowsError: [Error 5] Access is denied: 'f:\\games\\eve\\launcher\\launcher.exe'

u might wanna make sure the launcher is closed, if the patch is executed by something other than the launcher, or rethink the timing of how the launcher check auths, checks compatibility, patches, and launches the client

Restarting my launcher successfully patched and launched.

BUMP plz acknowledge before odyssey 1.1 devs

TL;DR;

-leaving a client on across downtime on a patch day
(i.e. connect before downtime, let TQ disconnect, wait till TQ is patched and running)
-leaving the launcher open too,
-clicking 'restart' in the "server disconnected" modal window in that disconnected client

Somehow the launcher launches the client without the launcher first checking for the patch.

At this point the client detects wrong version and offers to download an (often/always?) 6Mb patch.

This executes the traditional patch installer executable with a 7 step process. It does not warn or give me a chance to close the launcher.

Since the launcher is still running the patch executable crashes if it attempts to modify launcher files.

-NJ

Can you also make it work with hibernation? The old launcher used to detect patches when I came out of hibernation/regularly checked but since SSO it doesn't do that anymore requiring me to restart the launcher every day, just in case there was a patch :(

Small annoyance next to the inability to start multiple clients and logging them in simultaniously.

Any link for the patch?