In order to combat SPAM on the forums, all users are required to have a minimum of 2 posts before they can submit links in any post or thread.
Discussion in 'UHall' started by Deb, Nov 2, 2009.
Any ideas what the patch we just got is for?
Nope, but it is both clients.
Nothing on UOHerald yet. Hmmmm
Mystery patch! Yummy
I must reaffirm that I didn't receive any patch yet.
I thought the patch server was the same for everyone, so why doesn't my client find any patch?
what was the patch? I havent logged out to repatch yet but how big is it etc?
I have also not recieved a patch with the EC so dont worry you are not alone.
Look patchlog - only client.exe and dbghelp.dll modified. My guess is "better illegal apps un-support"
dbghelp.dll was added, rather than modified.
With Mr. Google's help, I'd say it's to do with the on-crash debug info.
Since that was added, the client.exe modification was probably to support it.
Does this mean they solved the black spots in the EC? Or maybe the crashing after being too loaded? Either one would be nice if not both. Guess I am being greedy but I pay my subscription fee too
So, does this mean... classic client will crash more after patch?
Further guessing, I'm going to say "not in the short term".
However, if the process of them getting relevant information on crashes is improved, then in the long run, they'll be better able to fix crash bugs, since they'll have more to work on.
What I suppose you could take from this, though, is that its a demonstration of will to fix crash bugs with the 2D client, which means they're going to keep shoring it up each time they break something.
hopefully this patch is to fix the harbring (or whatever his name is) teleporting you into private houses to where you can't get out and if he kills you while you're in that house you lose your items. 3 times last night teleported into a private home where I had to either hit i'm stuck or recall out. Bad Monster
He stuck me in a dungeon wall, right after insurance ran out.. lost everything that wasn't blessed. Good thing I already hit 120 imbue so i can rebuild rather easily..
This patch is to fix the future patch that will come into the game once the future patch is patched into place. This new patch fixes all the bugs the future patch will have.
Then they will have another patch to fix the bugs in this patch thats to fix the bugs in the upcoming patches..you see? but this patch might not solve all the problems and they might need 2 more patches after the patch for this patch to really screw Umm I mean really fix things..
If you get this...U might be ready to work for UO.
I think this patch was to insure that uo will be laggy for another 2 months.Then a new patch to fix the lag.Week later uo will have another event.Prolly a xmas event to insure everyone has a merry laggy xmas.
Correct. I patched, was playing and recalled to my house and my client crashed. When it did I got a msg box with a bunch of error codes and a note saying copy this ane email it to [email protected].
I noted this. And then ignored it.
If you really want me to send it -then setup a webservice and have my client push the msg to the webservice on my approval. Don't make me bother to create an email. Sheesh.
I had to clear my patch folder a couple times to get the patch to apply, kept getting an error message that the patch couldn't be applied.
Actually, it was doing that before the patch. I got a few crashes when flying around with a gargoyle, although they tended to happen at the worst possible time, and there's no way I'm taking the time to compose an email when there's likely to be some manner of monster chewing on my arse.
It's better than no feedback, but as you say, the process should be as simple and unobtrusive as a yes or no button.
I get it & fully agree with you
dbghelp.dll I would imagine is for Windows 2000/Win9x support. Since a recent patch the version of dbghelp they use in UO is newer than the newest one available for those OS'es.
any clue what this last patch was for?
The tone of that message.. something in the spirit of "you crashed our client, tell us what you did wrong"..
I concur; it should have a one-button error submission system. I'd even check an "auto-send errors on crash" box if it were an option.
I got something like this on crash.
And as paranoid as I am, I feared a fishing scheme to get me to email info.
So I ignored it.