Thank you, G. I hope it's just a few misplaced semi-colons.

:tes:

For me the game has become pretty much unplayable so I've decided to put it aside for now until it's patched in a way that fixes the bugs causing the problems, mostly CTDs. I won't be recommending it to anyone until it's playable.

Being in the software industry myself I know how complex it is to fix bugs in applications, is it the application? The video driver? Audio driver? Things that seem very simple always wind up being complex. I 'fix' one thing one place, next thing I've broken something else somewhere else. Unfortunately doing QA across all configurations of systems in nearly impossible, things like regression testing.. ugh. No matter what the application is there are always a few bugs, I accept that. I feel though that Bethesda was so fixated on 11/11/11 that they cut corners, froze the bug list prematurely (Every company has a long list of bugs; P1/P2/P3 prioritized - in a rush you clear the P1s and hope the P2/P3s don't turn into show stoppers). Now, they are probably scrambling to understand the new P1s ( a long list now ) and figuring out how to fix them.

Someone mentioned earlier that the LAA patch is a fix, it's not. The LAA patch is a temporary work-around that allows game threads to utilize more system memory. The problem is that somewhere in there is a real troublesome memory bug that points to most likely a very large memory leak. If I was Bethesda I wouldn't be just flipping LAA switch on as that might introduce other unknown issues requiring big testing, but it also doesn't address the underlying issue which might by a culprit in more systemic issues in the game.

Anyway, it would be great to hear from Bethesda, just even acknowledgement of the P1s they are tirelessly working on as the experience I've had so far is pretty mixed.

Thank you. Being a web dev I know how frustrating and demoralizing, not to say panic-inducing (!!!) it can be to update something only to have a simultaneous outcry from hundreds of people who've had problems. I love you guys and the games you make, but I was rather upset to find my XP-freezing workaround had become a work-a-not.

(For me, just having a way of rolling back the patch so I can run the old .exe in compatibility mode would be cool)

Just received a tweet from a member of staff at Bethesda.

http://twitter.com/#...gstaffinfection

Me (@gevans81) "Your game is broken, how about a word from the dev team to let us know what the heck is going on?"

@gstaffinfection "we'll be sharing some news shortly"

Maybe they should have taken that approach before release. Everybody knows there's no such thing as 100% bug free software but releasing a patch that does more harm than good is just unacceptable. Seems to me that even 3 years wasn't even enough time and that the game may have been released too soon. Even if I'm wrong about that there's still no excuse for releasing a bad patch. They weren't under any release pressure then. There are many people who have difficulty playing this game (fortunately I'm not one of them) and seeing as how most paid $50 or more, I think they have a right to complain and be a little upset that an official patch actually made things worse.

The post sounded like someone who just had no idea why the big flurry of negative posts on patch issue, I had no idea of other sorts of participations. It was my comment on a short post, only.

True, although I've repeatedly got the impression that Bethesda's legal department are a bitlot too defensive: I know it's standard legal advice to not admit anything, but I think that has to be balanced with the need to actually communicate.

Excellent post. Good insight into what these guys are most likely scrambling to do. I'm sure they feel like theyre putting fingers in the dike right now.

I understand people are annoyed and want answers. We have all paid money for the game. But some of the posts im reading are ridiculous. Its just a game. Some people need to stop acting like screaming children whose toy car has stopped working and learn some damn patience.

Just my two cents :confused:

Yes.

Funny you should say that.
The Skyrim Script Extender team fixed the resistances bug.
Overnight.

Since the new patch, I cannot play Skyrim at all. The game loads, the little icon comes up on the left hand side of the screen...no menu on the right hand side with continue and all that.

And yes, I tried deleting the mods...then I tried verifying the game cache, then I tried uninstalling, re-installing, and verifying the game cache...so yeah, tried it all...

So, you're running an admittedly sub-par machine that requires you to run the game in compatibility mode, and you're blaming the game?

I hope you're not serious, mate.

Good for them. :celebration:

LOL!!!

Thanks Gstaff... Although, I think we all know this statement was much needed one day earlier, nonetheless, better now than never. Lets get these repairs done, and enjoy Skyrim at its finest! :tes:

see even to just tell us themselves that it works like this^^ and thats why its so hard would alleviate some of the frustration. through all the community support i would just like a rundown of how they plan to fix the bugs and why it has been so difficult. if i got an explanation i wouldnt be waiting around deciding if im going to return my game.

+1

Exactly, people need to stop whinning they want their patches and fixes NNOOOWWW!!! I have mentioned before that it took them awhile to patch Morrowind more then people realize, same goes with Oblivion and now Skyrim. they will fix the stuff when they get to it....END OF STORY!!!

Sorry, cannot use that, the source code already existed, it just requires tweaking depending on which exe it will be calling.

Why don't they turn on LAA by default?, simple, it can cause memory clash in 32 bit systems, and before you ask, no it's not a simple matter to write an official 64bit exe.

P.S, I would like to see a 64bit exe myself, but I won't be holding my breath.

How little you know of Bethesda. If at all possible they will ignore as many problems as possible. That is why as a community we must try to continually draw attention to serious issues - to have any hope of having them fixed.

Fixes take time. You know what doesn't take time? Not releasing a patch that you know has game breaking bugs. I am such a problem solver. So, yes, if Bethesda knowingly breaks the [censored] they sold us, we expect them to say "Oh yeah, our bad. We're on it!"

I doubt they will fix it if anything they will say "on our systems it works fine, stop your [censored]ing"

That's literally all I need - just a confirmation that Bethesda is indeed working on it. Much obliged, keep us informed.

As someone who works tech support for a large software as a service company, we never trust the customers word. Honestly end users are [censored] and don't know what they did that would trigger the hiccup. It could have been caused by something that happened 100 hours of gameplay ago.