This fucking Blizzard! What a joke...
http://www.youtube.com/watch?v=spMS3Hhk1FA
http://www.youtube.com/watch?v=spMS3Hhk1FA
Diablo III - It's official
- Thread starter N00b
- Start date
Lol, if something is a joke it's your attitude
When something is made by humans, there's bound to be some bugs here and there, and chances are someone will find them eventually.
Lol, if something is a joke it's your attitude
When something is made by humans, there's bound to be some bugs here and there, and chances are someone will find them eventually.
How is it a bug? It was programmed that way! You cant use local time, instead of server time by accident.
How's that? You mean someone, early on before the server code was running, couldn't have written a gettime routine for client time and forgotten to go back and change it once the server code was up and talking?
Why would anyone even write it client site in the first place? It is big system and main focus of online-only approach, so it shouldnt be written by one person and tested by one person, but whole team, so client based approach doesnt make sense.
Would You write it that way?
BTW it can also explain many bugs we had with auctions bidding, especially in last minutes.
So which is it then? Intentional or bug? As to why anyone would use a local time variable, I would imagine that then rendering engine and client app work was started well before the server code. That's pretty common, no? So if your team is working on the client and there is no server yet, where is your time variable going to come from?
What makes you think a bug has to be an accident?
By the name. Otherwise, it's called a "feature".
Okay, I decided to give Diablo 3 a try even though I won't be able to play it on long, international flights...
anyway, maybe (likely) it's because I'm playing on normal and my highest is a lowly 11th level Wizard, but I'm finding it quite fun and entertaining...here's hoping the imbalances are debugged before I get far enough along to experience them.
anyway, maybe (likely) it's because I'm playing on normal and my highest is a lowly 11th level Wizard, but I'm finding it quite fun and entertaining...here's hoping the imbalances are debugged before I get far enough along to experience them.
It runs TERRIBLE on my Macbook with Sandybridge graphics, if that's any indication. Just...terrible. Which is strange, really, because there's hardly any overdraw most of the time so it really shouldn't be fillrate limited, and a dual core/four threads should be enough CPU grunt. It's an i7, so max turbo is 3.4GHz (not on all four threads though of course...) I guess it's all the transparent mist and such that swirls around everywhere that's killing the GPU. *shrug*
Wonder if you can turn that off somehow?
Wonder if you can turn that off somehow?
D
Deleted member 13524
Guest
That's not new:
Not that Diablo 3 ever set a benchmark for visual/performance efficiency, though.
No shit... WoW runs better on my macbook than D3 does, which is ludicrous considering how much more visually complex WoW's environments are.
D
Deleted member 13524
Guest
D
Deleted member 13524
Guest
It's within the minimum specs.. I'd guess a little bit like a HD4000, maybe a bit less.
