These forums have been archived and are now read-only.

The new forums are live and can be found at https://forums.eveonline.com/

Issues, Workarounds & Localization

 
  • Topic is locked indefinitely.
 

Alternative way of patching

First post First post First post
Author
Previous Topic Next Topic
Amsterdam Conversations
Doomheim
#201 - 2012-05-24 12:51:39 UTC
Samantha Utama
Caldari Provisions
Caldari State
#202 - 2012-05-24 13:27:39 UTC
The repair.exe fixed it finally after about the 3rd try.

But thanks for the patch rename trick. Didn't think to try that. I'm pretty sure that'll be quite useful in the future and would have saved me quite a few re-downloads.

It's almost as if we have to play this mini-game where we have to try to trick the launcher into letting us play, each time there's a big patch Blink
Bao Gong
Doomheim
#203 - 2012-05-24 13:33:58 UTC
Janica Erris wrote:
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...


When you have the new patch (manual download)
1 launch the launcher (of course it gonna try to download the new version, let it do what he wants, doesn't matter, go directly to step to)
2 launcher is downloading the new patch, don't care, go in Launcher Setting, Import YOUR Downloaded Patch, apply.
Urga Urhuga
USF
#204 - 2012-05-24 21:19:29 UTC
thanks again for all the advices.
once again ccp's launcher failed Roll
Haage
Aliastra
Gallente Federation
#205 - 2012-05-25 03:26:17 UTC
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?
v3nd3tt4
Underworld Alts Syndicate
#206 - 2012-05-25 06:02:56 UTC
Haage wrote:
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?


Sometimes the launcher download such patch file where the version name is inversed..
e.g: EVE_Online_364755-360229.patch , 425MB, 1st Inferno patch iirc..(notice the similarity with your patch version)

Alternatively, it is always safer and better to download the patch manually (refer to page 1) to avoid such situation. Be careful though, cuz there might be some typo error in the naming of the patch file that will make your situation worse.. Lol

But if you already have the 3 patch files in your EVE folder, try rename them like these (if they're different):

the 1GB patch file to "EVE_Online_369870-377452_win.patch"
the 21 MB patch file to "EVE_Online_376700-377452_win.patch"
the 14MB patch file to "EVE_Online_377452-377968_win.patch"

By right, the launcher will be able to recognize the patch files and applying them correctly.


-V
CCP Atropos
C C P
C C P Alliance
#207 - 2012-05-25 09:50:19 UTC
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.

I understand why you're doing it though; the Launcher fails and so you download the offline patches, in the hope that the Launcher can be told to apply them, Unfortunately this isn't the case. We didn't design it to apply sequential downloaded patches, assuming that it wouldn't happen. Obviously we were wrong!
v3nd3tt4
Underworld Alts Syndicate
#208 - 2012-05-25 11:40:58 UTC
CCP Atropos wrote:
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.


Yup, I was aware of the possible consequences of renaming the patches. Hence I always have a backup folders for changes I made. And if you refer to my posts, the renaming was necessary since it was (most likely) a typo on the patch name during initial release. So, I renamed 1 of them in order to force the launcher to recognize that the patch is already there in EVE folder.

Besides, it was under assumption that it was the same patch the launcher was trying to download again based on their size. And repair tool reports no missing stuff after that anyway. Big smile

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.

Note to others: So the renaming trick is NOT recommended, especially if you're not sure which patch file is the correct one to be renamed. If everything else fails and you try it anyway, always check your client with repair tool to ensure nothing is missing.
CCP Atropos
C C P
C C P Alliance
#209 - 2012-05-25 11:56:22 UTC
v3nd3tt4 wrote:
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. Oops
Salpun
Global Telstar Federation Offices
Masters of Flying Objects
#210 - 2012-05-25 11:57:37 UTC
CCP Atropos wrote:
v3nd3tt4 wrote:
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. Oops

What about pulling sisi info over so we do not have to down load the info twice?

If i dont know something about EVE. I check https://wiki.eveonline.com/en/wiki/ISK_The_Guide

See you around the universe.
Francisco Bizzaro
#211 - 2012-05-25 12:13:54 UTC
Would it be possible to create somewhere a running list of patches when they are applied, e.g. an evelopedia page with a 2-column list of the form:
[date] [patch-number]

I've used up enough of my own time patching, so would like to wait until things "stabilize" (for instance, more than 72 hours without a patch) before I bother again. At that point I may just download the full client to avoid this hassle. But I don't want to do it every day. So a list letting me know how often patches are appearing would be very helpful.

I hope the new launcher is very helpful to your internal processes at CCP, because from the end-user perspective it's really pretty disappointing how fragile the whole process has become.
v3nd3tt4
Underworld Alts Syndicate
#212 - 2012-05-25 19:05:49 UTC  |  Edited by: v3nd3tt4
CCP Atropos wrote:
v3nd3tt4 wrote:
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. Oops


Just here giving tips to help others that might have the same problem but you're welcome! Big smile

Anyway, I mentioned MD5 mainly cuz I know of other MMOs where their launchers use MD5s to verify the integrity of client files. If there are files found to be corrupted or missing then the launcher will download whatever files needed and then 'patch' whatever files needed to be patched.

Now, correct me if I'm wrong but it seems to me the patching will modify the corrupted files into a 'proper' one. Maybe taking out bits of corrupted ones and 'integrate' the old usable bits with the new ones. Not that I know how it actually works but in the end the clients will end up having identical files, as in name, MD5, actual size etc.. (mainly core ones, with exceptions such as user config files usually differ).

Perhaps use the same way of patching? Maybe not exactly as how they do it but main point is to make everyone's installs 'identical'. And the launcher will have no problem in recognizing patch files. May be a whole different way of patching but perhaps will be worthwhile in the long run. Just a suggestion though. Blink

In the meantime, try having some consistency with the patch names (the ones that launcher downloads and the ones for manual patching). That way, at least the launcher will download same patch name with the manual one to avoid confusion among players and the launcher itself. Blink
Fossor Wintersky
Ordinus Ursorum Cautorum
#213 - 2012-05-28 17:25:06 UTC
Again:

repairtool:

Traceback (most recent call last):
File "repairTool\progressPanel.pyc", line 82, in _TaskRun
File "repairTool\repairUI.pyc", line 97, in Start
File "repairTool\repairLogic.pyc", line 199, in Repair
File "repairTool\repairLogic.pyc", line 355, in Restore
File "zsync\zsync.pyc", line 393, in RestoreFolder
File "zsync\zsync.pyc", line 582, in GetFileRestorers
File "zsync\fileSync.pyc", line 124, in IsComplete
File "zsync\fileSync.pyc", line 107, in GetFoundRanges
File "zsync\fileSync.pyc", line 176, in _UpdateRanges
File "zsync\fileSync.pyc", line 275, in _DataChunkRecognized
File "zsync\fileSync.pyc", line 223, in _UpdateCurrentData
File "zsync\fileSync.pyc", line 233, in _ReadChunk
IOError: [Errno 13] Permission denied
Время работы: 0h10m40s
Carter Chamberlain
The Scope
Gallente Federation
#214 - 2012-05-29 12:55:18 UTC
Could we have the latest patch file please?
Bao Gong
Doomheim
#215 - 2012-05-29 13:11:42 UTC  |  Edited by: Bao Gong
of course:
http://cdn1.eveonline.com/379356/EVE_Online_377968-379356_win.zip
or
http://content.eveonline.com/379356/EVE_Online_377968-379356_win.zip

size: 19.2MB from the Client
size: 23.2MB form the Launcher

If the Launcher crashs... don;t close it.
Download the link, then import the patch with the Launcher Feature.

CCP ?

#213 :
same here.
1 Just kill EVE process (Launcher Client...)
2 Download manually the patch, restart the launcher, import the patch in.
If the launcher refuse to work, try this #187: https://forums.eveonline.com/default.aspx?g=posts&m=1341756#post1341756
GM Retrofire
Game Masters
C C P Alliance
#216 - 2012-05-29 13:22:44 UTC
Carter Chamberlain wrote:
Could we have the latest patch file please?



Patch links have been updated

GM Retrofire| Senior Game Master
Vladimiur
Caldari Provisions
Caldari State
#217 - 2012-05-30 11:09:50 UTC
how about uploading the update directly after the release i hate waiting for it while the rest of my corp already started doing stuff after downtime....... thanks
Rugisty
Wildly Inappropriate
Wildly Inappropriate.
#218 - 2012-05-30 11:45:39 UTC
Can we have the patch for manual download (again) please?
Fossor Wintersky
Ordinus Ursorum Cautorum
#219 - 2012-05-30 11:54:12 UTC
GM Retrofire wrote:
Carter Chamberlain wrote:
Could we have the latest patch file please?

Patch links have been updated


But launcher broken again:

Exception during UpdaterModule.Update
Traceback (most recent call last):
File "lib\update.pyc", line 764, in Update
File "lib\update.pyc", line 873, in _Update
File "lib\update.pyc", line 535, in Run
File "zsync\zsync.pyc", line 1284, in CreatePatch
File "zsync\zsync.pyc", line 1022, in GetFilesToRepair
File "zsync\zsync.pyc", line 969, in GetLocalFileSha1
File "checksum.pyc", line 357, in GetSum
File "checksum.pyc", line 199, in ChecksumFile
File "checksum.pyc", line 210, in ChecksumFileObject
File "core_utils.pyc", line 242, in ReadToCallback
IOError: [Errno 13] Permission denied
Locals by frame, innermost last:

http://pastebin.com/idSNyMTD
GM Retrofire
Game Masters
C C P Alliance
#220 - 2012-05-30 12:21:12 UTC
Rugisty wrote:
Can we have the patch for manual download (again) please?



Patch list has been updated.

GM Retrofire| Senior Game Master