Lightroom: AMD Fury and GPU acceleration does not work (MSI Afterburner OSD issue)

  • 1
  • Problem
  • Updated 3 years ago
  • Solved
  • (Edited)
GPU accelerate enabled does not work with an AMD Fury card in the latest build of LR CC 2015.2.1, AMD beta driver 15.9.1 and Windows 8.1. I get a blue image with a cross through where the photo should be inside of the develop module, disable the GPU option and instantly the blue cross image disappears, i get the photo back and LR behaves as it should do.

Lightroom version: CC 2015.2.1 [ 1046594 ]
License: Creative Cloud
Operating system: Windows 8.1
Version: 6.3
Application architecture: x64
System architecture: x64
Logical processor count: 8
Processor speed: 4.0 GHz
Built-in memory: 20471.0 MB
Real memory available to Lightroom: 20471.0 MB
Real memory used by Lightroom: 909.7 MB (4.4%)
Virtual memory used by Lightroom: 894.1 MB
Memory cache size: 1334.8 MB
Maximum thread count used by Camera Raw: 8
Camera Raw SIMD optimization: SSE2
System DPI setting: 144 DPI (high DPI mode)
Desktop composition enabled: Yes
Displays: 1) 3840x2160
Input types: Multitouch: No, Integrated touch: No, Integrated pen: Yes, External touch: No, External pen: Yes, Keyboard: No

Graphics Processor Info:
AMD Radeon (TM) R9 Fury Series

Check OpenGL support: Passed
Vendor: ATI Technologies Inc.
Version: 3.3.13399 Core Profile Context 15.201.1151.1004
Renderer: AMD Radeon (TM) R9 Fury Series
LanguageVersion: 4.40

Application folder: C:\Program Files\Adobe\Adobe Lightroom
Library Path: E:\Lightroom\Photographs\Photographs-2.lrcat
Settings Folder: C:\Users\User\AppData\Roaming\Adobe\Lightroom

Installed Plugins:
1) Canon Tether Plugin
2) HDR Efex Pro 2
3) jf Metadata Wrangler
4) LR/Mogrify 2

Config.lua flags: None

Adapter #1: Vendor : 1002
Device : 7300
Subsystem : 49e1043
Revision : cb
Video Memory : 4070
Adapter #2: Vendor : 1414
Device : 8c
Subsystem : 0
Revision : 0
Video Memory : 0
AudioDeviceIOBlockSize: 1024
AudioDeviceName: Speakers (Realtek High Definition Audio)
AudioDeviceNumberOfChannels: 2
AudioDeviceSampleRate: 44100
Build: Uninitialized
Direct2DEnabled: false
GPUDevice: not available
OGLEnabled: true
Photo of Darren

Darren

  • 7 Posts
  • 1 Reply Like

Posted 3 years ago

  • 1
Photo of Darren

Darren

  • 7 Posts
  • 1 Reply Like
And with GPU acc disabled.
Photo of Jeffrey Tranberry

Jeffrey Tranberry, Sr. Product Manager, Digital Imaging

  • 14147 Posts
  • 1765 Reply Likes
Thanks. I've asked our eng team to take a look. Appreciate the detailed system info.
Photo of Darren

Darren

  • 7 Posts
  • 1 Reply Like
Many thanks :)
Photo of Michelle Qi

Michelle Qi, Employee

  • 10 Posts
  • 1 Reply Like
Hi Darren,

Do you know if Lightroom 6.1.1 worked with this new AMD driver 15.9.1? Trying to figure out if this issue occurred after you update to Lightroom 6.2+ or AMD 15.9.1. Thanks!
Photo of Darren

Darren

  • 7 Posts
  • 1 Reply Like
Hi

I can't be 100% sure but I think the issue was still present in the previous AMD 15.8 beta drivers and build of LR. As i say i can't be 100% though as i've kept GPU acc disabled for a while now but after reading the release notes thought i'd give it another shot to find not much had changed.

Thanks
Photo of Darren

Darren

  • 7 Posts
  • 1 Reply Like
Any news?

Thanks
Photo of Darren

Darren

  • 7 Posts
  • 1 Reply Like
I've 'fixed' the issue.

With MSI Afterburner running in the background GPU acc does not work, with it closed GPU acc works.

It is the OSD of MSI that causes the issue inside of LR, if i disable the MSI OSD and leave it running LR functions fine.
Photo of Chris Cox

Chris Cox

  • 20280 Posts
  • 813 Reply Likes
Thanks for letting us know what you found.
Photo of Darren

Darren

  • 7 Posts
  • 1 Reply Like
No problems, the default key of the OSD of MSI Afterburner is the 'scroll lock' key, simply pressing that to disable the OSD while in LR instantly makes GPU acc work and the blue image disappear :).
Photo of Jeffrey Tranberry

Jeffrey Tranberry, Sr. Product Manager, Digital Imaging

  • 14147 Posts
  • 1765 Reply Likes
Thanks for closing the loop. We saw a similar issue/report early on which prompted us to add the 3rd troubleshooting step here: https://helpx.adobe.com/photoshop/kb/...

Sorry, I should have pointed you at this section initially - but jumped to the conclusion that it might be a problem specific to a newer card.