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
Zmey Crafter
Tiny Crazy Corp
#561 - 2012-03-14 19:20:43 UTC
Launcher, launcher....

When bookmarks and other stuff be sorted again?
Michael Theon
The Scope
Gallente Federation
#562 - 2012-03-14 19:30:56 UTC
CCP Donut Golem wrote:
Michael Theon wrote:
CCP Donut Golem wrote:
Michael Theon wrote:
so to most of you, a small solution for today, reinstall the whole game manually and you can start it again out of the bin-file as it works yesterday, launcher still does not work, this will last until the next update,either the launcher is fixed then or you have to reinstall.

not perfect but it works for today
fly safe


Sorry you had to go through a full install. Do you recall the error you were having?



the update got stuck by the install of the launcher, got the same messages as a lot of the people already have postet in the forum. the repair got stuck with an error message
system is windows 64
the launcher does not get installed


Hi, can you try installing a full copy of the Launcher into your EVE client directory via the following: http://cdn1.eveonline.com/350962/EVEOnlineLauncherInstaller.exe and running eve.exe afterwards?



did not change anything, still the launcher is not working and i got the same error messages
Rose Makanen
Doomheim
#563 - 2012-03-14 19:32:37 UTC
CCP Zulu wrote:
Sabrina Sin wrote:
CCP TomB wrote:
Sabrina Sin wrote:
Just found more than two kinds of rats in the belts? That works like intended or is it a fault?


Yes, always been like that.


Then I've been playing something else the last years. I had only 2 kinds of rats in 1 belt e.g. supremacists and Obliterators but never more kinds in one spawn


I can safely say that it's always been like this, you can get mixed spawns with lots of different types/classes of NPC's though they're the same faction.


Lol I can safely say that in almost 2 years of ratting i have never face this. Now each class of every single pop has differents names . For exemple you can have a Malakim and Throne in the same pop.
But anyway no problem change is good ! Strange i have not seen this in the release notes though.
Castle cheesecake
Doomheim
#564 - 2012-03-14 19:36:45 UTC  |  Edited by: Castle cheesecake
can we have the option for manual patch downloads back please?

its finally working for me (the launcher) but i think that option would be much appresiated still

edit: spoke too soon, launcher stops and says it has error

gives me a list of stuff but cant seem to post it here since it has "html" code
Aineko Macx
#565 - 2012-03-14 19:46:25 UTC
Still severe screen flashing on ships spawning on grid (decloak, bridge, warp-in).

Additionally, graphics have started to flicker occasionally, especially Stargates.

iveeCore 3.0: The PHP engine for industrial activities and CREST library
zzyazoo
Republic Military School
Minmatar Republic
#566 - 2012-03-14 20:03:46 UTC
I am a vista 32 bit system and after reading all the posts see that most of you are win 7 64 bit, but for what it is worth I too had an initial error in loading the launcher. My first response was to turn off my antivirus program and when I tried again everything works okay. I did not hear anyone else mention the antivirus possibility of causing the problem.
Lucas Quaan
DEMONS OF THE HIDDEN MIST
TRUTH. HONOUR. LIGHT.
#567 - 2012-03-14 20:08:37 UTC
For reasons beyond the grasp of us mere mortals, items on the market are no longer sorted alphabetically, nor any other way it would seem. This is confusing and dumb. Please fix.
Xi 'xar
Rift Watch
#568 - 2012-03-14 20:10:30 UTC
Last night I managed to patch and get into eve.

Tonight, I'm currently trying to patch as follows:

"Creating EVE_Online_349998-350962"

The progress bar gets to 25% and then simply restarts at 1%. Been doing this for the last 10 minutes, so I'm rather confused...

Any suggestions?

http://herdingwolves.wordpress.com/
Castle cheesecake
Doomheim
#569 - 2012-03-14 20:10:50 UTC
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
Alunis
Focused Annihilation
#570 - 2012-03-14 20:11:04 UTC
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
#571 - 2012-03-14 20:13:51 UTC
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.
Shaden Nightwalker
Tryblium Sanguinis
#572 - 2012-03-14 20:14:09 UTC
"Neutron Blaster turret color will adapt to the racial style of the ship they're fitted to."

Does not work with Tech 2 Neutron Blasters mounted un Tech 3 Ships .
Castle cheesecake
Doomheim
#573 - 2012-03-14 20:17:35 UTC
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.
Lucas Quaan
DEMONS OF THE HIDDEN MIST
TRUTH. HONOUR. LIGHT.
#574 - 2012-03-14 20:20:02 UTC
CCP Donut Golem wrote:
Acthiliak wrote:
So why do I suddenly have to launch a launcher that adds zero features or functionality to my previous Eve experience, but goes a step further from being absolutely useless and actually becomes an annoyance because now I have to click extra buttons arbitrarily and the launcher doesn't close itself when I click Play, so yet another arbitrary click has to be made.

What was the point of this launcher?


Please check the Settings menu for an option to hide the Launcher if there is no update available.

Yeah, only that setting doesn't actually do anything.

The wording on that tab could use some work too. Saying "The EVE Launcher can be configured to only appear if an update is available, and to not automatically close when the EVE client is started" (emph mine) and then have a check-box to do the exact opposite, i.e. force it to close, is ass-backwards. It's a nice check-box, though.
Kashti Nada
Center for Advanced Studies
Gallente Federation
#575 - 2012-03-14 20:20:08 UTC
Roughly eleven times out of twelve patching EVE has proven to be a total clusterfuck. It's like they have monkeys for devs punching at the keyboard and when they manage to get something to compile through some incredible fluke they release it with no quality assurance whatsoever. So I wasn't surprised to find out patching the client failed...

What I want to know is whether it is safe to reboot my machine this time or has it been rendered unbootable.
Lovelocke
Deep Core Mining Inc.
Caldari State
#576 - 2012-03-14 20:20:48 UTC
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.




Just done this and the patch loop has stopped and launcher seems to be working! I'll post in a moment if it works.
Augustus Ogana
Aliastra
Gallente Federation
#577 - 2012-03-14 20:24:47 UTC  |  Edited by: Augustus Ogana
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.



PLAYERS: THIS WORKS.

CCP: PAY ... not whoever I said before but actually ALUNIS 1B ISK PLUS 3 FREE MONTHS

He/she just saved your incompetent apathetic butts.

EvE - the Linux of MMOs - now with occasionally-broken installers! :P
Alunis
Focused Annihilation
#578 - 2012-03-14 20:26:31 UTC
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.
Lovelocke
Deep Core Mining Inc.
Caldari State
#579 - 2012-03-14 20:29:51 UTC
ALUNIS'S SUGGESTION WORKS!

The ESET suggestion! Follow this, launcher ran and it updated! It works!!!!!!!!!!!!!!!!!!!!!!!!!
Jaden Plymoth
Iron Havok
#580 - 2012-03-14 20:30:30 UTC
Lovelocke 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.




Just done this and the patch loop has stopped and launcher seems to be working! I'll post in a moment if it works.


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.