Backstage - OOC Forums
General Discussion => General Non-RP EVE Discussion => Topic started by: Silas Vitalia on 28 Nov 2013, 13:49
-
Anyone else getting tired of new patches breaking your games? My luancher barely works, these auto patches constantly fail, I can barely get the game running now. :bash:
-
This has been the worst update since Trinity. For chrissake.
-
What happened exactly?
I have noticed that if the client shows you the 'need to upgrade' dialog after you clicked 'play', ie. inside the regular game client window, you need to quit the launcher before proceeding. It's annoying, but happens seldom enough that I can live with it.
-
After Rubicon launch the launcher crashed about 75% of the time.
The automatic patch downloads have nuked the game, repair tool not working, etc. had to download entire client for a fresh reinstall.... seems ok now but it's just been annoying.
-
I've been having a large number of socket disconnects.
-
Odd; aside from a large number of 6mb troll patches every day - which happened before Odyssey anyhow - I've not been having any particular problems.
-
Odd; aside from a large number of 6mb troll patches every day - which happened before Odyssey anyhow - I've not been having any particular problems.
Those are not troll patches. If you're seeing that, you're trying to start the client directly rather than going through the launcher. We've been having legit patches every couple of days to get stuff that didn't make it into the release or to add new features. See the patch notes (http://community.eveonline.com/news/patch-notes/patch-notes-for-rubicon).
Aside from the derpery where they broke the launcher on patch day, for which a workaround was VERY quickly provided, I've had no issues at all.
Have you tried turning it off and on again?
-
I've been noticing the onset of random memory leaks from time to time since I patched into Rubicon.
Oh well, at least it's not a boot.ini
-
Not had any problems or disconnects here, guess I'm lucky vOv
-
Nothing odd here, not even on the shitty laptop.
Do need to close/reopen launcher though after cluster reboots and some other odd mark of time.
-
Odd; aside from a large number of 6mb troll patches every day - which happened before Odyssey anyhow - I've not been having any particular problems.
Those are not troll patches. If you're seeing that, you're trying to start the client directly rather than going through the launcher. We've been having legit patches every couple of days to get stuff that didn't make it into the release or to add new features. See the patch notes (http://community.eveonline.com/news/patch-notes/patch-notes-for-rubicon).
Aside from the derpery where they broke the launcher on patch day, for which a workaround was VERY quickly provided, I've had no issues at all.
Have you tried turning it off and on again?
I know; I refer to them as 'troll patches' because CCP for some reason feels the need to deploy one every single day instead of just saving them up for a once-every-few-days or once-a-week larger patch.
-
It's called agile development, and it's not a new concept within CCP.
Yes the volume of patches has increased, but that is a positive, not a negative. Less strain on bandwidth is a good thing when it comes to rolling these things out, and since they are all in small packages it's very easy to roll back to the previous day if something goes awry.
Much better than their old approach of block releasing and then not being able to remember how their codebase even works.
-
It said socket closed, and now I can't get into game. Log in, select character, get black screen, get "socket closed".
launcher doesn't even start now. Says it's in offline mode, that the server is unreachable
eve forums/eve main site also unusable.
API also unusable.
Can connect with one character, but not another. Therefore, it's not a problem on anything that I can do anything about.
-
It's called agile development, and it's not a new concept within CCP.
Yes the volume of patches has increased, but that is a positive, not a negative. Less strain on bandwidth is a good thing when it comes to rolling these things out, and since they are all in small packages it's very easy to roll back to the previous day if something goes awry.
Much better than their old approach of block releasing and then not being able to remember how their codebase even works.
It's not harder the slightest to roll back to an older version, no matter how heavy a patch was... If the older version worked fine, you roll back to it, there is no reason it should not work fine again...
-
It's not harder the slightest to roll back to an older version, no matter how heavy a patch was... If the older version worked fine, you roll back to it, there is no reason it should not work fine again...
You have two options:
1. Roll back a large production patch which changed a large amount of things in order to fix what is broken.
2. Roll back a small production patch which changed a small amount of things in order to fix what is broken.
Which is better?
-
Gave up, went to bed, returned.
Still cannot log in. Black screen, socket closed.
Can't log into eve website to file a bug report, petition, or write on forums.
vOv
-
It's not harder the slightest to roll back to an older version, no matter how heavy a patch was... If the older version worked fine, you roll back to it, there is no reason it should not work fine again...
You have two options:
1. Roll back a large production patch which changed a large amount of things in order to fix what is broken.
2. Roll back a small production patch which changed a small amount of things in order to fix what is broken.
Which is better?
I still don't see the difference. They could roll back to the first beta versions of eve if they kept them...
The issue is not rolling back to older versions, the issue is to roll back ingame actions on a character sheet / assets / stats. The issue is not a technical one, the issue is a timeframe one. The more time spent with the new version, the more problematic it will be to roll back to an older one...
-
Gave up, went to bed, returned.
Still cannot log in. Black screen, socket closed.
Can't log into eve website to file a bug report, petition, or write on forums.
vOv
There's a haiku or two in there, desperate to get out.
-
It's not harder the slightest to roll back to an older version, no matter how heavy a patch was... If the older version worked fine, you roll back to it, there is no reason it should not work fine again...
You have two options:
1. Roll back a large production patch which changed a large amount of things in order to fix what is broken.
2. Roll back a small production patch which changed a small amount of things in order to fix what is broken.
Which is better?
I still don't see the difference. They could roll back to the first beta versions of eve if they kept them...
The issue is not rolling back to older versions, the issue is to roll back ingame actions on a character sheet / assets / stats. The issue is not a technical one, the issue is a timeframe one. The more time spent with the new version, the more problematic it will be to roll back to an older one...
It's not just timeframe Lyn, there's other practical issues: Firstly if you've patched something, you've changed the executed code, for an MMO that code has been executed in N machines of different configurations so the actual state of the code and data at the point of the rollback is virtually impossible to determine which means god knows what will actually happen in the process of the rollback unless the rollback consists of a clean install: you could have memory left unreturned to the stack, buffer overflow errors, code waiting for a response that will never come any of which could lead to fatal errors.
Second finding whatever forced you to roll back in the first place, I do a certain amount of coding as a hobby and I can tell you any piece of code longer than "Hello World" has bugs in it, if you want to design code for a nuclear plant you need a very special level of testing that tests even completely impossible hardware conditions and software problems that could never occur... just in case they do somehow. In any case actually coding something is the easy part, debugging it so it actually does what you want it to do is another thing entirely, especially if you're dealing with a logic error which a debugger can't detect (i.e. you *think* you've coded it to do X when it reality it will do Y: since the code is technically A-OK the debugger will ignore it and the code will compile fine, it just won't do anything useful) or a swallowed exception. The more you change inbetween code changes the more possibilities you have for the cause of your problem and the more time it takes to *find* the more time it takes to fix and the longer it stays broken.
-
Error -7 when loading url https://login.eveonline.com/Account/LogOn?ReturnUrl=
unhelpful, and still cannot either connect to eve, or use the eve website.
-
It's not harder the slightest to roll back to an older version, no matter how heavy a patch was... If the older version worked fine, you roll back to it, there is no reason it should not work fine again...
You have two options:
1. Roll back a large production patch which changed a large amount of things in order to fix what is broken.
2. Roll back a small production patch which changed a small amount of things in order to fix what is broken.
Which is better?
I still don't see the difference. They could roll back to the first beta versions of eve if they kept them...
The issue is not rolling back to older versions, the issue is to roll back ingame actions on a character sheet / assets / stats. The issue is not a technical one, the issue is a timeframe one. The more time spent with the new version, the more problematic it will be to roll back to an older one...
It's not just timeframe Lyn, there's other practical issues: Firstly if you've patched something, you've changed the executed code, for an MMO that code has been executed in N machines of different configurations so the actual state of the code and data at the point of the rollback is virtually impossible to determine which means god knows what will actually happen in the process of the rollback unless the rollback consists of a clean install: you could have memory left unreturned to the stack, buffer overflow errors, code waiting for a response that will never come any of which could lead to fatal errors.
Second finding whatever forced you to roll back in the first place, I do a certain amount of coding as a hobby and I can tell you any piece of code longer than "Hello World" has bugs in it, if you want to design code for a nuclear plant you need a very special level of testing that tests even completely impossible hardware conditions and software problems that could never occur... just in case they do somehow. In any case actually coding something is the easy part, debugging it so it actually does what you want it to do is another thing entirely, especially if you're dealing with a logic error which a debugger can't detect (i.e. you *think* you've coded it to do X when it reality it will do Y: since the code is technically A-OK the debugger will ignore it and the code will compile fine, it just won't do anything useful) or a swallowed exception. The more you change inbetween code changes the more possibilities you have for the cause of your problem and the more time it takes to *find* the more time it takes to fix and the longer it stays broken.
Uh... It's not a question of coding, it's a question of correct versioning (cf the version number displayed in every game menu). If your code is broken in a certain version, you don't release that version. If you didn't notice a glitch or a broken version, then you release it but will either have to quickly hotfix it or just rollback while fixing is being made on newer versions.
I don't know how CCP works. I grossly know that in my own experience a patch is nothing more than replacing older files by newer files. If you want to rollback, you replace the newest files by the older ones corresponding to the correct version.
Again, if an older version worked and if you roll back to it, it will use the same exact files and will therefore works as well as before.
Are you familiar with versioning and revision control (SVN, Git, etc) ?
-
I'll admit, no, I'm not, at least not in detail, I get a bit of the theory but without knowing more I probably shouldn't have commented. That's a bit above my level, sorry I think I misunderstood your conversation in the thread... serves me right for reading in a hurry whilst trying to run out the door... I'll withdraw the previous post (metaphorically, I'll leave it up for reasons of accountability) and apologise.
-
No problem... I don't think what you said is wrong or anything. Versioning precisely exists to prevent that kind of issues.
-
The issue isn't about whether it's easy to roll back, or the complexity of any bugs, or anything like that. Smaller patches are better because if a rollback is needed, there's less overkill and thus less time wasted for both client and server. It's also easier to track down the problem, as fewer changes have been made in any given patch.
-
Yeah
-
oh look another patch ruining my client.
Patch fail.
Repair fail, suggested I 'reinstall client'
ffs
-
Can we get more information on how your installation is set up? What sort of drive is it on? Is it on a whole drive, or a partition? Is it a RAID setup? SSD? Classic HDD? What is your internet servce, and how is your network setup? Wireless? Wired? What brand is your modem and router?
The frequency and regularity of your ruined clients suggest that it's something local to you, especially since people like me and others are not having any problems with patching.
-
I have my OS on an SSD for speedy boot time and put most of my files on a regular large HD. Eve included.
99% of patches have been mostly fine, Rubicon has just consistently failed upon using the launcher. ]
It's alright, gives me something to do for 3 hours while the client re downloads :)
-
I have my OS on an SSD for speedy boot time and put most of my files on a regular large HD. Eve included.
99% of patches have been mostly fine, Rubicon has just consistently failed upon using the launcher. ]
It's alright, gives me something to do for 3 hours while the client re downloads :)
Dumb question, but have you petitioned for tech support on this? You probably should.