Monday, August 31st 2015
AMD Releases Catalyst 15.8 Beta Driver
AMD released the Catalyst 15.8 Beta driver. In addition to an updated display driver, with likely support for newly launched GPUs, the Radeon R9 Nano and R9 370X, the drivers offer DirectX 12 performance optimizations for "Ashes of the Singularity," and optimizations with stability updates for "Batman: Arkham Knight." More importantly, the driver integrates Oculus 0.7 SDK, and fixes a number of game-specific bugs.DOWNLOAD: AMD Catalyst 15.8 Beta for Windows 10/8.1/7 64-bit | 32-bit
24 Comments on AMD Releases Catalyst 15.8 Beta Driver
Either way, the Ashes of the Singularity affair is still purely speculation and unsupported claims.
...I mean, I really seriously probably could. But I think MS would send an assassin/lawyer hybrid thing to kill/incarcerate me if I tried that... so not going to.
It's too buggy when gaming. GTA V will randomly crash when joining a mission (can't render dx11 blah blah). Killing Floor 2 also randomly C2D.
Either that or Nvidia's drivers suck..... :roll:
well those new settings are interesting...
If you can get that far, and get through the days of downloads, it works rather well. But I can't recomend it as a practical solution, I use it for myself because I have a spare 1TB HD in my server doing nothing.
Too bad FuryX still locks down on HBM overclocking.
Windows 10 has a bad driver support, I installed GTA San Andreas and DirectX 9 (latest installer released before MS started locking DirectX to Windows version) but I could not start it because it said it was missing DirectX 9. I did this in Vmware Workstation and when I tried it on Windows 8.1 VM it worked.
Ad in the fact that its a complicated and needles solution to a simple problem, it appeals to me, got any links?
Also, how is the "target" temp different from the max temp on a 290X?
about 80~100 fps in MadMax / 30~50 in new Metal Gear =P... (1440p / Max settings ).
Since I did upgrade from Windows 7 to 10, I wouldn't be surprised if the upgrade screwed up some stuff that is causing issues. I probably should just do a clean install and get it over with. It has been over a year anyways, so I'm about due. The interface for RSTe seems to be broken too which could be related (probably VC++ redist.) With all these automatic updates, I wouldn't be surprised if after a restart it screwed with something that was installed in Win7 before the upgrade.