AMD launches Catalyst 15.8 beta drivers with Oculus SDK support

[sinu]

Content source

http://www.techspot.com/news/61956-amd-launches-catalyst-158-beta-drivers-oculus-sdk.html

Following on from Nvidia's release of the GeForce 355.82 graphics card drivers, AMD has today launched their own set of new drivers: Catalyst 15.8 Beta.

Surprisingly, AMD doesn't specify any performance optimizations in this driver for Metal Gear Solid V: The Phantom Pain or Mad Max, two games which are set for release on September 1st. This could mean AMD has yet to optimize either of these games for their hardware, though we'll have to wait until their release to find out for sure.

What has been included in the Catalyst 15.8 Beta drivers is support for version 0.7 of the Oculus SDK. AMD has also improved performance and stability in Batman: Arkham Knight, as well as Ashes of the Singularity running in DirectX 12 mode.

AMD does note that there are a few minor issues with the Catalyst 15.8 beta drivers, such as Dirt Rally crashing during gameplay on some BenQ FreeSync monitors, and driver installation issues if you're running Windows 10 and have a system with an AMD 990FX chipset and CrossFired GPUs.

 

[hjlbx]

It's great that AMD always improves their drivers. However, there is one potentially critical problem for Comodo Internet Security use on AMD systems...

If Comodo does not recognize any of the graphics drivers, then they will be treated as Unrecognized by Defense+. When this happens, upon loading into active memory they will be auto-sandboxed. This can cause all manner of system mayhem, up-to and including a smashed system = Black Screen unbootable system.

When installing any AMD drivers it is best to set HIPS to Training Mode for at least a few days. While Training Mode is active, Defense+ will create hidden Allow rules for those Unrecognized AMD objects. After switching to Clean PC, Safe or Paranoid Mode those AMD objects will be treated as Trusted and allowed to run without restriction.

It is better to use Training Mode than to disable HIPS - because - when HIPS is re-enabled, Defense+ will simply re-detect the AMD objects as Unrecognized.

Alternatively, one can immediately change a file's rating from Unrecognized to Trusted. This accomplishes the same end result, but Training Mode is more thorough...

 

[sinu]

It's great that AMD always improves their drivers. However, there is one potentially critical problem for Comodo Internet Security use on AMD systems...

If Comodo does not recognize any of the graphics drivers, then they will be treated as Unrecognized by Defense+. When this happens, upon loading into active memory they will be auto-sandboxed. This can cause all manner of system mayhem, up-to and including a smashed system = Black Screen unbootable system.

When installing any AMD drivers it is best to set HIPS to Training Mode for at least a few days. While Training Mode is active, Defense+ will create hidden Allow rules for those Unrecognized AMD objects. After switching to Clean PC, Safe or Paranoid Mode those AMD objects will be treated as Trusted and allowed to run without restriction.

It is better to use Training Mode than to disable HIPS - because - when HIPS is re-enabled, Defense+ will simply re-detect the AMD objects as Unrecognized.

Alternatively, one can immediately change a file's rating from Unrecognized to Trusted. This accomplishes the same end result, but Training Mode is more thorough...

That's true its a long pending bug to be fixed by comodo even I had that problem anyway I removed Comodo for some other reason