* Patch 1.3.4 fails to fix game-breaking memory leak / FPS lag in PvP *

Gillysan · August 2014

Obscure wrote: »

Memory leaks and such aren't that important at this stage in ESO's development. Once ZOS has the build feature complete, they'll take care of the bugs their tester group has identified for them afterwards. The PC and MAC test platforms for ESO have very dedicated testers to find and catalog these bugs for them, so dedicated in fact we're even testing the business model by purchasing the product giving them a subscription fee. Based on the figures they have reliable feedback on even that model to determine what changes are necessary for the game at launch.

These things will certainly be taken care of prior to ESO's yet to be announced release date. Rest assured they'll have it fixed up and running smoothly for launch, so make sure you have your XBone or your PS4 ready to go! Soon the fruits of all our rigorous testing will be realized in the launch state build of ESO. We're almost there fellow testers!

#paidbeta #unpaidqualitycontrol

Somebody gotta start an in-game union guild. The Beta Testers Fighters Union. Also the Beta Testers Mage Collective.

Illumous · August 2014

dcincali wrote: »

apostate9 wrote: »

dcincali wrote: »

But

Barrier: Fixed an issue where the damage shield could be stacked multiple times

Was "fixed". Which wasn't an issue anywhere ever...

Except in all PvP everywhere...

Never once did i run into a group that beat us from having a barrier up.. This is a l2p issue just like rolling out of oil, moving out of the impulse bomb groups and for a short time the orbs...

Each barrier gives about 1.5k damage shield. All three versions of Barrier could stack on top of each other (Barrier, Reviving Barrier, and Replenishing Barrier). This made the total damage shield with all three stacked about 4.5k. This was a major part of the impulse train strategy that made it almost impossible to stop (especially with the Rapid Maneuvers, Heals, and constant Purges).

Warraxx · August 2014

ZOS_GinaBruno wrote: »

Just to keep you all in the loop, we should have a better idea of where this stands tomorrow morning. Hang tight until then, and thanks for your patience!

regards,
Captain of the Titantic

Fix't

fromtesonlineb16_ESO · August 2014

NerfEverything wrote: »

ITT: People with no idea how their computer works throwing around the term "memory leak"

LOL, clueless people are clueless .. guess ZOS have no idea either then ...

ZOS_GinaBruno wrote: »

Hey guys, just wanted to give you all an update on this. We have identified the source of the memory leak, and are currently testing the fix for it now. We'll get this rolled out as soon as possible!

... try posting something useful next time perhaps?

Or better still, keep silent.

RoyMallis · August 2014

Complaining about something (regardless of how legitimate the complaint) without offering a solution is just whining.

I see most people calling for ZOS to fix this immediately. This implies that you seem to believe they are doing nothing at the moment, which given the severity of the issue is an absurd conclusion to come to. They get it, you can't enjoy they game as it is. Honestly though, coming on here and crying about it and making impossible demands of them isn’t doing anything to get them to resolve the issue any faster. You are being of zero benefit to anyone. Instead if you were to request some substantial information on the issue and some specifics of what is being done to resolve it (even if it’s some over our head, game making mumbo jumbo) would be a far more understandable request than: “FIX IT NAOW!!!” *insert gamer rage aura*

SirenofEntropy · August 2014

RoyMallis wrote: »

Complaining about something (regardless of how legitimate the complaint) without offering a solution is just whining.

I see most people calling for ZOS to fix this immediately. This implies that you seem to believe they are doing nothing at the moment, which given the severity of the issue is an absurd conclusion to come to. They get it, you can't enjoy they game as it is. Honestly though, coming on here and crying about it and making impossible demands of them isn’t doing anything to get them to resolve the issue any faster. You are being of zero benefit to anyone. Instead if you were to request some substantial information on the issue and some specifics of what is being done to resolve it (even if it’s some over our head, game making mumbo jumbo) would be a far more understandable request than: “FIX IT NAOW!!!” *insert gamer rage aura*

What you have said is fair, however, most people just wanted to hear something from them regarding whether it was even being looked into or not. They have now given us some information that the problem has been found and they are working on a fix, so the anger and angst on the forum regarding it has calmed considerably. Of course there's still going to be a few people who didn't read any of ZOS's comments that are going to come to the forum and rage.

In one of my earlier comments in this thead I did actually ask if Gina (or another team member) could give us some information regarding the source of the leak, because I am genuinely curious about it. Whether or not they give us those specifics, though, is another matter.

Some of the people who were getting really frustrated over this were just getting sick of hearing other people tell them "it's your computer" when in this case it clearly was not. This problem wasn't a simple case of "should have read the recommended specs before you bought it", but rather a suddenly emerging issue for many people who, prior to the last update, were able to play their games with absolutely no issues at all.

In addition, I think it's completely fair for people who are paying a sub fee for a game to be upset when it is unplayable. Most of the really angry "fix it now" comments came before ZOS had said a single word on the issue.

LunaRae · August 2014

ZOS_GinaBruno wrote: »

Hey guys, just wanted to give you all an update on this. We have identified the source of the memory leak, and are currently testing the fix for it now. We'll get this rolled out as soon as possible!

Glad to hear, hope it makes it for Thursday's reg patch time.

Elsonso · August 2014

SirenofEntropy wrote: »

What you have said is fair, however, most people just wanted to hear something from them regarding whether it was even being looked into or not. They have now given us some information that the problem has been found and they are working on a fix, so the anger and angst on the forum regarding it has calmed considerably. Of course there's still going to be a few people who didn't read any of ZOS's comments that are going to come to the forum and rage.

Yes. After all, it has not been a secret that they have been working on this issue since the middle of last week.

We all knew that once they finished their investigation, we would hear about it. Now that we know they have a fix, we know that once it is ready to go we will hear about when they plan to deliver that fix.

Reiterpallasch · August 2014

I'm fairly certain none of them play their own game, or else some of this stuff would be fixed so much faster than it is now.

dharbert · August 2014

Reiterpallasch wrote: »

I'm fairly certain none of them play their own game, or else some of this stuff would be fixed so much faster than it is now.

^ This.

How, as a group of developers, can you create a patch and test it out on your servers and NOT notice that you are getting kicked out of PvP every couple of minutes?

Unless, of course, you didn't test it out in the first place....

Elsonso · August 2014

Reiterpallasch wrote: »

I'm fairly certain none of them play their own game, or else some of this stuff would be fixed so much faster than it is now.

I am certain that they do play the game, but it may be on a private internal server.

dean_steusloffub17_ESO · August 2014

lordrichter wrote: »

Reiterpallasch wrote: »

I'm fairly certain none of them play their own game, or else some of this stuff would be fixed so much faster than it is now.

I am certain that they do play the game, but it may be on a private internal server.

Can I go play on that one, then? It must be working flawlessly.

Xsorus · August 2014

dharbert wrote: »

Reiterpallasch wrote: »

I'm fairly certain none of them play their own game, or else some of this stuff would be fixed so much faster than it is now.

^ This.

How, as a group of developers, can you create a patch and test it out on your servers and NOT notice that you are getting kicked out of PvP every couple of minutes?

Unless, of course, you didn't test it out in the first place....

Because it wasn't every couple minutes? more like once an hour.

SirenofEntropy · August 2014

dharbert wrote: »

Reiterpallasch wrote: »

I'm fairly certain none of them play their own game, or else some of this stuff would be fixed so much faster than it is now.

^ This.

How, as a group of developers, can you create a patch and test it out on your servers and NOT notice that you are getting kicked out of PvP every couple of minutes?

Unless, of course, you didn't test it out in the first place....

Like the guy above said, they probably play/test the game on some private internal server. If the memory leak/crash is being triggered by the number of players on the screen, then they probably aren't seeing the issue on their end.

What they should do is investigate reported bugs and performance issues by logging into the same servers that we use, so they could see for themselves what we've all been talking about.

IKilled007 · August 2014

ZOS_GinaBruno wrote: »

Hey guys, just wanted to give you all an update on this. We have identified the source of the memory leak, and are currently testing the fix for it now. We'll get this rolled out as soon as possible!

Will this fix affect Macs too?

onlinegamer1 · August 2014

ZOS_GinaBruno wrote: »

Hey guys, just wanted to give you all an update on this. We have identified the source of the memory leak, and are currently testing the fix for it now. We'll get this rolled out as soon as possible!

Why are you hotfixing Trial loot (something that doesnt CRASH THE GAME), but NOT hotfixing this ?!?!

Elsonso · August 2014

SirenofEntropy wrote: »

What they should do is investigate reported bugs and performance issues by logging into the same servers that we use, so they could see for themselves what we've all been talking about.

I am sure that they do.

Pucko82 · August 2014

after hotfix i am stuck on Login-loadingscreen. /facepalm

Merlin13KAGL · August 2014

WebBull wrote: »

LunaRae wrote: »

Haven't been experiencing nasty lag, per se - but definitely crashing a LOT more than usual in Cyrodiil. Everyone in my group crashes at least 4-5 times in a 4-6 hour session, with no notable event. Can happen at anytime for no apparent reason.

It happens for the reason listed in the title of the post, memory leak. As soon as you get around 3.5gb mem .....crash incoming. You can monitor and avoid it by logging out and back in around 3gb mem.

This needs to be Priority #1 fix.

@LunaRae, yes to the crashing. Repairs don't find anything.

@Webbull, not automatically the cause of the crash. I'm running 16Gb on the system, so while it's not ideal, it's not going to take my system or the process down at 3.5 Gb.

It varies considerably, and it's not about activity in the area or time in play.

trustcotraptb14_ESO wrote: »

Massive skill lag / unable to fire ULT
Skills not working as intended / AoE abilitys not hitting anything
Character getting stuck mid combat, unable to move - must relog to fix
Unable to enter/exit doors - E does nothing
Client crashes very frequently
Server rollbacks

These are the major issues I've encountered since resubbing a week ago.

The game is still a buggy train wreck.

@trustcotraptb14_ESO, all of these, all as my love for Cyrodiil was starting to develop.

It's one thing to get your butt handed to you in a fight. It's another to go catatonic while observing the process because nothing responds.

Wicked delays or non-response to skill fires, weapon swaps, and targeting crosshairs that show I can fire but does not complete the action. Nothing like targeting someone on the wall and thinking you've blasted them for the last 3-4 seconds and wondering while their health never drops.

I've had this the worst in Cyrodiil (Chillrend), but also in Cave of Trophies (Coldharbor) last night.

May as well have 'Kill me' tattooed on my forhead.

Elsonso · August 2014

Merlin13KAGL wrote: »

@Webbull, not automatically the cause of the crash. I'm running 16Gb on the system, so while it's not ideal, it's not going to take my system or the process down at 3.5 Gb.

It varies considerably, and it's not about activity in the area or time in play.

On the first point, it will not take your computer down because that is not how Windows or Mac works. The process can go down, no matter how much memory you have. ESO will crash on your system when it gets into the last 1/2 GB of the 4GB of space that it can access.

On the second point, you don't know that, and I am fairly sure you are wrong. I think the longer you play the more likely to get an out of memory crash. I also think that it is made worse by things around you, either textures or sounds, that increase when there is more activity in the area.

For the record, I think this is an oversized texture cache related to dyes. I think that the game caches outfits used to display dyed armor on people and NPCs around you. I think that the cache is getting too large.

However, this game does goofy things with audio, so I am not discounting the idea that something bad is happening in the audio subsystem.

twev · August 2014

RoyMallis wrote: »

Complaining about something (regardless of how legitimate the complaint) without offering a solution is just whining.

<snip>

I'm rather confidant from my experience with the gaming community that there ARE many in the player community who COULD offer solutions and code solutions.

Just as soon as they have access to the source code, and someone on the inside with qualifications was listening.

Since that ain't gonna happen any time soon, and considering all the bug reports from the free beta-beta that were never addressed, than the army of players NOT offering solutions on fixes for this paid beta is about normal.

And opining that players without solutions under these circumstances deserve your denigrating scorn is just terrific arrogance and pomposity.

Thechemicals · August 2014

onlinegamer1 wrote: »

Please hotfix this memory leak asap. We can't wait another week for a fix.

I hate to call it, but he is right. The crashes and now sudden slow motion lag is extremely frustrating and this patch doing nothing about it makes me a bit annoyed now as well. Your first priority should always be stability of the game and bug control. Everything else....to include trivial things like....fixing stacked barrier shields seems like youre micromanaging too much.

Have management consolidate the teams working on specific issues,"that arent a priority" and get them to team up in fixing the stability and bugs and other high priority things. In fact... making game changing changes like the barrier stack removal and increasing battle bonus 10% DURING A TIME that is experiencing heavy crashes and stability problems, SHOULD not even be applied until the main problem is fixed. Barrier has been stacking since release people.... no reason you had to do it now.

onlinegamer1 · August 2014

ZOS_GinaBruno wrote: »

Just to keep you all in the loop, we should have a better idea of where this stands tomorrow morning. Hang tight until then, and thanks for your patience!

@ZOS_GinaBruno
Do the words "as soon as possible" mean to you, what they mean to us? a.k.a. Hot Fix?

Its "tomorrow". Update please?

emeraldbay · August 2014

onlinegamer1 wrote: »

ZOS_GinaBruno wrote: »

Just to keep you all in the loop, we should have a better idea of where this stands tomorrow morning. Hang tight until then, and thanks for your patience!

@ZOS_GinaBruno
Do the words "as soon as possible" mean to you, what they mean to us? a.k.a. Hot Fix?

Its "tomorrow". Update please?

Yes, I'm more than ready to stop crashing every few hours.

stefan.gustavsonb16_ESO · August 2014

The only solution I could possibly offer as an end user is "please hire some better programmers", but that won't fix the problem in the short term, so it would not really be helpful at this point. They just need to find a way to get their current development team to shape up, fix the game-breaking bugs and stop creating new ones, and I'm pretty sure they don't need me to tell them that.

dean_steusloffub17_ESO · August 2014

ZOS_GinaBruno wrote: »

Hey guys, just wanted to give you all an update on this. We have identified the source of the memory leak, and are currently testing the fix for it now. We'll get this rolled out as soon as possible!

Since some things are rolled out to the PTS (paid test server) without being tested properly, can you just go ahead and roll this out right meow, anyway?

We'll let you know whether it's working or not, as per usual.

Darlgon · August 2014

Gina Thanks ffor the updates, even tho admittedly, I am here to see if its "tomorrow morning" yet.

For some of the more.. upset... posters, memory leaks are old hat to a lot of gamers. I have seen them in almost every game.

How do you manage them? A few basic things I have had to learn over the years:

1. Reboot your whole computer, at least daily, and especially after a game crash, as Windows sucks at clearing a crash out without a reboot. Each time you start the game client, it takes up a set amount of memory, but Windows does not always clear out what was there before,, so it adds up.
2. Some games, and I think ESO is included, starts a mini-instance of the game, for lack of a better term, each time you change to an alt, to make them load faster. So, if you have logged in and out moving stuff around, quit game and then restart the launcher, if not a machine reboot to control.
3. I see people saying, "dont repair the game". That is just.. wrong. A game crash is an ABEND, ABnormal END of a program. Even if a repair finds nothing wrong, its better to repair to check to make sure all the delicately balanced files and databases match what is on ZoS servers.
4. Be patient. Finding out what causes memory leaks takes time. It could be server, client, client AND server, computer specific, Windows version specific, lack of patching Windows, due to a recent Windows patch, or many other things.
5. Lastly, if you want it fixed, make sure to type out what you were doing and hit the "Submit" button on that crash report that pops up. The more data they have, the quicker they can nail down the causes.

AzureButterfly · August 2014

I'm sure it has something to do with either the weapon-slot caching or armor textures - and I'm leaning heavily towards the former. My RAM usage shot up to 95% when I was rapidly switching weapon sets in a fight. The program is probably storing unneeded data every time you swap until it has twenty copies of "this guy has a sword in weapon slot one!"

I hope the programming guys don't have too much trouble fixing it. I'd really like to play ESO. :C

c0rp · August 2014

Its now afternoon and there are no updates.

onlinegamer1 · August 2014

c0rp wrote: »

Its now afternoon and there are no updates.

QFT, can we get an update on this?

*** Patch 1.3.4 fails to fix game-breaking memory leak / FPS lag in PvP ***

* Patch 1.3.4 fails to fix game-breaking memory leak / FPS lag in PvP *