Monday, November 2nd 2015

Steam Offers Batman Arkham Knight Refunds After Second Failed PC Launch

Steam announced that it's offering refunds for Batman: Arkham Knight after a second spectacular failure with its PC release. Arkham Knight was pulled from Steam shortly following its late-June launch over the PC version being plagued by crippling and often unplayable bugs. The game was re-launched in October promising improvements to stability.

The October re-launch of Batman Arkham Knight at a reduced $49 price-tag (over the $59 original) met with even stiffer criticism over little or no effort being put into patching its most glaring bugs and performance issues. Steam is now entertaining refund claims for the game up to December 2015. This only covers people who bought the game and 'paid for it' with Steam, and not those who got it as freebies in promotions such as NVIDIA's Arkham Knight key giveaway. Those who bought the game in its PC-DVD (physical media) format are likely also not covered, since the game was sold directly by the publisher, and not Steam, which only serves as a DRM platform.

Image Courtesy: VideoGamesBlogger
Add your own comment

53 Comments on Steam Offers Batman Arkham Knight Refunds After Second Failed PC Launch

#1
RejZoR
This is why we need refunds. I hope gamers will refund it en mass and show greedy publishers it's just not worth rushing games before they are actually ready for release.
Posted on Reply
#2
uuuaaaaaa
The October re-launch of Batman Arkham Knight at a reduced $49 price-tag (over the $59 original) met with even stiffer criticism over little or no effort being put into patching its most glaring bugs and performance issues.

How come they did not learn from the first time around? What were they thinking?
Posted on Reply
#3
Recus
We need Redux version on UE4. Patches won't fix this mess.
Posted on Reply
#4
jigar2speed
I am not sure if Gameworks was the main reason to be blamed for issues in Arkham Knight, but developers should take a note from this incident and be very cautious using Gameworks API in their game.
Posted on Reply
#5
64K
I think I recall something when they pulled the game off of Steam from an unofficial source at Rocksteady that said that they simply couldn't fix the game and shouldn't re-release it at all on PC. They know the game is still a problem for PC gamers but they also know that die-hard Batman fans are going to try their best to play it anyway and not ask for a refund.
Posted on Reply
#6
lemonadesoda
What were the developers thinking?

Next up, developers will release games with a patch-tuesday model... you can install the game but it doesnt work, then every tuesday you get an update... slowly the game will begin to add graphics, sounds, maps, nPCs, until n months from launch, there is actually a bug free game to play.
Posted on Reply
#7
john_
I am reading that this is WB's decision, not just Steam's.
Posted on Reply
#8
Airbrushkid
I am one of the lucky one's. I've been playing it with no problems.
Posted on Reply
#9
TheinsanegamerN
lemonadesodaWhat were the developers thinking?

Next up, developers will release games with a patch-tuesday model... you can install the game but it doesnt work, then every tuesday you get an update... slowly the game will begin to add graphics, sounds, maps, nPCs, until n months from launch, there is actually a bug free game to play.
That's been common practice for this entire generation, although not to that extreme. How many games were broke at launch, and needed patch after patch to become playable. Assassins creed unity, battlefield 4, watch_dogs, Cod:ghosts all come to mind. How many games lock away content to be sold as day 1 DLC?

Especially on pc, there was no way to get your money back until steam started offering refunds. and WB has never cared about the PC. Batman, Arkham origins was also buggy on release, and the fact that AK was handed to a third party showed that WB never cared about the PC platform.
jigar2speedI am not sure if Gameworks was the main reason to be blamed for issues in Arkham Knight, but developers should take a note from this incident and be very cautious using Gameworks API in their game.
very much so. Gameworks was never a good idea. Why devs would use it is beyond me, but any game that uses it has problems.
Posted on Reply
#10
FordGT90Concept
"I go fast!1!11!1!"
So are the problems only on AMD hardware?
Posted on Reply
#11
truth teller
FordGT90ConceptSo are the problems only on AMD hardware?
no, the game has way deeper issues, visual compatibility between vendors in this case is not a problem, if anything it looks worse on the green camp (game seems to work fine on current consoles).
sadly this is todays aaa titles, use some framework from one camp cause "wow ez", console first and then rip off pc players while you can. good thing consumers voice sounded louder in this case.
kudos to steam, btw
Posted on Reply
#12
omnimodis78
jigar2speedI am not sure if Gameworks was the main reason to be blamed for issues in Arkham Knight, but developers should take a note from this incident and be very cautious using Gameworks API in their game.
GameWorks isn't the problem whatsoever, it's the fact that it's a port done wrong; as badly as it can be done. You probably can't even explain what GameWorks is without having to look it up. GameWorks runs just perfectly fine in all other current games I can think of which I am playing, and it worked fine in Arkham Origins. Please don't spread sensationalist nonsense if you don't really understand the problem.
Posted on Reply
#13
Chaitanya
uuuaaaaaaThe October re-launch of Batman Arkham Knight at a reduced $49 price-tag (over the $59 original) met with even stiffer criticism over little or no effort being put into patching its most glaring bugs and performance issues.

How come they did not learn from the first time around? What were they thinking?
They weren't thinking but smoking their own shit. This is what is wrong with developers, treating PC gamers as 3rd grade citizen. they need to get their act together or they will be losing the biggest user base.
Posted on Reply
#14
ZoneDymo
omnimodis78GameWorks isn't the problem whatsoever, it's the fact that it's a port done wrong; as badly as it can be done. You probably can't even explain what GameWorks is without having to look it up. GameWorks runs just perfectly fine in all other current games I can think of which I am playing, and it worked fine in Arkham Origins. Please don't spread sensationalist nonsense if you don't really understand the problem.
Now dont get all bend out of shape, we all have heard a lot of problems from multiple games stemming from gameworks.
Posted on Reply
#15
Octopuss
I might be wrong, but it give me the impression that this is what happens when a game is primarily written for consoles and ported to PC. I feel like it always should be the other way around, and when it is, it works.
Posted on Reply
#16
FordGT90Concept
"I go fast!1!11!1!"
OctopussI might be wrong, but it give me the impression that this is what happens when a game is primarily written for consoles and ported to PC. I feel like it always should be the other way around, and when it is, it works.
The only game I can recall that went that way was Witcher 2 and it didn't go well. It took over a year to port and they found they pretty much had to recode the entire engine substructure to make it work. When developing for multiplatform, it's best to do them simultaneously. That's the way Witcher 3 was done. Optimizations that had to be made for consoles can also make the game run better on lower end hardware on Windows. Rockstar has the formula right: develop all simultaneously and give PC the extra TLC it requires.

I really see no obvious reasons why Arkham Knight is exceptionally poor in terms of PC release. I'm sure Warner Bros knows and probably Rocksteady too but they probably aren't saying anything. All four games use the same engine and Rocksteady developed all except one (Arkham Origins).
Posted on Reply
#17
qubit
Overclocked quantum bit
Someone's got massive egg on face, lol.
Posted on Reply
#18
Casecutter
So is Nvidia going to make good and actually provide a "working game" for those that have or redeemed the promotional Free game voucher that was used to spur sales?
Posted on Reply
#19
MxPhenom 216
ASIC Engineer
jigar2speedI am not sure if Gameworks was the main reason to be blamed for issues in Arkham Knight, but developers should take a note from this incident and be very cautious using Gameworks API in their game.
If it was Gameworks, every game that used it would have a similar fate, and most havent, at least not as badly as this one.
Posted on Reply
#20
MxPhenom 216
ASIC Engineer
ChaitanyaThey weren't thinking but smoking their own shit. This is what is wrong with developers, treating PC gamers as 3rd grade citizen. they need to get their act together or they will be losing the biggest user base.
PC gamers are no where near the biggest user base lol.
Posted on Reply
#21
Octopuss
MxPhenom 216PC gamers are no where near the biggest user base lol.
Unfortunately.
Posted on Reply
#22
FordGT90Concept
"I go fast!1!11!1!"
MxPhenom 216PC gamers are no where near the biggest user base lol.
Over the software lifetime, yes, they are. 10 years from now, people will still be buying the game on Steam, GOG, uPlay, Origin, and the like. 10 years from now, the only people buying Arkham Knight on Xbox One and PlayStation 4 will be the used market which generates very little revenue for the publisher. They're going to fix it--they can't afford to not fix it.
Posted on Reply
#23
TheGuruStud
If I didn't know better (hell, maybe I'm right), I'd say all of the crap PC games are a conspiracy by publishers to damage the PC reputation (we know how much power they exert over devs). They don't like PC gaming, in fact, they hate it. They want everyone on console to double, triple and quadruple dip their profits.

Why produce good content if you can just force everyone to a locked platform, charge w/e you want, then charge more for a few "extras" that you didn't unlock originally? And make money off online subs!

There's literally no excuse with the money and talent behind the scenes of why shit can't get done properly. Are they Hollywood accounting or what?
This was RARELY a problem before the internet allowed easy patches (like this day 1 BS from every game).

I played tons of games in the 90s through the early '00s in which I never had to update. I completed them with no big bugs and no performance issues (every single one was smooth as butter). And you if you do a comparison of graphics quality vs hardware at the time vs now, then you'll realize what a joke games are today. All the HP in the world can't run some new titles.

Of course, maybe they're just that lazy and stupid. Even consoles have had major issues with crashing, abysmal performance and bugs.

I also blame Nvidia. They're not helping anything with their shadiness. Helping to ruin performance isn't doing the platform one bit of good. But what do they care? Short term profits rule!
Posted on Reply
#24
webdigo
AirbrushkidI am one of the lucky one's. I've been playing it with no problems.
You are not lucky. You just haven't noticed anything while you played.
Posted on Reply
#25
rtwjunkie
PC Gaming Enthusiast
omnimodis78GameWorks isn't the problem whatsoever, it's the fact that it's a port done wrong; as badly as it can be done. You probably can't even explain what GameWorks is without having to look it up. GameWorks runs just perfectly fine in all other current games I can think of which I am playing, and it worked fine in Arkham Origins. Please don't spread sensationalist nonsense if you don't really understand the problem.
So much for all the hopeful thinking I saw on this forum when the new generations of consoles were released.

The thinking was they are pc's now, and ports will be easier to do and play much better on pc's.

Um....yeeeeaaaahhh.
Posted on Reply
Add your own comment
Apr 24th, 2024 13:15 EDT change timezone

New Forum Posts

Popular Reviews

Controversial News Posts