EVE Search - Sticky:EVE Online: Crucible 1.5 Issues

All Channels

EVE Information Portal

Sticky:EVE Online: Crucible 1.5 Issues

» Click here to find additional results for this topic using Google

Monitor this thread via RSS [?]

Author	Thread Statistics \| Show CCP posts - 77 post(s)
Alunis Focused Annihilation Detrimental Imperative 0	Posted - 2012.03.13 17:16:00 - [1] - Quote I've posted about this very same problem with Sisi This patch wasn't ready to be deployed because tons of people had reported the issue that is causing the problem here but CCP failed to take proper notice So here it is once again CCP.. You screwed up and this same error has carried over from Sisi that we told you was happening in the first place. Idiots. FIX THIS
Alunis Focused Annihilation Detrimental Imperative 0	Posted - 2012.03.13 17:30:00 - [2] - Quote CCP Donut Golem wrote: Malkhuth wrote: How can we download the newest version of the launcher? Launching the game, the existing launcher, or the repair file is broken for me right now. The patch which delivers the Launcher can be found here: http://content.eveonline.com/349998/evepremiumpatch349998.exe. Please try downloading and running it again. If issues persist, please try the Repair Tool. This patch says it wants to install to the Sisi folder.. Are you telling us to install this to the Eve folder instead?
Alunis Focused Annihilation Detrimental Imperative 0	Posted - 2012.03.13 17:38:00 - [3] - Quote Using the repair tool gets this lovely error.. Exception in thread Thread-2: Traceback (most recent call last): File "threading.pyc", line 530, in __bootstrap_inner File "threading.pyc", line 483, in run File "zsync\readFromUrl.pyc", line 117, in DownloadPart File "zsync\readFromUrl.pyc", line 136, in _DownloadPart File "zsync\zsync.pyc", line 761, in callback FileSyncError: data corruption No handlers could be found for logger "zsync" Oh wait.. we've complained about this error on Sisi too...
Alunis Focused Annihilation Detrimental Imperative 0	Posted - 2012.03.13 17:38:00 - [4] - Quote CCP Topknot wrote: Some clients seem to be getting permission errors when the Launcher is trying to update a file that the client uses. This has to do with the privileges on the Launcher. We are working on an update for the Launcher that we will deliver as soon as possible. In the meantime, we suggest you try running the "Eve Online Launcher" shortcut as administrator (through right-click). If that doesn't work, try to use repair.exe to update your client. How is that going to help when we can't even install the client?
Alunis Focused Annihilation Detrimental Imperative 0	Posted - 2012.03.13 17:43:00 - [5] - Quote CCP Donut Golem wrote: Eli Williams wrote: Launcher stops downloading patch at 40% each time. Just been out for over 3 hours, came back and still at 40%. Restarted launcher and it got back to 40% downloaded (from 0% as it didn't resume at 40%) in a few mins. Then just stops again. Done this 5 times now. Where can I manually download the .patch file from and import it? Would be the easiest option but on the website there is no longer a download option for patches page, says I HAVE TO use the launcher. The .patch file is essentially a delta of your local client and a "master" on our servers. As such it's essentially install-specific. If you're having trouble with the Launcher, we'd recommend that you run it as administrator, or try using the Repair Tool. Hope that helps. Running the repair tool or launcher as admin does NOT fix the errors that we're posting. These are errors that were posted repeatedly on the Sisi forum regarding issues with people failing to be able to get on the test server. It's amazing that these issues were not addressed considering the number of people that were posting about this in the first place. I'm sure if you guys would bother to take a look, you'll see that I as well as others posted about the errors we were getting trying to connect to the test server. Administrator privs do NOT fix the issue. The repair tool does NOT fix the issue. Are you getting this? Look in the Sisi thread about this.. You'll see this was an error that was foreseeable had you guys taken the time to actually read the test forums.
Alunis Focused Annihilation Detrimental Imperative 0	Posted - 2012.03.13 17:59:00 - [6] - Quote CCP Donut Golem wrote: Alunis wrote: CCP Donut Golem wrote: Malkhuth wrote: How can we download the newest version of the launcher? Launching the game, the existing launcher, or the repair file is broken for me right now. The patch which delivers the Launcher can be found here: http://content.eveonline.com/349998/evepremiumpatch349998.exe. Please try downloading and running it again. If issues persist, please try the Repair Tool. This patch says it wants to install to the Sisi folder.. Are you telling us to install this to the Eve folder instead? For what it's worth, running this locally points at my main TQ installation. Pointing it at yours should be benign, it will simply re install the launcher. I'll try it but I'm a windows 7 user and I've been reporting errors regarding the launcher since SIsi started throwing fits and I was unable to get on there. So not sure that this is going to resolve anything. No matter what permissions I give it on Win7 it fails miserably.
Alunis Focused Annihilation Detrimental Imperative 0	Posted - 2012.03.13 18:09:00 - [7] - Quote kartofius al andalus wrote: the updater worked without any hazzle, but after accepting mission and going to the mission's system i don't have the expected 'warp to location' link http://prikachi.com/images/810/4517810g.png please, help :) You can't warp to where you're already at..
Alunis Focused Annihilation Detrimental Imperative 0	Posted - 2012.03.13 19:46:00 - [8] - Quote How long do we the paying customers have to wait for CCP to back this patch out? There were ample warnings about this error posted to the Sisi thread for a couple of months now. Why are we paying for developer stupidity at this point. It's not as if we didn't tell you about this problem repeatedly. There has been posts about Sisilauncher failing to wokr with these same errors. There were posts about the new launcher giving the same errors. There were posts about the repair tool not fixing the issues on Sisi on top of the fact that complete client downloads were not fixing the issue because they had to be patched as soon as you finished downloading and running the client. So how long do we have to wait for this patch to be backed out so the rest of us that pay for multiple accounts in some cases, can get in and play the game or is this where CCP says "Screw you" once again like they did last summer? What does it take? A Jita protest to get your bloody attention? Oh wait.. we can't protest in Jita because we can't bloody login let alone PATCH THE BLOODY CLIENT!
Alunis Focused Annihilation Detrimental Imperative 0	Posted - 2012.03.13 20:32:00 - [9] - Quote Mograthi wrote: Alunis wrote: How long do we the paying customers have to wait for CCP to back this patch out? There were ample warnings about this error posted to the Sisi thread for a couple of months now. Why are we paying for developer stupidity at this point. It's not as if we didn't tell you about this problem repeatedly. There has been posts about Sisilauncher failing to wokr with these same errors. There were posts about the new launcher giving the same errors. There were posts about the repair tool not fixing the issues on Sisi on top of the fact that complete client downloads were not fixing the issue because they had to be patched as soon as you finished downloading and running the client. So how long do we have to wait for this patch to be backed out so the rest of us that pay for multiple accounts in some cases, can get in and play the game or is this where CCP says "Screw you" once again like they did last summer? What does it take? A Jita protest to get your bloody attention? Oh wait.. we can't protest in Jita because we can't bloody login let alone PATCH THE BLOODY CLIENT! Lolz you assume that CCP actually reads stuff in test server feedback forum when it is blatantly obvious they don't given the number of times issues like this are pointed out by players but still make it to TQ and then the Dec's are befuddled about it. I assume that they don't give a damn because I was one of those people that posted about this problem repeatedly. Which begs the question CCP, why are we bothering to post this information to you on the test server forum threads if you aren't going to resolve the issues we are pointing out to you BEFORE you deploy this to TQ. There were posts to your facebook about this patch being bad, there were posts to the sisi forums about this being bad.. This patch is a failure. So how about backing it out NOW so that the rest of us can get back in and play until you figure out what you screwed up.
Alunis Focused Annihilation Detrimental Imperative 0	Posted - 2012.03.13 20:44:00 - [10] - Quote I'd like to point out the following thread. https://forums.eveonline.com/default.aspx?g=posts&m=879880#post879880 This is one of many forums threads about Sisi having issues that are related to this very problem today. So would someone at CCP mind telling me why any of us bother posting errors and problems regarding Sisi when you clearly ignore them. See the date when this problem was posted? The response from CCP was not even to the original posted. I'd like some answers here. Not about the problem but about why CCP isn't paying attention to our feedback so that problems like this don't happen on TQ. This issue could have been avoided on the live server today had our input been listened to in the first place. So I'd like some real answers from CCP as to what in hell we have to do in order to get them to start being accountable for screwing up a game we not only pay for but help them to debug and yet they ignore us and waste our time and our money with their developers who can't be bothered to READ and FIX errors that are POSTED.
Alunis Focused Annihilation Detrimental Imperative 3	Posted - 2012.03.13 21:58:00 - [11] - Quote CCP Cascade wrote: korondipeter wrote: What about 64 bit support? The issue you are experiencing has nothing to do with 64 bit support. There are currently 37 000 players online TQ, a lot of them are running on a 64 bit OS. What you are experiencing is something else. Have you tried rebooting your computer and then without starting any eve client or anything else, run the repair tool. The reason why you will have to reboot is to make sure that there are no locked files from other programs. Please let me know how that works for you. As opposed to over 50,000 players that were online yesterday playing, of which I was three. So how about you stop with the excuses and trying to make things sound perfectly ok since the majority of people are able to play while the rest of us are screwed as a result of an issue WE TOLD YOU ABOUT over and over and over again for MONTHS. Just stop posting until you fix the problem. All you're doing is pissing people like me off who took the time to be part of the process to debug the game and you lot couldn't be arsed to pay attention to in the first place. BACK THE PATCH OUT OR REFUND MY GAME TIME. Every day I am unable to play all three of my accounts is TIME I EXPECT REFUNDED TO ME. It's not my fault CCP didn't bother to listen to me when I replied about the problems on Sisi. It's YOUR FAULT for not taking the time to pay attention.
Alunis Focused Annihilation Detrimental Imperative 3	Posted - 2012.03.13 22:28:00 - [12] - Quote obviouscyno wrote: heres your 0.02 euros back for the time you have lost Euros have no value. payment in US Dollars please.
Alunis Focused Annihilation Detrimental Imperative 4	Posted - 2012.03.14 00:30:00 - [13] - Quote CCP Cascade wrote: As of 23:57 GMT we released a new Launcher and a new repair tool to resolve some issues that players have been experiencing during the initial deployment of Crucible 1.5. Those of you experiencing issues with the Launcher or updating the game, please follow these steps: 1.Reboot the computer. 2.Navigate to the EVE client install folder. 3.Run the Repair tool until it finshes. 4.Run eve.exe from the same folder We ask people to reboot their computer to make sure that there are no locked files or other processes running while running the repair tool. This would otherwise interfere with the repair tool and prevent the client from updating. Please let us know if this resolves the issues you are experiencing. How about telling us why this issue wasn't resolved on Sisi before it was deployed on to TQ. Please stop ignoring this issue. It was repeatedly posted about by people on Sisi and CCP failed to address the issue before deployment. When is CCP going to actually step up and take responsibility for it's failure to address player posted issues so that we aren't suffering downtime from the game now as a result of poor response from the Developers and CCP Management? Just wondering where those changes to how CCP is going to conduct itself are being applied here as promised after last summer's Jita Protest.. I don't see a whole lot of CCP taking responsibility nor do I see anyone answering my repeated questions on why this issue was ignored on Sisi before being deployed to TQ. Not that the CSM does anything worthwhile but certainly would like to see some accountability here and once again CCP is failing to communicate with the clients.
Alunis Focused Annihilation Detrimental Imperative 5	Posted - 2012.03.14 02:37:00 - [14] - Quote The only thing that worked for me was to download the entire new client and then launch the executable from the bin directory. The launcher is broken, the repair tool fails. Way to go CCP.. more FAIL.
Alunis Focused Annihilation Detrimental Imperative 5	Posted - 2012.03.14 20:11:00 - [15] - Quote Ok this is terrible to have to go through this many hoops in order to have fixed a problem that isn't a problem on my end but a poor lack of sight on CCP's part. Two things that had to be done in order to FIX the problems. ESET Security 5 had to be told to give exceptions under protocol filtering for ExeFile.exe, launcher.exe, and repair.exe. The other thing that had to be done was in my router I had to turn off SPI filtering. Stateful packet inspection has caused issues with rsync in the past under UNIX applications and it also seems that it can and will create issues for Eve's new launcher. These are not things I enjoy having to turn off because I do like to keep a properly secured system but these are the current exceptions that I had to make for Eve in order to get it working properly. One this was done I could run the repair client and the launcher worked. Again, I point out that these issues many of us posted on back in January on Sisi and we told CCP that the launcher in it's current state was not ready to be deployed. Until I can remove these exceptions for Eve and turn SPI back on I consider the client broken and a security risk due to poor coding and QA control.
Alunis Focused Annihilation Detrimental Imperative 5	Posted - 2012.03.14 20:13:00 - [16] - Quote Castle cheesecake wrote: okay so i downloaded the whole clientt, installed it, still same problem. repair.exe didnt work either this is going on day 2 ccp, come on, need some help here If you downloaded a completely new client you should be able to go directly into the bin directory and execute "ExeFile.exe" directly to launch the client provided that they have deployed the complete new client update in the latest build.
Alunis Focused Annihilation Detrimental Imperative 5	Posted - 2012.03.14 20:26:00 - [17] - Quote Castle cheesecake wrote: Alunis wrote: Ok this is terrible to have to go through this many hoops in order to have fixed a problem that isn't a problem on my end but a poor lack of sight on CCP's part. Two things that had to be done in order to FIX the problems. ESET Security 5 had to be told to give exceptions under protocol filtering for ExeFile.exe, launcher.exe, and repair.exe. The other thing that had to be done was in my router I had to turn off SPI filtering. Stateful packet inspection has caused issues with rsync in the past under UNIX applications and it also seems that it can and will create issues for Eve's new launcher. These are not things I enjoy having to turn off because I do like to keep a properly secured system but these are the current exceptions that I had to make for Eve in order to get it working properly. One this was done I could run the repair client and the launcher worked. Again, I point out that these issues many of us posted on back in January on Sisi and we told CCP that the launcher in it's current state was not ready to be deployed. Until I can remove these exceptions for Eve and turn SPI back on I consider the client broken and a security risk due to poor coding and QA control. how do you figure if that solution would work for others? im no computer genius, or even knowledgeable in any way. i heard about this turning off your antivirus, but i dont have "ESET Security 5" so i dont think thats the case for me. I'm stating that this is what I had to do in order to fix the problem on my end. I don't know that it will work for everyone however the two things I turned off or made exceptions for both watch the transport of streams inbound and it cured the errors because the firewall and the router firewall were no longer touching the traffic inbound from CCP. If you have a firewall on your system / AV product then it could very well be doing protocol filtering and you should turn it off and test to see if that fixes the issue you're having. As far as your router goes, if you don't know how to access it then you might need to contact the vendor or check their website and get direction on looking up if the router does have SPI filtering and if it is on by default and how to turn it off. That's the only way you can test my solution to see if it works for you. I was getting the same errors that everyone else was getting. So my guess is that because of how the new launcher streams the client updates that any type of filters correcting traffic can and will cause issues.
Alunis Focused Annihilation Detrimental Imperative 5	Posted - 2012.03.14 20:33:00 - [18] - Quote Lovelocke wrote: ALUNIS'S SUGGESTION WORKS! The ESET suggestion! Follow this, launcher ran and it updated! It works!!!!!!!!!!!!!!!!!!!!!!!!! Any firewall / AV Software that does protocol filtering as part of it's package (all the major AV and Security packages do), is looking for the same sort of errors that SPI filtering also watches for at the router level. So if you have a AV / Security package and/or a router that uses SPI filtering you need to turn these off for the moment. THIS IS ONLY A WORKAROUND. CCP should not be using a protocol that does NOT error check such as rsync. This is why everyone is having problems.
Alunis Focused Annihilation Detrimental Imperative 5	Posted - 2012.03.14 20:38:00 - [19] - Quote Jaden Plymoth wrote: Well, if this is truely the thing causing the patch loop, then I'm royally screwed as I dont have the authorization to change router settings where I'm at. Which is why the delivery system that CCP has picked to make their new launcher work is wrong in the first place. A great many people will not have access to the router or know how to make these changes. It's one thing to be able to turn off the firewall / security software but quiet another to dig into a router or get someone to change the router setup to fix this sort of problem.
Alunis Focused Annihilation Detrimental Imperative 5	Posted - 2012.03.14 21:16:00 - [20] - Quote Augustus Ogana wrote: So to recap two solutions to 1.5 launchers being totally broken on Windows, maybe/not specific to Win7-64: Problem: 1.9 launcher gets to 15% patch built, then starts again, over and over. Likely cause: Antispyware / firewall / antimalware / antivirus software is not allowing updates. Solution: For ESET 5: Go to Advanced Settings, Web and email, Protocol Filtering, Excluded Applications. If you've been trying like mad to fix it before now, then launcher.exe, eve.exe, and exefile.exe may already be in this list. Just check the boxes and hit OK. If not (those 3 above aren't in the list): Click Add button and add each, one at a time. For launcher it needs launcher.exe in the (eve)\launcher folder, not the shortcut or anything you may have downloaded from a forum link and moved to your eve folder. Ah, good times. Presuming you're at 1.9 you should fly smoothly now. If your launcher gets updated at this point, you may have to repeat the above steps before getting the launcher to say Play. If you don't have ESET 5, you may have a similar option in your security software, boiling down to "let this app act like there aren't *** living on my disk. Give it security douche immunity. This vampire is invited." Or you can take the bad, dumb, and easy risk of temporarily disabling security to just get it over with. If you have a separate firewall with the SPI filtering feature, it may also interfere. Thanks to Alunis for finding all this out.** Next one: Problem: Walked away like a rational person when 1.5 did a pratfall. Your probable situation is a mix of these problem/solutions: - all client settings may be gone (you need to find your pre-1.5 %appdata% bla bla eve_folder_tranquility folder; copy everything from its settings subfolder into your newer blabla_tranquility\derp\settings folder.) - launcher.exe, launcher shortcut, and repair are all acting stupid, throwing logs about missing extensions, broken shortcut, and/or pretending CCP is dumb enough to compile without 64 bit support. (you should run (eve)\bin\exefile.exe and hope for the best, it should work now, though you might have to come back for the other problem/solution above) - stuff I didn't run into (sorry, good luck) I think you forgot to mention a very large hammer or explosive device to be involved in this solution..
Alunis Focused Annihilation Detrimental Imperative 5	Posted - 2012.03.14 21:18:00 - [21] - Quote Stephen Ambrye wrote: i did all of this, and while the launcher went up to about 45% this time, it still encountered an error. Do you have a router and if so have you checked to see if it has SPI filtering turned on? If so, turn it off. SPI filtering does the same thing as ESET and other firewalls that protocol filter.
Alunis Focused Annihilation Detrimental Imperative 9	Posted - 2012.03.15 09:29:00 - [22] - Quote Once again I will post this for those of you getting the data corruption issue while trying to repair or update the software so that you are able to possibly get the game to work since CCP refuses to announce they botched in a big way. 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. Cure: You must disable in your router the SPI Filtering if it's enabled. If you use ESET / NOD32 you must go into the advanced options and add exceptions for Launcher.exe, repair.exe, and the eve.eve file as well. CCP is telling people to reboot and jump through hoops and all sorts of silly things. This isn't an issue you can resolve by rebooting it if you're geting those errrors. So try using the suggestions.
Alunis Focused Annihilation Detrimental Imperative 12	Posted - 2012.03.16 13:56:00 - [23] - Quote 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.
Alunis Focused Annihilation Detrimental Imperative 15	Posted - 2012.03.16 18:01:00 - [24] - Quote 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 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?
Alunis Focused Annihilation Detrimental Imperative 15	Posted - 2012.03.16 19:05:00 - [25] - Quote ARCHTURU5 wrote: 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 If you think they're really bothering to read these posts in earnest, they're only doing so when they think they can reply to something with some form of witty response that might fix an issue. If CCP had been reading player posts this disaster would never have gotten beyond Sisi in the first place.
Alunis Focused Annihilation Detrimental Imperative 15	Posted - 2012.03.17 00:11:00 - [26] - Quote Nikon Evenstar wrote: Alunis wrote: 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 . HTTP is not UDP so your comment makes no sense If ANY tool/appliance interferes with a running TCP connection by altering its payload it is broken, period. If the launcher uses HTTP range requests and they are being mangled by the antivirus software, the antivirus software is broken. The whole point of TCP is that the stream is guaranteed to be in order and without any loss of packets. The data is also protected by (admittedly weak) checksums I know from experience how extremely aggravating this is; I used to program back-end software for mobile apps, and carriers regularly screwed with the HTTP headers and sometimes even payload because their over congested networks had to use caching and all sorts of dirty NAT tricks to get internet to every mobile device... Some of them went as far as inserting ads into the HTTP stream, completely breaking clients which used HTTP as an RPC transport.. A workaround could be as simple as using a different TCP port for HTTP traffic so the router/av software doesn't start messing with it. Wrong.. You're not looking at the whole picture here. rsync IS UDP. Using a HTTP wrapper around a UDP protocol doesn't change the fact that the protocol being used by rsync is still a UDP protocol. A friend of mine, Pat Paddget, wrote a piece of software some years ago that does the same thing that they're doing. The software was called corkscrew. It allows you to take a process such as rsync, ssh, telnet, or any program for that matter that needs to access a foreign site via a proxy. The same mechanic is being used here. They're wrapping rsync through HTTP which yes, DOES USE TCP. But it doesn't change the fact that the stream being pushed through doesn't look correct to SPI and to firewalls with protocol filtering.. I have already talked to support at ESET about this issue and they came to the same conclusion that I did regarding this issue. So you can come to any conclusion that you like but I didn't fall off the truck yesterday and I do understand exactly what CCP has done to the point that when they said they were using rsync it confirmed why another friend of mine that had SPI filtering enabled on his router, why he was suddenly able to get the Sisi client to work a month ago while I was still having the issue due to ESET filtering the protocols as well. CCP should NOT be using rsync. Period. There is no reasons for them to use this protocol, wrapped or not, when torrents allow them to take the load off their servers on patch days and it has error checking available since it uses TCP properly.
Alunis Focused Annihilation Detrimental Imperative 15	Posted - 2012.03.17 00:14:00 - [27] - Quote Jack Cassidy wrote: raven666wings wrote: So far i have this list of users who aren't pleased with the reckless way CCP conducted this update leaving costumers deprived of service they paid for, and want the game time they lost back to their accounts. I'm gonna write and deliver the costumer support pettion tomorrow, so lemme know if you wanna sign it too or say if you want out of the list. Thanks raven666wings Ferdi Fauri Anita1 Endless Delirium Alunis Nicky Ormand Elsmere Tier'Fold Ulf Raben Zehel Frauz Callidus Dux RsA Larza Crosi Wesdo PryMary Pila Ferant Frickin Rhino Shannae Darkehart KeSya Claproth Rythm Jack Cassidy Ericdon hiwil eocsnesemaj Marlakh Nikuno Jack Lagoon Yeh man I want out. Im unhappy with CCP atm but not enough to chase up compensation. I don't want compensation from CCP.. I want CCP to wake up and start doing real QA testing and going through the Sisi forums properly and addressing major issues BEFORE they deploy a major release like this. Enough said..
Alunis Focused Annihilation Detrimental Imperative 37	Posted - 2012.03.19 16:34:00 - [28] - Quote Dear CCP. Thanks for the response to my petition and acknowledging this thread and the fix presented. However, the main issue that I have told you about in my petition still stands. First off telling me that you're working with ESET to try and find a solution to your problem as opposed to telling me the standard BS reason that you told everyone else being that you were hoping for ESET to release a patch to fix the problem confirms exactly what I've been saying all along in this thread. The problem is NOT with ESET or other AV / Firewall packages but within CCP's launcher code. Secondly, when you discovered this issue there was no rollback plan on the client and server which should have been done the minute problems started cropping up in the first place. You've completely alienated your Mac and Linux users in the midst of trying to figure out what you did to screw up a fairly decent number of your PC users atop of it all. This should have been the immediate course of action when the production release failed for such a widespread number of your users. Third, while I appreciate the private thanks from a GM on this issue, I'd much rather see all of the community that has participated in helping to find workarounds and help you be publicly acknowledged and a formal apology to the community for not being more forthcoming as promised by your CEO just last summer. Many of us have been very patient over the last week while you guys took off over the weekend and left us hanging and waiting for a fix. There has been no fix, no apologizes, and no acknowledgement that the launcher and it's use of the rsync protocol via http has caused issues. There has been little chatter about Mac and Linux users issues by anyone from CCP. There has been no announced intent to roll the launcher back until it's ready for consumer usage. In other words, CCP is acting like all is well on the home front while it's players are left thrashing in the wind. This is now how you treat customers. This is not how you treat loyal users such as myself that have been playing 8 years or longer on several accounts and have put up with one debacle after another during major patch releases. A little piece of advice. Get off your backsides and make good before you lose a lot of customers. The natives are restless and ready to revolt if you can't tell from the tone of the community.
Alunis Focused Annihilation Detrimental Imperative 39	Posted - 2012.03.20 17:37:00 - [29] - Quote Tidwald wrote: The easy solution is to move your EVE install to a location you have write access to. A better solution would be for the developers not to play fast and loose with file permissions... You should not follow the developer's advice when they suggest that you run the launcher as admin. What they won't tell you is that when you do this the launcher will alter the permissions on "C:\Program Files\ccp\EVE" to give everything write access to that directory. NOT A GOOD IDEA. QFT! CCP continues to ask people to do things that defy logic with regard to file permissions and firewalls. Turning off your firewalls to permit the game to update is just as bad an idea as playing with file permissions like this. :sarcasm: But hey according to several idiots in this thread, we should all just relax and not worry about our game time lost due to CCP's mistakes. We should all file petitions according to them. Let's see how well that goes right? :/sarcasm: Really sick of these issues and it's been over a week now with very little feedback from CCP.
Alunis Focused Annihilation Detrimental Imperative 41	Posted - 2012.03.21 23:50:00 - [30] - Quote Two more issues. Last night while trying to help my best friend setup his new laptop, we removed the AV software completely from the system as it was a factory install of Norton which is a piece of garbage out of the box. All patches to the OS were installed. Brand new Toshiba i3 Satellite running Windows 7 Home Premium 64bit. Eve installer failed repeatedly to work. Workaround: Created CCP\EVE directory, downloaded latest version of repair.exe - client installed correctly using the repair tool as the installer. From the installer to the launcher CCP just fails miserably. Second issue related to in game: Planetary Interactions Customs Offices. While transferring items via the customs office the transfer box will occasionally close completely upon hitting the transfer button. So glad CCP has taken such an active interest in the game. What a perfect piece of software they have created. At least the definition of Debugging remains the same. Process of removing old bugs and installing new bugs.

COPYRIGHT NOTICE
EVE Online, the EVE logo, EVE and all associated logos and designs are the intellectual property of CCP hf. All artwork, screenshots, characters, vehicles, storylines, world facts or other recognizable features of the intellectual property relating to these trademarks are likewise the intellectual property of CCP hf. EVE Online and the EVE logo are the registered trademarks of CCP hf. All rights are reserved worldwide. All other trademarks are the property of their respective owners. CCP hf. has granted permission to EVE-Search.com to use EVE Online and all associated logos and designs for promotional and information purposes on its website but does not endorse, and is not in any way affiliated with, EVE-Search.com. CCP is in no way responsible for the content on or functioning of this website, nor can it be liable for any damage arising from the use of this website.