Tuesday, June 23rd 2015

AMD Releases Catalyst 15.6 Driver for Batman: Arkham Knight

AMD released Catalyst 15.6 drivers, with optimizations for Batman: Arkham Knight. These Beta drivers, meant for Radeon R9 200 series, HD 7000 series, and HD 6000 series;(there are separate upcoming drivers for R9 300 and R9 Fury series); include performance optimizations, stability improvements for Batman: Arkham Knight, this week's big game release. The game itself has been causing problems to PC gamers, with a 30 fps cap, which can be disabled using a config file edit, but yielding stuttering and frame-skipping on both Radeon and GeForce video cards; and is expected to see a launch-day patch.
DOWNLOAD: AMD Catalyst 15.6 for Batman: Arkham Knight, for Windows 7 64-bit | Windows 7 32-bit | Windows 8.1 64-bit | Windows 8.1 32-bit
Add your own comment

27 Comments on AMD Releases Catalyst 15.6 Driver for Batman: Arkham Knight

#1
Vinska
TFW "go to the yesterday's nvidia thread on the same matter, read while substituting the word "nvidia" with "AMD" and you're golden without needing to post here" :cool:
Posted on Reply
#2
ISI300
I got a better title for this:
"AMD Doesn't Trust it's Own 15.5 Driver - Batman Arkham Knight Driven by AMDs Own 15.6 Driver."
Sorry, this was the only time I will have done this.
Posted on Reply
#3
the54thvoid
ISI300 said:
I got a better title for this:
"AMD Doesn't Trust it's Own 15.5 Driver - Batman Arkham Knight Driven by AMDs Own 15.6 Driver."
Sorry, this was the only time I will have done this.
I would let this tawdry new craze die out if you please. Trolling posts lose their humour almost instantly.

It will be good to see if AMD can outwit the Gameworks fx. I know its not meant to impact AMD hardware but we know it does have some impact.
Posted on Reply
#4
natr0n
Reading steam comments on this game seems to be a real mess currently.
Posted on Reply
#5
ISI300
the54thvoid said:
I would let this tawdry new craze die out if you please. Trolling posts lose their humour almost instantly.

It will be good to see if AMD can outwit the Gameworks fx. I know its not meant to impact AMD hardware but we know it does have some impact.
Actually, although GW is implemented in this game, I think the main problem is the horrific optimization and the shoddy PC port. I have never seen a Batman game work on day one (Haven't played Arkham Aylum).
Arkham City: GFWL, horrible DX11 performance on launch (Surprisingly, ran better on my 5870 than my 460.)
Arkham Origins: Better than City, but way too many glitches, some stopping you from progressing
Posted on Reply
#6
RCoon
Gaming Moderator
natr0n said:
Reading steam comments on this game seems to be a real mess currently.
Game runs like ass for 50% of people, and fine for the other 50%. It's hit and miss, and it's a total mess. If you don't have problems, quids in. If you do have problems, get a refund and wait for the next week of patches that inevitably arrive.
Posted on Reply
#7
LightningJR
Nice to see them on top of things again.

Now only if the game developers would do the same.
Posted on Reply
#8
GhostRyder
I have not bought the game yet so I may hold off on updating to this driver because I was planning on playing with the 15.15 driver a bit.

Game also looks like its going to need a lot of patching from what I have been reading as it is...
Posted on Reply
#9
Casecutter
Well if paying opening day price for this... is stupid! These Gaming Houses need to be informed that no matter how epic you build momentum and pre-release frenzy, gamers should sit and patiently wait to see if these titles are ready for prime time... So many games have come out as a cold mess, and in a week the price falters, as it should. Gamers need to vote by not paying that opening day upcharge.
Or do and be happy.
Posted on Reply
#10
Eric_Cartman
btarunr said:
These Beta drivers, meant for Radeon R9 200 series, HD 7000 series, and HD 6000 series;(there are separate upcoming drivers for R9 300 and R9 Fury series); include performance optimizations, stability improvements for Batman: Arkham Knight, this week's big game release.
What that translates to is these drivers just fix bugs so the game runs on the R9 200 cards, but we'll only be applying the performance optimizations for the R9 300 cards to make them look artificially better than the R9 200 cards.
Posted on Reply
#12
btarunr
Editor & Senior Moderator
some_big_freek12 said:
How many hours remaining in AMD Radeon Fury X review?
About 20 hours.
Posted on Reply
#13
Steevo
Eric_Cartman said:
What that translates to is these drivers just fix bugs so the game runs on the R9 200 cards, but we'll only be applying the performance optimizations for the R9 300 cards to make them look artificially better than the R9 200 cards.
No, you are confusing AMD with Nvidia.
Posted on Reply
#14
the54thvoid
Steevo said:
No, you are confusing AMD with Nvidia.
Well sort of but AMD aren't playing completely fairly:
AMD is aware that effectively rebranding a whole series, albeit with performance improvements when compared to the previous generation, is a dangerous game to play, especially for enthusiasts who pore over specifications with a fine-toothed comb. Looking to add more value, the company is introducing a number of technologies that, for now, will be limited to the 300-series.

The first is frame-rate targeting control. As the name suggests, the driver enables a specific framerate target to be achieved, and such an approach is useful if the card produces surfeit performance in easy-to-render games. There's little point in producing 150fps at full GPU chat when, say, 60fps will do. Frame-rate control dynamically reduces the frequency and power consumption of the GPU for a quieter, cooler experience.

Such technology is included for all 300-series cards but there is no genuine reason why it can't run on the older 200-series mob. AMD says it has 'validated' frame-rate control for the newer GPUs; we feel that it's deliberately not included on the previous-generation GPUs because such a feature provides some form of family differentiation. And the tech certainly isn't new; Nvidia has had it available for its GPUs for a while now.
http://hexus.net/tech/news/graphics/84089-amd-radeon-300-series-explored/
Posted on Reply
#15
Octopuss
AMD is starting to piss me off. After a month and sometimes even longer of waiting, they add some tweak for one shitty game. What the hell?
Posted on Reply
#16
erocker
*
Octopuss said:
AMD is starting to piss me off. After a month and sometimes even longer of waiting, they add some tweak for one shitty game. What the hell?
They can't win, can they? They do something, people get mad, they do nothing people get mad. Mad mad mad amd.
Posted on Reply
#17
ManofGod
PC Master Race indeed. :laugh::rolleyes: I am grateful that I console game on my XBox One and 360 as well as game on my PC. This game is one reason I am. (Perhaps this is why you could get the game of up to 40% off on release.)
Posted on Reply
#18
Octopuss
erocker said:
They can't win, can they? They do something, people get mad, they do nothing people get mad. Mad mad mad amd.
Yeah, why bother fixing general bugs that have been present for months to years and which apply to most people when they can slap in a little tweak for one single game and call it a new Catalyst version.
Posted on Reply
#19
RejZoR
From what i've seen this game is a pile of rotten garbage. I blame it on Canada.

In other news, no driver will ever fix a badly made and/or broken game...
Posted on Reply
#20
Batou1986
I find it funny that this driver specifically disables crossfire for this game instead of adding a profile.
Posted on Reply
#21
mcloughj
Installed the beta driver. batman and the batmobile became explosions of triangles. Went back to the omega driver and gotham was all messed up while driving said mobile.

The game is broken, mainly because Rocksteady out sourced the PC port to a small developer with little PC experience.

No driver is going to fix that.
Posted on Reply
#22
kn00tcn
Octopuss said:
Yeah, why bother fixing general bugs that have been present for months to years and which apply to most people when they can slap in a little tweak for one single game and call it a new Catalyst version.
which bugs? there are different groups within the driver team that focus on specific things

one group does performance, another does bugs, another does crossfire, another does video, etc

(i dont have the citation but it's possibly from andrew or robert sometime in the last 1-3 years)

if you follow the driver leaks, you can see they are most certainly busy fixing bugs, adding features, boosting performance (there is partially working crossfire freesync in the 1040 leak for example)

there are 3 milestone drivers coming up
The Catalyst 15.15 drivers (windows 7, 8) features:
- FPS Targeting: The ability to save power by setting a maximum FPS target
- Virtual Super Resolution: The ability to downscale a game from a high resolution to a lower resolution, giving a user higher-quality textures in game (also known as supersampling)
- Performance optimizations: Adding game performance optimizations to AMD R9 Fury X and other graphics cards.

Catalyst 15.20 (Windows 7, 8, 10) features:
- Catalyst Uninstaller: Allows users to uninstall their AMD catalyst drivers cleanly, so new drivers can be installed without incident
- OpenCL 2.0 optional features: Multiple performance and feature additions
- FreeSync + CrossFire: The ability to run FreeSync dynamic screen refresh technology with multiple GPUs in CrossFire mode.

Catalyst 15.20 Windows 10 specific features:
- HEVC (High Efficiency Video Codec): Enables quality streaming and 4K experiences
- DirectX 12: Support for the low-level efficient graphics API for Windows 10
- Windows 10 WHQL (Windows Hardware Quality Lab): AMD’s latest driver release (15.20) will be WHQL and WHQL for Windows 10 as well.

Also AMD is bringing support for HDR monitors to the Radeon 300 series. Support for colors up to 16 bpc or 16-bit color.
patience & empathy! why would they want to be a dick to their customers? their r&d is so low, their stock is so low, games are a luxury, & to an extent some of the other computing tasks that have bugs
Posted on Reply
#23
R-T-B
erocker said:
They can't win, can they? They do something, people get mad, they do nothing people get mad. Mad mad mad amd.
They could start by releasing a driver marked "stable" every few months, WHQL or not.
Posted on Reply
#24
Octopuss
R-T-B said:
They could start by releasing a driver marked "stable" every few months, WHQL or not.
The drivers ARE stable, there's no problem with that. AMD repeatedly said the betas go through the same testing as the WHQL ones, and there are literally no differences. The name is a bit unfortunate though, and they should change it into something less "controversial".
Posted on Reply
#25
R-T-B
Octopuss said:
The drivers ARE stable, there's no problem with that. AMD repeatedly said the betas go through the same testing as the WHQL ones, and there are literally no differences. The name is a bit unfortunate though, and they should change it into something less "controversial".
If that is true why don't they fork out the measly amount for a WHQL cert?

This also does not inspire confidence:
Download our latest beta driver and get a preview of what we're currently working on.
Note! This driver is provided "AS IS" and under the terms and conditions of the End User License Agreement provided therewithin.
I'm willing to admit it's as simple as a terminology change but they need to clear that up. Any links to where they have said that, that you know of?
Posted on Reply
Add your own comment