- 2 Posts
- 1 Reply Like
Posted 2 years ago
Venkatesh Penjuri, Official Rep
- 48 Posts
- 13 Reply Likes
Are you on Windows? Could you share us your system info here?
Help->System info->Save as and share the text file.
Thanks
- 2 Posts
- 1 Reply Like
Venkatesh Penjuri, Official Rep
- 48 Posts
- 13 Reply Likes
Chandan Kumar, Official Rep
- 28 Posts
- 11 Reply Likes
Thanks,
Chandan
- 4 Posts
- 2 Reply Likes
Venkatesh Penjuri, Official Rep
- 48 Posts
- 13 Reply Likes
Thanks
- 4 Posts
- 2 Reply Likes
crash report was sent
- 4 Posts
- 2 Reply Likes
(windows 10, latest graphic card driver)
do better not update!
Victoria Bampton - Lightroom Queen, Champion
- 5308 Posts
- 2091 Reply Likes
- 1 Post
- 0 Reply Likes
- 203 Posts
- 62 Reply Likes
switching to Develop module with GPU support on blacks out my image:


interesting:
when restarting Lightroom the first switch to develop module works correctly, switching back to the library module and the again to develop another picture leads to this black image phenomenon
- 9 Posts
- 1 Reply Like
I also note a seeming disconnect between the filmstrip selected photo and the selected photo identified in the grid....
Victoria Bampton - Lightroom Queen, Champion
- 5333 Posts
- 2110 Reply Likes
- 203 Posts
- 62 Reply Likes
- 9 Posts
- 1 Reply Like
- 203 Posts
- 62 Reply Likes
The bug (black image) does not occur when starting LR, switching the ONCE to the development module and then moving between images (using the filmstrip).
It only occurs when switching back to the library module selecting another image and switching to the development module with this new image!!
As I wrote the bug occurs also when Develop.PreferOpenGL = true.
It occurs also when using the newest video driver.
It didn't occur in LR CC 7.12.
Simon Chen, Principal Computer Scientist
- 1681 Posts
- 577 Reply Likes
- 203 Posts
- 62 Reply Likes
Why did LR 7.12 work with my video card and driver and activated GPU support and the new version fails after switching twice to the development module?
Is there a logging option to help Adobe identify the exact error scenario on my system?
Simon Chen, Principal Computer Scientist
- 1681 Posts
- 577 Reply Likes
- 203 Posts
- 62 Reply Likes
Tip#3 (disabling GPU support) is of course a minimal option.
- 2 Posts
- 4 Reply Likes
The second screen still shows the image.
- 196 Posts
- 52 Reply Likes
- 2 Posts
- 4 Reply Likes
Lightroom Classic version: 7.0.1 [ 1142117 ]
License: Creative Cloud
Operating system: Windows 7
Version: 6.1
Application architecture: x64
System architecture: x64
Logical processor count: 8
Processor speed: 2,8 GHz
Built-in memory: 8182,0 MB
Displays: 1) 1920x1200, 2) 1920x1200
Input types: Multitouch: No, Integrated touch: No, Integrated pen: Yes, External touch: No, External pen: Yes, Keyboard: No
Graphics Processor Info:
OpenGL: AMD Radeon HD 5700 Series
Check OpenGL support: Passed
Vendor: ATI Technologies Inc.
Version: 3.3.13417 Core Profile Context 15.301.1901.0
Renderer: AMD Radeon HD 5700 Series
LanguageVersion: 4.40
Total Video Memory: 1011 MB
I downloaded the 16.2.1 Radeon drivers, Crimson edition. These are the latest although over a year old. They did not fix this issue.
I guess I failed to make clear in my initial response that there was not only a very simple way to reproduce the phenomenon that you raise, but that the way it occurs suggests the bug is in Lr and not in any of the other components of the system.
We have a common goal here.
Trust this helps
- 203 Posts
- 62 Reply Likes
Another detail for you Adobe guys to solve the problem:
When you start LR CCC with GPU support enabled and with a picture in development mode you can move between the images using the filmstrip without any Problem AS LONG AS YOU STAY IN DEVELOPMENT MODE. When you switch to library mode everything works fine. But switching back to development mode you have to select a picture which was already opened in development mode before (e.g. those which was selected when you switched to library mode).
Otherwise (when you Switch to development mode having selected a "new" Picture) this black Screen issue occurs.
So it seems to be a bug in a part of your code which is executed to load the picture into memory when switching from library to development mode.
- 2 Posts
- 0 Reply Likes
What a joke ... I hope that Adobe will solve this problem asap
Simon Chen, Principal Computer Scientist
- 1681 Posts
- 577 Reply Likes
- 1 Post
- 0 Reply Likes
Setting Config.lua-Flags:
AgView.disableDirect2D = true
Fixed the issue. Switching on/off the use of the GPU made no difference.
Maybe it helps on debugging or others to fix their issue...
Mike
- 3 Posts
- 1 Reply Like
Since switching to Classic CC I am getting a black screen when move from Library to Develop. The R/A and Y/Y options display properly, and when I close LR in the develop mode, the photo shows correctly when I re-open the program.
Library Mode:

Switch to Develop mode (the histogram responds to changes):

Switch to Y/Y in develop mode:

I am using Windows 7 Professional 64.
I have un-installed and re-installed with re-set preferences.
Please Help
Brian Price
- 3 Posts
- 1 Reply Like
- 203 Posts
- 62 Reply Likes
It's really strange that the picture is displayed properly in devekop mode when switching to Y/Y options but in normal display mode we only get a black screen.
Please fix this bug to reenable the GPU enable option!
- 2 Posts
- 0 Reply Likes
Enabling GPU acceleration in Lightroom Classic CC causes the entire photo in be black in the develop module.
Closing and restarting Lightroom will fix the issue, but it returns if I go into the LIbrary module, and then select a different photo to develop.
Disabling GPU acceleration is the only way to definitively fix the issue. I am working with 46 MP files on a 2560 x 1440 monitor, disabling the GPU is unacceptably slow.
I reinstalled Lightroom CC (2015) and it does not have this issue, I can use GPU acceleration without a problem.
I bought a new video card (Radeon RX 580) and updated with the latest drivers in an attempt to fix this issue.
Interestingly enough, if I use the crop tool inside develop mode, the photo renders perfectly fine.
- 203 Posts
- 62 Reply Likes
Seems that in development module it now wirks fine when you switch between images INSIDE a collection. (this also didn't work with LR 7.1)
But when you switch to another collection/folder the black screen phenomenon still appears! :(
- 203 Posts
- 62 Reply Likes
- 203 Posts
- 62 Reply Likes
I'm somehow tired of replies like "The black screen issue is most likely due to some driver compatibility or bugs. Do a complete clean install the latest GPU driver."Using a 4k display the GPU support is highly necessary for speed reasons and the exact issue description and observations in this thread make it - in my eyes - evident that there is a bug in Lightroom which causes this behavior.
- 203 Posts
- 62 Reply Likes
They even read the forum discussions in the Adobe forums (this is good customer support, Adobe!).
AMD summary after 4 loops of different approaches to solve the bug and get information per logs:
"Da Sie in Ihrer ersten email zwei Forum Beiträge verlinkt haben, und in beiden dasselbe Fehlverhalten auch von Nutzern mit Nvidia Grafikkarten zu lesen ist, kann ich mir schwer vorstellen dass das Problem an dem AMD Treiber liegt. Scheinbar ist die GPU-Unterstützung ein Feature von Lightroom, das noch nicht ausgereift ist, ich würde jedenfalls mit den aktuell gegebenen Informationen den Fehler auf der Seite von Adobe vermuten.""As there are several comments in the forums which describe the error to occur with AMD and NVIDIA video adapters, I can hardly imagine that the bug is located in the AMD driver. It seems that GPU support is a Lightroom feature which is not mature yet. Anyway, with the current information I would suspect the error to be on Adobe's side."
- 203 Posts
- 62 Reply Likes
- 203 Posts
- 62 Reply Likes
After trying another video adapter from another PC which worked fine ona WIndows 10 PC while also having the same issue on my main LR WIndows 7 PC I finally found what causes the problem:
when I use my GPU via DirectX everything works fine (also after change of libraries)

when I use OpenGL instead (e.g. by using the config.lua flag Develop.PreferOpenGL) the issue causes the black screen

The only problem is:When using Windows 7 there is always OpenGL used (as the newest DirectX version don't work with Win7).
When using Windows 10 I can selecht between DirectX and OpenGL.
I would be very pleased if you Adobe guys could try to reproduce this issue with the new information (switch to OpenGL by using the config.lua flag and change folder in Develop mode) to locate the bug.
- 2 Posts
- 0 Reply Likes
Same fix as usual - I just updated the driver for my video card and that fixed it.
*******************************************************************************************
I had the same problem a couple of years ago.
Word usually gets out to the Graphic card manufacturers pretty fast.
Some of the manufacturers list the release date of the drivers and occasionally you will see a new update 2 days after the previous update (where someone goofed)
Related Categories
-
Lightroom Classic
- 14875 Conversations
- 3742 Followers