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

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

EVE Information Portal

 
  • Topic is locked indefinitely.
 

EVE Online: Crucible 1.5 Issues

First post First post
Author
Previous Topic Next Topic
eocsnesemaj
Doomheim
#741 - 2012-03-16 13:02:12 UTC
Soooo yea still cant play eve... keeps dropping connection, my internet remains totally fine just eve craps out at random time intervals.... If im not able to play by the time chars need a top up on time im not going to do that until i find somewhere its been fixed.. no point paying if i cant play.
Marlakh
Sebiestor Tribe
Minmatar Republic
#742 - 2012-03-16 13:21:28 UTC
Day 1
Day 2
Day 3

At the end of Day 3, I successfully installed patch 351477, which allowed the client to launch and login successfully. I thought my troubles were finally over. Boy, was I wrong!

Day 4:

I fired up the client, and the Launcher proceeded to revert 351477 back to 350962! What happened afterward was Days 1 to 3 all over again! In other words:

1. Opened Eve Launcher as admin and clicked "Play".

2. Once client has launched, Incompatible (Protocol) message appeared beside the login text fields. I noticed that the client version on the top left read 350962. The Dialog box appeared titled "Ready to Update" and said "the update has been downloaded. The client will now close and the update process begin". Clicked ok.

3. Update setup progress dialog box appeared and appeared to finish with no errors.

4. Opened Eve Launcher again and clicked "Play".

Steps 1 to 3 then repeated itself, just like Days 1 to 3. As of this writing, the Launcher version still read v1.09. I hope v1.11 (which is supposed to be out today) addresses the problem.

Grroooooaaaannnnn.....
Jaden Plymoth
Iron Havok
#743 - 2012-03-16 13:39:39 UTC
Marlakh wrote:
Day 1
Day 2
Day 3

At the end of Day 3, I successfully installed patch 351477, which allowed the client to launch and login successfully. I thought my troubles were finally over. Boy, was I wrong!

Day 4:

I fired up the client, and the Launcher proceeded to revert 351477 back to 350962! What happened afterward was Days 1 to 3 all over again! In other words:

1. Opened Eve Launcher as admin and clicked "Play".

2. Once client has launched, Incompatible (Protocol) message appeared beside the login text fields. I noticed that the client version on the top left read 350962. The Dialog box appeared titled "Ready to Update" and said "the update has been downloaded. The client will now close and the update process begin". Clicked ok.

3. Update setup progress dialog box appeared and appeared to finish with no errors.

4. Opened Eve Launcher again and clicked "Play".

Steps 1 to 3 then repeated itself, just like Days 1 to 3. As of this writing, the Launcher version still read v1.09. I hope v1.11 (which is supposed to be out today) addresses the problem.

Grroooooaaaannnnn.....


I very nearly had this problem last night when my client crashed and I attempted to relaunch the launcher. The problem once again lies in win_launcherinfoTQ_inc.txt. When it calls
ClientUpdate:
BuildNumberInfoFile:
The value it is receieving back is the value for the old patch, where as its supposed to be the new patch. If you change the URL it calls with the same file, only with the right information on a seperate server and still have the .patch file for 350962 to 351477, you can fool your launcher into needing an update. The update process will fail, but the 'import' tool will work and you can import the .patch file to get your client up and running.
Alunis
Focused Annihilation
#744 - 2012-03-16 13:56:39 UTC
CCP Cascade wrote:
Alunis wrote:

Cause: CCP has decided to use a protocol that uses a UDP packet stream and has zero error correction while streaming the traffic to the end users. The problem is not with the UDP stream itself, it's with anything that does protocol filtering such as your router in the case it's doing SPI (Stateful Packet Inspection) filtering or many firewalls which do protocol filtering.


This just isn't true. We're using HTTP range requests and rsync over HTTP


rsync over HTTP is still UDP packet streaming. The protocol has no error correction bits and sends packets out of order. What I said *is* correct. A proper launcher should have been using a torrent stream and this would have avoided the problems you guys are causing. As it stands you're asking people to have to turn off vital security tools in order to get the game client. You had two months to address this issue when it was posted on the Sisi forums and nothing was done to take this issue seriously.

CCP Cascade wrote:

This however is true and we urge those who are running into problems with ESET NOD32 to contact customer support and ask them to release an update to the software.


ESET isn't the problem here. CCP is. What you fail to understand is that even if ESET sends a patch out you still have issues with SPI over routers which will look at rsync and throw up errors at it as well. When you are using a protocol that has zero error checking and can and does send packets out of order, do you sincerely expect that this is the end of your problems by asking all of the companies such as AVG, ESET, and Nortons to release patches to fix non-issues in their software?

You make this sound like it's just ESET that is having issues but as we've posted in this thread, it extends beyond ESET firewalls..

CCP Cascade wrote:

This workaround which was posted early morning on the 14th was to resolve various other issues people were experiencing and many have reported that this worked for them. Data corruption which is what a lot of people are reporting now can be the result of firewalls and non functioning routers and other causes which we are still investigating. We're very much trying to help people getting this issue and getting to the bottom of the problems they are experiencing.


You know, I understand that you guys are trying to address other issues as well. But let's tell people exactly what issue you *have* fixed with the patches you're coming out with. Let's stop assuming that you've fixed the problems people such as myself have had. I say that because people that are posting the same errors I and those like me have had, your people keep telling to do the same thing.. Reboot, do this and that, try to download the repair tool again.. blah blah blah.. It doesn't work because you don't have a fix..

In summary, stop taking credit for fixing things that WE the community came up with the workarounds for. Stop trying to blame the firewall companies because it's not them that made the mistake. It's CCP that made the mistake.. Stop using rsync, it's a UDP protocol and whether you're streaming it over HTTP or not, it's still not designed to send error free transmissions from one end point to another. SPI router filtering as well as firewall packages are doing their job. Use a torrent protocol which streams over TCP and has error correction bits in the packets.

Problem solved for *many* people.

Thanks for playing.
hiwil
Caldari Provisions
Caldari State
#745 - 2012-03-16 14:01:18 UTC
Well, now the launcher says client is ready, when i push the play button the old launcher screen pops up and nothing else happens, no eve just this stupid launcher. I have deleted all cashe files and reinstalled eve 3 times now. The eve launcher version is 1.09. I got training running out soon, get this crap fixed!
Jaden Plymoth
Iron Havok
#746 - 2012-03-16 14:09:25 UTC
hiwil wrote:
Well, now the launcher says client is ready, when i push the play button the old launcher screen pops up and nothing else happens, no eve just this stupid launcher. I have deleted all cashe files and reinstalled eve 3 times now. The eve launcher version is 1.09. I got training running out soon, get this crap fixed!



Have you tried launching eve.exe from the bin folder? THats the client itself and bypasses the launcher completely.
hiwil
Caldari Provisions
Caldari State
#747 - 2012-03-16 14:13:00 UTC
Jaden Plymoth wrote:
hiwil wrote:
Well, now the launcher says client is ready, when i push the play button the old launcher screen pops up and nothing else happens, no eve just this stupid launcher. I have deleted all cashe files and reinstalled eve 3 times now. The eve launcher version is 1.09. I got training running out soon, get this crap fixed!



Have you tried launching eve.exe from the bin folder? THats the client itself and bypasses the launcher completely.




Yeah i tried that, but nothing happens. Same issue as running it from the launcher. :(
Jaden Plymoth
Iron Havok
#748 - 2012-03-16 14:19:00 UTC
hiwil wrote:
Jaden Plymoth wrote:
hiwil wrote:
Well, now the launcher says client is ready, when i push the play button the old launcher screen pops up and nothing else happens, no eve just this stupid launcher. I have deleted all cashe files and reinstalled eve 3 times now. The eve launcher version is 1.09. I got training running out soon, get this crap fixed!



Have you tried launching eve.exe from the bin folder? THats the client itself and bypasses the launcher completely.




Yeah i tried that, but nothing happens. Same issue as running it from the launcher. :(


Honostly I'm not sure what to suggest at this point for you dude, its beyond what i've had to troubleshoot at this point. Only other suggestions I have are try running that exe in admin mode and compatibility settings. The only times my client has done what you're saying is when there has been a corrupted file somewhere and I wound up having to use the repair tool. That was before 1.5 though when repair.exe worked in full.
hiwil
Caldari Provisions
Caldari State
#749 - 2012-03-16 14:36:06 UTC  |  Edited by: hiwil
Jaden Plymoth wrote:
hiwil wrote:
Jaden Plymoth wrote:
hiwil wrote:
Well, now the launcher says client is ready, when i push the play button the old launcher screen pops up and nothing else happens, no eve just this stupid launcher. I have deleted all cashe files and reinstalled eve 3 times now. The eve launcher version is 1.09. I got training running out soon, get this crap fixed!



Have you tried launching eve.exe from the bin folder? THats the client itself and bypasses the launcher completely.




Yeah i tried that, but nothing happens. Same issue as running it from the launcher. :(


Honostly I'm not sure what to suggest at this point for you dude, its beyond what i've had to troubleshoot at this point. Only other suggestions I have are try running that exe in admin mode and compatibility settings. The only times my client has done what you're saying is when there has been a corrupted file somewhere and I wound up having to use the repair tool. That was before 1.5 though when repair.exe worked in full.



thanks for trying, my repair tool is completly broken, and i did install the latest and greates and placed it in the EVE folder (that was for CCP)
Marlakh
Sebiestor Tribe
Minmatar Republic
#750 - 2012-03-16 15:40:51 UTC
Jaden Plymoth wrote:

I very nearly had this problem last night when my client crashed and I attempted to relaunch the launcher. The problem once again lies in win_launcherinfoTQ_inc.txt. When it calls
ClientUpdate:
BuildNumberInfoFile:
The value it is receieving back is the value for the old patch, where as its supposed to be the new patch. If you change the URL it calls with the same file, only with the right information on a seperate server and still have the .patch file for 350962 to 351477, you can fool your launcher into needing an update. The update process will fail, but the 'import' tool will work and you can import the .patch file to get your client up and running.


Well, I couldnt locate the win_launcherinfoTQ_inc.txt file, but I did import the 350962 to 351477 patch file again, which forced the Launcher to reverse the reversion (lol) back to 351477. But then it also updated itself to v1.11. The client launched successfully after both actions, so not sure which was the one that solved it.

In any case, thanks for the tip. Just keeping my fingers crossed that there's no Day 5 of my problems Evil
CCP Donut Golem
C C P
C C P Alliance
#751 - 2012-03-16 16:02:16 UTC  |  Edited by: CCP Donut Golem
Marlakh wrote:
Jaden Plymoth wrote:

I very nearly had this problem last night when my client crashed and I attempted to relaunch the launcher. The problem once again lies in win_launcherinfoTQ_inc.txt. When it calls
ClientUpdate:
BuildNumberInfoFile:
The value it is receieving back is the value for the old patch, where as its supposed to be the new patch. If you change the URL it calls with the same file, only with the right information on a seperate server and still have the .patch file for 350962 to 351477, you can fool your launcher into needing an update. The update process will fail, but the 'import' tool will work and you can import the .patch file to get your client up and running.


Well, I couldnt locate the win_launcherinfoTQ_inc.txt file, but I did import the 350962 to 351477 patch file again, which forced the Launcher to reverse the reversion (lol) back to 351477. But then it also updated itself to v1.11. The client launched successfully after both actions, so not sure which was the one that solved it.

In any case, thanks for the tip. Just keeping my fingers crossed that there's no Day 5 of my problems Evil


We've include a fix in version 1.11 of the Launcher which should force to request non-cached versions of the info files in question. Please let us know if you encounter this issue again. Thanks!

Edit - Here's a list of the major fixes:
· Numerous fixes to the Launcher self-update mechanism
· Hardened patch importing and exporting
· Fixed an error where the browser process spawned by clicking links in the Launcher inherited the file handles of the Launcher itself, causing permissions conflicts while patching.
· Properly managing paths with a variety of unexpected characters such that the Launcher doesn't assume that a process is running from the folder under its purview.
· The Launcher needlessly held onto the handles of processes that it suspected were running from the directory under its purview. This has been corrected.
· Added logging of HTTP Headers such that we're better able to debug Firewall/Router/Antivirus interference.
· Forced the Launcher's embedded browser to log to the EVE/launcher folder, reducing interference with the patching process, and removing clutter.
· Changed the method by which we delete old files before they're successfully patched.
· Reduced the amount of time we wait for the Launcher to attempt to send logs to a hard limit of 3 seconds.
· We now request non-cached copies of all meta-data files from the web, which should reduce instances of the Repair Tool or Launcher erroneously patching to a previous version.
· The Launcher has been further hardened to closure during various stages of execution.
Nikuno
Atomic Heroes
#752 - 2012-03-16 16:26:42 UTC
Dear CCP

I am currently attempting to play your game. However it does not believe I have connection to the internet. Most curious since I am able to write this to you. Rebooting the computer hasn't helped either. So following the logic of the great Sherlock Holmes, since Eve sees no internet I must be using Voodoo to write this to you. On that basis can I request photos and hair/nail clippings of your Devs? I have some other Voodoo practices that I wish to try at this point.

'No connection could be made to the content server. Please make sure that your Internet connection is up and restart the Launcher.'
Jarnis McPieksu
Aliastra
Gallente Federation
#753 - 2012-03-16 17:15:52 UTC
Nikuno wrote:
Dear CCP

I am currently attempting to play your game. However it does not believe I have connection to the internet. Most curious since I am able to write this to you. Rebooting the computer hasn't helped either. So following the logic of the great Sherlock Holmes, since Eve sees no internet I must be using Voodoo to write this to you. On that basis can I request photos and hair/nail clippings of your Devs? I have some other Voodoo practices that I wish to try at this point.

'No connection could be made to the content server. Please make sure that your Internet connection is up and restart the Launcher.'


Wild guess; Firewall blocking the updated launcher?
PryMary
nul-li-fy
#754 - 2012-03-16 17:35:59 UTC  |  Edited by: PryMary
CCP Donut Golem wrote:
Marlakh wrote:
Jaden Plymoth wrote:

I very nearly had this problem last night when my client crashed and I attempted to relaunch the launcher. The problem once again lies in win_launcherinfoTQ_inc.txt. When it calls
ClientUpdate:
BuildNumberInfoFile:
The value it is receieving back is the value for the old patch, where as its supposed to be the new patch. If you change the URL it calls with the same file, only with the right information on a seperate server and still have the .patch file for 350962 to 351477, you can fool your launcher into needing an update. The update process will fail, but the 'import' tool will work and you can import the .patch file to get your client up and running.


Well, I couldnt locate the win_launcherinfoTQ_inc.txt file, but I did import the 350962 to 351477 patch file again, which forced the Launcher to reverse the reversion (lol) back to 351477. But then it also updated itself to v1.11. The client launched successfully after both actions, so not sure which was the one that solved it.

In any case, thanks for the tip. Just keeping my fingers crossed that there's no Day 5 of my problems Evil


We've include a fix in version 1.11 of the Launcher which should force to request non-cached versions of the info files in question. Please let us know if you encounter this issue again. Thanks!

Edit - Here's a list of the major fixes:
· Numerous fixes to the Launcher self-update mechanism
· Hardened patch importing and exporting
· Fixed an error where the browser process spawned by clicking links in the Launcher inherited the file handles of the Launcher itself, causing permissions conflicts while patching.
· Properly managing paths with a variety of unexpected characters such that the Launcher doesn't assume that a process is running from the folder under its purview.
· The Launcher needlessly held onto the handles of processes that it suspected were running from the directory under its purview. This has been corrected.
· Added logging of HTTP Headers such that we're better able to debug Firewall/Router/Antivirus interference.
· Forced the Launcher's embedded browser to log to the EVE/launcher folder, reducing interference with the patching process, and removing clutter.
· Changed the method by which we delete old files before they're successfully patched.
· Reduced the amount of time we wait for the Launcher to attempt to send logs to a hard limit of 3 seconds.
· We now request non-cached copies of all meta-data files from the web, which should reduce instances of the Repair Tool or Launcher erroneously patching to a previous version.
· The Launcher has been further hardened to closure during various stages of execution.



& with this it shows the: This program is NOT 64bit compatible please see your vendor for an updated program.

FFS sort this out CCP you are really starting to **** me off with this bull ****.

http://img215.imageshack.us/img215/7123/capturebtk.png
Alunis
Focused Annihilation
#755 - 2012-03-16 18:01:10 UTC
PryMary wrote:
CCP Donut Golem wrote:
Marlakh wrote:
Jaden Plymoth wrote:

I very nearly had this problem last night when my client crashed and I attempted to relaunch the launcher. The problem once again lies in win_launcherinfoTQ_inc.txt. When it calls
ClientUpdate:
BuildNumberInfoFile:
The value it is receieving back is the value for the old patch, where as its supposed to be the new patch. If you change the URL it calls with the same file, only with the right information on a seperate server and still have the .patch file for 350962 to 351477, you can fool your launcher into needing an update. The update process will fail, but the 'import' tool will work and you can import the .patch file to get your client up and running.


Well, I couldnt locate the win_launcherinfoTQ_inc.txt file, but I did import the 350962 to 351477 patch file again, which forced the Launcher to reverse the reversion (lol) back to 351477. But then it also updated itself to v1.11. The client launched successfully after both actions, so not sure which was the one that solved it.

In any case, thanks for the tip. Just keeping my fingers crossed that there's no Day 5 of my problems Evil


We've include a fix in version 1.11 of the Launcher which should force to request non-cached versions of the info files in question. Please let us know if you encounter this issue again. Thanks!

Edit - Here's a list of the major fixes:
· Numerous fixes to the Launcher self-update mechanism
· Hardened patch importing and exporting
· Fixed an error where the browser process spawned by clicking links in the Launcher inherited the file handles of the Launcher itself, causing permissions conflicts while patching.
· Properly managing paths with a variety of unexpected characters such that the Launcher doesn't assume that a process is running from the folder under its purview.
· The Launcher needlessly held onto the handles of processes that it suspected were running from the directory under its purview. This has been corrected.
· Added logging of HTTP Headers such that we're better able to debug Firewall/Router/Antivirus interference.
· Forced the Launcher's embedded browser to log to the EVE/launcher folder, reducing interference with the patching process, and removing clutter.
· Changed the method by which we delete old files before they're successfully patched.
· Reduced the amount of time we wait for the Launcher to attempt to send logs to a hard limit of 3 seconds.
· We now request non-cached copies of all meta-data files from the web, which should reduce instances of the Repair Tool or Launcher erroneously patching to a previous version.
· The Launcher has been further hardened to closure during various stages of execution.



& with this it shows the: This program is NOT 64bit compatible please see your vendor for an updated program.

FFS sort this out CCP you are really starting to **** me off with this bull ****.

http://img215.imageshack.us/img215/7123/capturebtk.png


This is what happens when the launcher is corrupted.

What happens when you try to run the repair.exe?
Jack Lagoon
Noble Sentiments
Second Empire.
#756 - 2012-03-16 18:07:40 UTC
Launcher gets to 14.4% for me and then throws this error
Quote:

Exception during UpdaterModule.Update
Traceback (most recent call last):
File "lib\update.pyc", line 528, in Update
File "lib\update.pyc", line 554, in _Update
File "lib\update.pyc", line 278, in Run
File "zsync\zsync.pyc", line 1210, in CreatePatch
File "zsync\zsync.pyc", line 947, in GetFilesToRepair
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 241, in ReadToCallback
IOError: [Errno 13] Permission denied
....


More to that error, mail me for complete output

Running repair tool gives

Quote:
(1/7) Downloading index: Initializing ...
(1/7) Downloading index: 100.0%, 585.49 KB/585.49 KB, 96.59 KB/s, 00m02s
(2/7) Hashing files: Initializing ...
Warning:
Traceback (most recent call last):
File "zsync\zsync.pyc", line 711, in ChecksumFiles
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 241, in ReadToCallback
IOError: [Errno 13] Permission denied
.... Missing block crap that it does

And when it reaches 93.3% it gives this error
Quote:
res\audio\Turrets.bnk, missing 166 out of 166 blocks
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 376, in RestoreFolder
File "zsync\zsync.pyc", line 565, 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
Total Runtime: 0h02m31s


Getting a little ticked off at this stupid launcher and not being able to play. I've been trying to launch these all as administrator, did the whole reboot thing to try to reset what files are open and nada. Any help on this would be nice
Mi Linn
Rock-Eaters INC
#757 - 2012-03-16 18:09:03 UTC
What?

OK let me get this straight... From now on or untill CCP programers figure out how to do there jobs I have to shut down my anti virus just to start Eve....Guys I love the game, but over the years you've had some dusyies on patch day's.....
What's your favorite Patch moment plz just one per post.
My favorite was the patch that deleted your autoexe file in the patch cleanup then rebooted the pc Cool that was classic!!
hiwil
Caldari Provisions
Caldari State
#758 - 2012-03-16 18:42:05 UTC  |  Edited by: hiwil
so where do i get this new mythical launcher at ver 1.11? When i launch it does not give me an option to download it. Of course this is the fix right?????

so i do some looking online for a manual download for the new eve client and guess what "all patching will be done thru the new EVE launcher" This is a friggin joke right?????

Fix this crap already!!
ARCHTURU5
The Scope
Gallente Federation
#759 - 2012-03-16 18:46:36 UTC
https://forums.eveonline.com/default.aspx?g=posts&t=80366

seriously ccp can the mac community, those of us able to download your launcher and update eve successfully, could we get some response as to why our frame rate has died and what you're doing about it. i mean i'm assuming the best, that you just lost the link to your above thread, which is apparently the thread for mac issues, so i'm posting it here for you to remind you since you seem to only be reading this one.

thanks in advance
Neo Agricola
Gallente Federation
#760 - 2012-03-16 18:53:40 UTC
Pos Notifications and Calendar Events are FUBAR.

See BUG Reports: 130 448; 130 479; 130480

Dont send Notifications when Towers run out of Fuel, shows Towers which arent here anymore a.s.o.

DISSONANCE is recruiting Members: https://forums.eveonline.com/default.aspx?g=posts&m=706442#post706442 Black-Mark Alliance Recruitment: https://forums.eveonline.com/default.aspx?g=posts&t=6710