New FPS issue response from Community Manager

Ifthir_ESO · July 2014

FENGRUSH wrote: »

Oh nice, a hotfix. This should go over well.

So you *** when they dont hotfix, and you *** when they do.

Tharvall · July 2014

A hotfix after 3 weeks?

I wonder if this will also work in my job. The next time my boss asks me for an urgent report or anything I'll just lay back, send some funny e-mails for 3 weeks and then say "Oh, you are right, this is really an urgent issue! I'll start thinking about it immediately!". And my boss will probably think "What a great guy! The best employee ever, he really deserves a huge pay rise".

Right?

xherics · July 2014

Rylana wrote: »

Like said in my post, someone with an extremely strong CPU (one that blows away the recommended specs this game claims to need) have built in compensation for the issue causing it.

That being said, even the most powerful processor will still be overwhelmed under the right conditions. You dont see it because your system is uberhaxxorz. It is still there, however.

Just because a game can be played on a top of the line super gaming rig built in q2 2014 doesnt mean its correct. It needs to be playable at that level even just at recommended system specs printed on the box.

Anything less is dishonest.

Speaking of me being "shady" where have you been? Ive been talking about this issue for over a week and no one has listened yet.

I have Intel Core i7 4771 CPU; nVidia GTX 710Ti and 16GB 2133Mhz ram, the game is on SSD disk, and I had the FPS drop problem. I will test this new "fix" later today if helps or not.

FENGRUSH · July 2014

Ifthir_ESO wrote: »

FENGRUSH wrote: »

Oh nice, a hotfix. This should go over well.

So you *** when they dont hotfix, and you *** when they do.

Pretty much, yes. There will be no genuine celebratory thanks when this is fixed.

bitaken · July 2014

I concur Feng - it should have been fixed 1.5 weeks ago. No thank you from me. They gave me at least 2 seizures with the FPS bug that I can think of. Those are the ones I can remember anyway.

FENGRUSH · July 2014

I dont like coming off as a complete *** on this. But even though its fixed(which I have no idea to what extent it is yet), the manner in which it was handled has already make a significant impact on me and the community.

The absence of communication from ZOS on it and genuine responses, just standard automated rhetoric... is really tough to deal with. That is what we have to look forward to pushing through future problems. And were dealing with a lot of problems as we move along here through rough patches (literally).

Mitharus · July 2014

FENGRUSH wrote: »

Pretty much, yes. There will be no genuine celebratory thanks when this is fixed.

... This is similar to an issue in my job (I deal with HPC clusters). We finally figured out that on a specific OS version, performance... sucks horribly as compared to the previous as soon as anything expecting interrupts to work sanely was ran. Locally, it blew performance away though even with the crap kernel (i.e. local 9 sec wrf run compared to 11 sec same machine/dataset, different OS).

This took weeks. Delving deep into kernel tune ables, custom kernels, library rebuilds, etc... (I mean, would you expect an strace to speed up a run by 5 sec? What about preloading libc?) before finally finding something that worked to get performance back on par. So yeah... some issues are buried so deep, and are so intrinsic, that you don't even know there is an issue until certain conditions are met. And by that point you can be completely screwed.

If they got the FPS issue starting to be ironed out, then wonderful. But to say what you have is, IMO, just down right petty. Yes, the issue was a PITA. Yes it sucks. But some things just are. If they are getting it worked out, then they do deserve thanks.

They also deserve being beaten over the head for the lack of communication on the issue, but I cannot completely fault the community managers for that. They, most likely, have a small bit to work with.

-M

Edit: I somewhat apologize for the snarkiness. Way to much blood in my caffeine stream to be writing a post. Still stand by my statements though, and I'll let it stand as is.

Tharvall · July 2014

they had a perfectly running game (performance wise). not only that, the performance - especially in large scale pvp battles - was praised in all the reviews. even in the negative ones.

i think zenimax can be very proud on themselves for the sheer stupidity that must have smitten them and led them to ruining a perfectly running system for no apparent reason. congratulations.

xherics · July 2014

The FPS problems are fixed for me, but yesterday I had 4 times disconnect with unknown error during 2 hours of PVP. For the 4th try I disabled all my addons, but it happened again.

Tintinabula · July 2014

Well today I had NO FPS drops..but painful 5-10 second FREEZES in large battles. I went back to no sound..no music and it all went away.

Raizin · July 2014

instead of shity fps we have horrible fps and unknown crashes! all hail zos!

FENGRUSH · July 2014

Mitharus wrote: »

FENGRUSH wrote: »

Pretty much, yes. There will be no genuine celebratory thanks when this is fixed.

... This is similar to an issue in my job (I deal with HPC clusters). We finally figured out that on a specific OS version, performance... sucks horribly as compared to the previous as soon as anything expecting interrupts to work sanely was ran. Locally, it blew performance away though even with the crap kernel (i.e. local 9 sec wrf run compared to 11 sec same machine/dataset, different OS).

This took weeks. Delving deep into kernel tune ables, custom kernels, library rebuilds, etc... (I mean, would you expect an strace to speed up a run by 5 sec? What about preloading libc?) before finally finding something that worked to get performance back on par. So yeah... some issues are buried so deep, and are so intrinsic, that you don't even know there is an issue until certain conditions are met. And by that point you can be completely screwed.

If they got the FPS issue starting to be ironed out, then wonderful. But to say what you have is, IMO, just down right petty. Yes, the issue was a PITA. Yes it sucks. But some things just are. If they are getting it worked out, then they do deserve thanks.

They also deserve being beaten over the head for the lack of communication on the issue, but I cannot completely fault the community managers for that. They, most likely, have a small bit to work with.

-M

Edit: I somewhat apologize for the snarkiness. Way to much blood in my caffeine stream to be writing a post. Still stand by my statements though, and I'll let it stand as is.

That's ok, there is a lot of truth to your post.

There are people that deserve thanks for fixing this, but theyre probably not reading this thread. The message must be sent to Zenimax that this wasnt acceptable. A company this size shouldnt have an issue that easily created and blatant on their client pushed live into production. They should have quite a large QA team. They have failed here, and ZOSs management must burden the responsibility. Community managers have the awful job of receiving our abuse, but it is warranted and necessary to get across a clear message.