L

19 Messages

 • 

276 Points

Mon, Apr 5, 2021 5:26 PM

Lightroom Classic: loses connection with files after folder is renamed

I've been using Lightroom for many years, and I've never experienced this problem until the last two updates to the application.

When I upload photos to Lightroom, the app creates a folder that is by default named with the date, in this format: 20210403.

I usually rename the folder, in Lightroom, with something more descriptive, just after the upload is complete. For example, 20210403_family-gathering.

Starting with the previous version of Lightroom, after I perform this action, Lightroom loses the connection with the files in the newly renamed folder. A question mark appears on the folder in the Navigation panel, and in Loupe view, every photo now displays a small exclamation mark in its upper right corner.

When I click on an exclamation mark, a dialog box appears, like the first one of three that I've uploaded.

When I click on "Locate," another dialog box appears. For example:
The first file, which is highlighted, is the one that is missing (although at this point, Lightroom has lost track of all of the files in the renamed folder). When I click the "Select" button, this dialog box appears:
Lightroom is obviously confused, and the only way around this, in the current version of Lightroom, is to quit the application and re-launch Lightroom. After I relaunch Lightroom, it re-finds the files and the exclamation marks are gone. When I quit Lightroom after renaming the folder from the most recent upload, I back up the catalog. I don't know if this is necessary, but I back up the catalog whenever I quit Lightroom.
This is a bug, which never existed for me, until the last two updates of the app.

Responses

Official Solution

Adobe Administrator

 • 

10.9K Messages

 • 

143.5K Points

3 m ago

I am moving this back to in-progress and have advised the team the fix did not work for everyone. 

The Classic Team has requested a new bug which we have written. Some of them may reach out to you for additional information.

Thanks for continuing to update us. 

(edited)

17 Messages

 • 

234 Points

Thanks Rikk. Mostly the fix introduced in 10.3 has worked for me, but twice it has failed in the exact same fashion as before. Soft errors are always hard to nail down!

8 Messages

 • 

138 Points

Thank you. The fix seems to work sometimes! Just seems a bit odd that it ‘loses’ some files occasionally

137 Messages

 • 

2.1K Points

6 m ago

Hello,

I always import photos into a yyyy/mm/dd based folder structure, and then rename the day-based folder to be a little more descriptive -- for example, "2021/04/04 Beach", or something.

New in version 10.2, the renamed folder and the photos within it go "missing" (dark grey icon with question mark on the folder) when I do that. I need to navigate to a different folder and then return to the folder I just renamed and then it will recover -- at least most of the time.

The photos inside the folder do remain marked as "missing" even after that though. When I quit and restart Lightroom Classic, everything is instantly back "online".

Is anyone else experiencing this problem?

System: iMac with MacOS 10.15, catalog lives on the internal SSD, photos are on an external USB3.0 hard drive. Catalog has just been checked for integrity and optimized.

Note: This comment was created from a merged conversation originally titled Lightroom Classic: folders/photos go "missing" after renaming them

1.2K Messages

 • 

13.1K Points

6 m ago

This can happen if the catalog already contains files with the same names. The folder name does not provide uniqueness in this case. However if you first copy the files into a folder within your image structure and then import from that folder, it usually works. But if importing from a camera or memory card then it looks for absolute file name uniqueness. At least on Windows, it has always worked this way for me.

 

The technique I use is to rename files after importing to something meaningful such as Fall_Color_CO_yyyy_mm_nnnn. Then the camera generated names import without issues.

  

  

17 Messages

 • 

234 Points

@bill_3305731

No, that's not what users are experiencing in this case. It's a consistent and reproduceable bug with the latest version on macOS. Renaming a folder following import causes the contents of that folder to be falsely reported as "missing". They are not. And the filenames are unique. That's not an issue.

245 Messages

 • 

2.4K Points

6 m ago

Are you renaming the folder in the Finder, or LR? If the Finder you can't expect LR to know about it, that's why they are lost. You HAVE to do everything inside LR after an import. BTW, it NEVER creates a folder for me, because I create all the folders first (or if I need a new one, right before the import), then select that location to import to (i.e., BotGarden21) and choose to add the next number in that series (so I check the last number that's in that folder, and pick one higher for the new import). Also, ALWAYS rename your files during importing, so you don't get the issue Bill is talking about. Your camera, after 99,999 in some cameras, will revert to 01, and that will conflict with the previous 01.

19 Messages

 • 

276 Points

I always rename the folder in LR, and I always rename files during import into LR. I have been doing this since LR v3, and have never had a problem in the past. There are no files already in the catalog with the same names as the ones I've just imported.

The current LR behavior I've described in my original post is a bug.

Adobe Administrator

 • 

10.9K Messages

 • 

143.5K Points

Are you renaming the folder before the import is complete?

Adobe Photography Products

Quality Engineering - Customer Advocacy

19 Messages

 • 

276 Points

Never. As I stated in my original post:

"I usually rename the folder with something more descriptive, just after the upload is complete. For example, 20210403_family-gathering."

Adobe Administrator

 • 

10.9K Messages

 • 

143.5K Points

I am not able to replicate your issue. 

Information about your system might be helpful

Mac or Windows?

OS version?

Location of Catalog?

Location of folder where files reside?

As the Lightroom Classic Import dialog will allow you to custom name a folder for the import, I have to ask if you have a reason for bypassing this and doing an after the fact rename. 

Adobe Photography Products

Quality Engineering - Customer Advocacy

19 Messages

 • 

276 Points

Mac OS 10.14.6

I use a 2018 MacBook Pro, plus two external hard drives. One of the drives contains the Lightroom catalog. The other drive contains my "photo library" — all of the image files I've imported into Lightroom.

As for why I rename a folder after importing, the simple reason is that's the way I've always done it. Sometimes I don't decide on a custom name until after I've browsed through the images. Would it be possible for me to choose a custom folder name prior to importing the files? Yes, but why should I have to?

1.2K Messages

 • 

13.1K Points

6 m ago

While much less frequent today, Lightroom has historically "lost" files and folders that were rediscovered with a restart. On Windows I've not had this happen on any V10 release.

So they have been steadily fixing it.

 

You are probably right that it's a bug.

  

5 Messages

 • 

90 Points

6 m ago

I have a similar problem.  I am on a iMac 10.14 with the photos on a NAS.  The NAS turns off at night and starts back in the morning.  I am using LrC 10.2.  I did not install the earlier version of Lr 10. The folder I have selected at night, before the NAS goes off, shows the photos and works normally.  In the morning, after the NAS is reconnected, all the folders show connected in the folders panel.  The same folder that was selected at night is still selected and either in grid or loupe view, but the photos have the missing flag.  Here is the strange thing - only the raw files(NEF) are missing, photoshop files are found.  All the other folders are fine.  I can select any of them and none are missing.  If I go back to the original selected file it is still missing.  Quitting Lr and a restart fixes the problem.

Disconnecting the NAS shows all the folders missing.  Reconnect and all the folders show connected.  The parent  and 3 subfolders(one subfolder was the one that shows missing in the morning) show connected but now two of the subfolders show missing raw files.  PSD files are not missing but all NEF files are. This only started with LrC ver 10.

David

245 Messages

 • 

2.4K Points

Don't enable a "Power Schedule" in your Synology Control Panel/Hardware & Power/Power Schedule. This way it won't turn off ever.

1.2K Messages

 • 

13.1K Points

Carlos, if drives have sleep enabled in the drive, it cannot be disabled. It's hardware. Drove me nuts until I figured out what was going on. I wouldn't think that NAS drives are built this way but it is common for normal desktop drives. Some people try to save money by using desktop drives in their NAS, perhaps that's not a good idea?

1 Message

 • 

60 Points

6 m ago

I am having this exact same problem.  I'm on a Macbook Pro, running Catalina version 10.15.7.  Photos are on an EHD.

5 Messages

 • 

90 Points

6 m ago

A little more information.  LrC finds jpeg's and psd's, just can't find the raw files(NEF).  Only with the current folder that was selected before the power went off the previous day.  Quitting and a restart of LrC fixes the problem.  I think this is a bug that was introduced in V10, before that it did not occur.

137 Messages

 • 

2.1K Points

For me it's only like that since v10.2.

5 Messages

 • 

90 Points

Trying to find a sure fire way to reproduce the behavior.  To summarize, the NAS is off 9 hours and then come back.  The folder that was selected when the connection went off, show connected after the reconnection, but all the raw files show missing.  I tried shutting off the NAS for 1 hr and then 2 hrs but no missing files after reconnection.  The interesting thing is the folders that were selected yesterday and there were 4, are all showing connected after the test of shutting down for 1 hr and then 2.  All the other folders are greyed out during disconnect.  The other strange thing is that of the 4 folders that were selected before the night shutdown, two of the folders only have the first image missing and the other 2 have all the images missing.

1.2K Messages

 • 

13.1K Points

Because I've lots of miscellaneous hardware lying around, the first thing I'd do is attach a hard drive to a USB port with a powered cable. I wouldn't use a case with any electronics. Then see if the problem occurs with this setup in place of the SAN.

If this setup works then the odds are that there's a driver problem for the SAN. While possible, it's unlikely to be a hardware problem with the SAN. 

  

People who use non-SAN drives in their SAN do experience all kinds of strange problems but the SAN usually reports them. SAN failures are rarely subtle. 

  

19 Messages

 • 

276 Points

5 m ago

Status update: As Rikk suggested, I followed the "Clean Lightroom Install Procedure," and this did not resolve the problem. Then I remembered that I had second EHD that I wasn’t using and connected that to my computer. I imported a batch of photos to the second EHD, and after the import was complete, I renamed the destination folder in Lightroom and there was no problem. No question mark appeared on the folder, and the individual image files did not display exclamation marks in Loupe view. Lightroom did not lose track of the folder or files.

Later, I imported the folder into my primary Photo Library EHD, using Lightroom's "Move" import setting. Lightroom copied the folder and its contents (.DNG image files), but after the import was finished, the folder name had been stripped of the words I had added when I originally renamed it. The moved folder's name was now in Lightroom's default date format "20100410." I again renamed the moved folder in Lightroom by adding a few descriptive words, and again, Lightroom did not lose track of the folder or its contents.

But importing image files directly into my primary Photo Library EHD and then renaming the destination folder in Lightroom continues to be a problem, and I don't think the problem has anything to do with my primary EHD going to sleep. It's in an enclosure that contains two 3.5-inch, 3 TB hard drives in a RAID 1 [Mirror] configuration. I only power up this EHD when I'm using Lightroom and/or Photoshop, and I don't believe this drive ever sleeps. I can hear it running constantly whenever I use it.

Even though the original problem I described does not occur when I import files to a second EHD, I still consider the problem to be a bug. I've been working with the same hardware configuration and workflow for several years and several iterations of Lightroom, and I've never had this problem before the last two Lightroom updates. My hardware configuration hasn’t changed. Lightroom has changed. 

If Lightroom suddenly refuses to play nice with my hardware and software configuration, that shouldn't be my problem.

Champion

 • 

1K Messages

 • 

15.9K Points

Using MOVE during import does NOT move the folder, only the photos in the folder to a new destination in a different folder as designated in your import destination dialog.

1.2K Messages

 • 

13.1K Points

@Logan31639

 

"I imported a batch of photos to the second EHD, and after the import was complete, I renamed the destination folder in Lightroom and there was no problem."

  

You've proven that your primary hardware is defective. Time to replace it. 

  

19 Messages

 • 

276 Points

I strongly disagree. My ability to import photos to a second, older EHD, and rename an imported folder in Lightroom without issue doesn’t prove anything, and that includes proving that there is no bug in Lightroom v 10.2.

1.2K Messages

 • 

13.1K Points

Are you serious? You need to take a class in logic. "A" fails. "B" works. So the fault must be with "C". 

19 Messages

 • 

276 Points

You need to take a class in science. There are these elements called variables, which you don't seem to be familiar with. There may well be different variables at work here, which you clearly haven't taken into account with your simple logic statement.

(edited)

Adobe Administrator

 • 

10.9K Messages

 • 

143.5K Points

5 m ago

"If Lightroom suddenly refuses to play nice with my hardware and software configuration"

It could be a change in hardware configuration, an OS issue, a failing component, or several other possibilities as well.  Given what you've done in troubleshooting a bug is looking very unlikely.

(edited)

137 Messages

 • 

2.1K Points

We have multiple people who all began to see the same problem at the very same time here. I doubt that's coincidence.

Folder operations in LrC have received improvements in v10 (changelog entry). That's related to what people are having problems with now.

At the same time, there's probably also some Mac users who held out on v10 until the "slow UI" problem was fixed in v10.2, so this is only beginning to show for more people now.

8 Messages

 • 

138 Points

5 m ago

I am running LR Classic 10.2 on OSX Big Sur 11.2. All operations carried on the local disk (not tried on NAS or plugin)

 

For some time the Rename folder in Library module has not worked correctly and the latest update to 10.2 (which I did this week) has made matters even worse.

 

Please note - I am only using LR to move files / rename folder, I am NOT using Finder.

 

After importing images to a folder in my Pictures library (in to a YYYY/MM/DD structure) if I try to rename the folder (say from DD to DD - Beach to make it more meaningful) I right click on the folder in the Folders panel, select Rename and enter new name in the dialog) and click Save.

 

The Folder name in the panel becomes greyed out with a small question mark (?) on the folder icon and the image in the window has an exclamation mark (!) against it. A check in Finder shows that the folder HAS been renamed correctly so it does not appear to be a permissions / security issue.

 

Prior to version 10.2 if I clicked away from the new folder and clicked back it would resolve itself. However since 10.2 this does not happen.

 

If I click on the exclamation mark next to the image I get a message “(image name) could not be used because the original file could not be found. Would you like to locate it?” yet underneath it shows the ‘Previous location….and the correct NEW folder name’!!

 

If I click on Locate it opens a ‘finder’ dialog at the CORRECT new location and with the files displayed. If I highlight the relevant image and click Save, I get a message ‘The file (image name) is associated with another photo in the catalog - Each file can only be associated with one photo’.

 

I have found that if I quit Lightroom and reload then all is resolved…but clearly that is not a viable solution every time I rename a folder and there is clearly some issues with the Rename option, which appears to have been made worse with the latest release.

1.2K Messages

 • 

13.1K Points

Have you noticed whether the number of photos in the folder has an impact? The catalog keeps track of the the full folder / filename for each photo so it has to be updated for every photo in the hierarchy. If you externalize all updates then the photos and XMPs have to be updated as well. 

8 Messages

 • 

138 Points

I have tried with single/multiple images, and with and without subfolders. Always does the same. The folders are being correctly manipulated, as shown in Finder and being shown correctly after quitting and relaunching. No files/folders are being moved / renamed outside of Lightroom, so somehow the catalog is losing sight of the folder during the rename process.

12 Messages

 • 

120 Points

5 m ago

I have a folder structure consisting of about 20k photos. Every time I go to synchronize root folder it says about 6k photos are missing. But they aren't.

This problem happens only when importing files from another catalog. As I migrated to macOS, photos from older Windows 10 were backed up to external HDD alongside its catalog. Then when loading them in Lightroom on Macbook, program says they are missing.

When loading photos in Lightroom on Mac, I pointed their new location on HDD and everything seems ok. Not a single image has a regular exclamation point, no folders are greyed out with a question mark. Photos are not smart previews. I have no problem going into develop module and even exporting so called missing images.

Exiting and opening Lightroom doesn't help as well. I even went so far to create a brand new catalog, where I imported images from the previous one. The problem still persists!

Using latest version of Lightroom Classic 10.2 on Big Sur 11.2.3

UPDATE:

I found the cause of the problem and the solution. All missing files originate from folders that contain one of the following letters in their name: č, ć, ž, š, đ. In order to fix it, I had to go rename folder, but don't actually change anything, just press ok when window Rename folder pops up.

This is clearly a bug, since this problem has never occurred before.

Note: This comment was created from a merged conversation originally titled Lightroom Classic: says photos are missing, but they are actually there

(edited)

Adobe Administrator

 • 

10.9K Messages

 • 

143.5K Points

Can you provide screenshots of the Finder window showing the full path to one of these 'missing images'

Also provide a screenshot of the Lightroom folders panel for the same image. 

I wonder if you have a capitalization problem between the catalog and the OS?

Adobe Photography Products

Quality Engineering - Customer Advocacy

12 Messages

 • 

120 Points

https://imgur.com/a/wIfzt6X

Here are screenshots of my problem, in the first image you can see from Library view that there about 6k photos missing from folder Klijenti. One of those photos is one that is shown.

In the second image, you can see a successful export even though it is said to be missing. Alongside is file info.

When I right click on the image -> Show in Finder, correct location on disk opens in Finder and image is selected. Folder in folders panel also correctly opens, with nothing being greyed out. 

I also tried right click on the folder -> Update Folder Location. Lightroom opens the already correct location in Finder, and when I click on Choose nothing happens.

Adobe Administrator

 • 

10.9K Messages

 • 

143.5K Points

Thank you for posting those but unfortunately they don't provide the information I need. 

I really need to see the screenshots of Finder showing the full path rather than Get Info showing me the same. 

In Lightroom I need to see the Folders Panel with the folder where the reported missing image resides - not the Missing Photos system collection. 

Neither of the screenshots help diagnose the issue. Is it possible for you to post those I've requested?

Adobe Photography Products

Quality Engineering - Customer Advocacy

12 Messages

 • 

120 Points

I am sorry, I misunderstood you.

https://imgur.com/a/SwHcCyS

Does this provide all the info you need?

Adobe Administrator

 • 

10.9K Messages

 • 

143.5K Points

Thank you. Yes that is a better view of what is going on. 

As a test, can you create a new Mac OS user and test the same catalog from the new user account to see if it behaves the same?

Adobe Photography Products

Quality Engineering - Customer Advocacy

67 Messages

 • 

932 Points

5 m ago

I'm having the exact same problem and it just started with latest update.   The error happens frequently...but sometimes the folders come back after about waiting for about 30 seconds, clicking on other folders, crossing my fingers, and/or swearing at Lightroom.  However, all images inside the folders remain missing and I am unable to use "find missing images" as it does nothing.    Otherwise, quitting Lightroom and relaunching always brings them back.  (Not an acceptable fix).  I'm very surprised Adobe "can't reproduce the problem".    It sure seems like a lot of us users can reproduce it.   This happens across all external hard drives that have images in lightroom, except my internal hard drive.  

Latest Lightroom Classic

2019 iMac 5K

Radeon Pro Vega 48 8 GB

Mohave 10.14.6

(edited)

67 Messages

 • 

932 Points

Ok, here's an update:   I opened up another Lightroom Catalog which I don't use very often and it works fine with changing folder names on all external drives.   So it appears that the bug is catalog-specific.    How do we fix this Adobe?   Let's see what happens if I optimize the catalog that's working...  I'll post a reply if anything changes after optimization.  

(edited)

67 Messages

 • 

932 Points

Optimization didn't break it.   I went back to my latest lightroom catalog backup of the catalog with the issue, from about 3 weeks ago... it's got the bug.

137 Messages

 • 

2.1K Points

How old is the catalog where this happens? I'm asking because mine is essentially "ages old" (begins in 2007) and I also went from Windows to Mac with it, and the photos and folder structure in it. Actually @Rikk had that catalog in his hands a while ago to do some repairs on it (on a different issue).

19 Messages

 • 

276 Points

My EHD is a NewerTech Guardian Maximus enclosure RAID-1, with two 3 TB Toshiba hard drives that I purchased from OWC. I've changed a few variables since discovering the problem, including upgrading from Mac OS 14.6 to 15.7, rebuilding the EHD's directory with DiskWarrior 5.2, and swapping the EHD's connection to my 2018 MacBook Pro from an external, CalDigit TS3 Plus Thunderbolt 3 dock to directly in one of the MBP's Thunderbolt ports. I also performed the recommended "Clean Lightroom Install Procedure." None of these changes have resolved the problem, which I still consider to be a bug, regardless of whether a single Adobe administrator can't reproduce the problem. It will only be further investigated by Adobe engineers, and defined as a bug that needs to be addressed, if enough end users complain to hurt the company's image, or profits. If there's any good news, it's that more people are speaking out about the same problem, and that's not a coincidence. Also, for however many people are protesting about the same issue in this forum, we can be sure that others are experiencing the problem who will not register a complaint in this forum.

67 Messages

 • 

932 Points

Have you tried creating a new catalog, adding a few images, and testing to see if the problem occurs with the new catalog?    I have one older catalog that works fine, but the rest of them have the same bug.  However new catalogs seem to work ok, though I've not tested a new catalog with a LOT of images.   I personally don't want to have to create an entirely new catalog and re-import all of my images to get rid of this bug. 

 

Adobe Administrator

 • 

10.9K Messages

 • 

143.5K Points

5 m ago

Though we've not been able to reproduce this behavior I've opened a ticket for investigation with the team. You may be contacted by an engineer for additional information.

Thank you for your patience. 

17 Messages

 • 

234 Points

Thanks Rikk. I can provide any data points you need regarding this issue. I have seen it across numerous client installations.

Adobe Administrator

 • 

10.9K Messages

 • 

143.5K Points

Thanks, I will let the team know. 

Adobe Photography Products

Quality Engineering - Customer Advocacy

2 Messages

 • 

90 Points

I have the exact same problem with the following configuration:

MacBook Pro 15' macOS Big Sur 11,3,1

2,4 GHz Intel Core i9 8 cœurs

32 Go 2400 MHz DDR4

LrC 10.2

LrC catalog path (SSD inside) :
Macintosh HD/Users/Milek/Pictures/Lightroom

At your disposal if you want to upload my catalog to reproduce the bug.

(edited)

67 Messages

 • 

932 Points

5 m ago

I've now determined that any new catalogs I create exhibit the same behavior, however one catalog I have works fine.  I've successfully copied that catalog and the copy works.  So now if I ever want to create a new catalog I need to make a copy of the only one that works, delete images I don't want, and add the ones that I want.  BTW, I wanted to add that the only bug I've found is that images get lost after renaming folders but moving folders/images around is perfectly fine and Lightroom tracks them just fine.  It's very specific to renaming.   

UPDATE: This one catalog that used to work fine now also has the same problem.  It worked for about 4 hours of use.  So now the problem occurs no matter which catalog I am using.

This is the information on my system and the catalog that (used to) work, while it was working.   

Lightroom Classic version: 10.2 [ 202103041821-226a1211 ]
License: Creative Cloud
Language setting: en-US
Operating system: Mac OS 10
Version: 10.14.6 [18G8022]
Application architecture: x64
Logical processor count: 16
Processor speed: 3.6 GHz
SqLite Version: 3.34.0
Built-in memory: 65,536.0 MB
Real memory available to Lightroom: 65,536.0 MB
Real memory used by Lightroom: 17,328.4 MB (26.4%)
Virtual memory used by Lightroom: 29,143.0 MB
Memory cache size: 949.9MB
Internal Camera Raw version: 13.2 [ 738 ]
Maximum thread count used by Camera Raw: 5
Camera Raw SIMD optimization: SSE2,AVX,AVX2
Camera Raw virtual memory: 280MB / 32767MB (0%)
Camera Raw real memory: 282MB / 65536MB (0%)
Displays: 1) 5120x2880, 2) 1920x1200

Graphics Processor Info: 
Metal: AMD Radeon Pro Vega 48

Application folder: /Applications/Adobe Lightroom Classic
Library Path: /Volumes/SAMSUNG SSD/LIGHTROOM IMAGE CATALOG T5/Lightroom Image Catalog-v10.lrcat
Settings Folder: /Users/gregwhite/Library/Application Support/Adobe/Lightroom

Installed Plugins: 
1) AdobeStock
2) Aperture/iPhoto Importer Plug-in
3) Aurora HDR 2019
4) Blurb BookSmart
5) DxO PhotoLab
6) DxO PhotoLab 2
7) DxO PhotoLab 2 Importer
8) DxO PhotoLab 3
9) DxO PhotoLab 3 Importer
10) DxO PhotoLab Importer
11) Export to Photomatix Pro
12) Facebook
13) Flickr
14) FocalPoint
15) HDR Efex Pro
16) HDR Efex Pro 2
17) LRT Export 5
18) Luminar 4
19) Nikon Tether Plugin
20) onOne Perfect Photo Suite
21) Perfect Effects
22) Perfect Portrait
23) Perfect Resize
24) PhotoFrame
25) PhotoTools 2.6
26) PhotoTune
27) SmugMug
28) Upload To Pictage

Config.lua flags: 
Features.disableGlobalTaskManager = true

AudioDeviceIOBlockSize: 512
AudioDeviceName: $$$/dvaaudiodevice/SystemDefaultAndEffectiveDeviceName=System Default (Built-in Output)#{comment}DVAAU-4201250: Open the audio hardware preferences page.
AudioDeviceNumberOfChannels: 2
AudioDeviceSampleRate: 48000
Build: LR5x77
CoreImage: true
GL_ACCUM_ALPHA_BITS: 0
GL_ACCUM_BLUE_BITS: 0
GL_ACCUM_GREEN_BITS: 0
GL_ACCUM_RED_BITS: 0
GL_ALPHA_BITS: 8
GL_BLUE_BITS: 8
GL_DEPTH_BITS: 24
GL_GREEN_BITS: 8
GL_MAX_3D_TEXTURE_SIZE: 16384
GL_MAX_TEXTURE_SIZE: 16384
GL_MAX_TEXTURE_UNITS: 8
GL_MAX_VIEWPORT_DIMS: 16384,16384
GL_RED_BITS: 8
GL_RENDERER: AMD Radeon Pro Vega 48 OpenGL Engine
GL_SHADING_LANGUAGE_VERSION: 1.20
GL_STENCIL_BITS: 8
GL_VENDOR: ATI Technologies Inc.
GL_VERSION: 2.1 ATI-2.11.23
OGLEnabled: true
GL_EXTENSIONS: GL_ARB_color_buffer_float GL_ARB_depth_buffer_float GL_ARB_depth_clamp GL_ARB_depth_texture GL_ARB_draw_buffers GL_ARB_draw_elements_base_vertex GL_ARB_draw_instanced GL_ARB_fragment_program GL_ARB_fragment_program_shadow GL_ARB_fragment_shader GL_ARB_framebuffer_object GL_ARB_framebuffer_sRGB GL_ARB_half_float_pixel GL_ARB_half_float_vertex GL_ARB_imaging GL_ARB_instanced_arrays GL_ARB_multisample GL_ARB_multitexture GL_ARB_occlusion_query GL_ARB_pixel_buffer_object GL_ARB_point_parameters GL_ARB_point_sprite GL_ARB_provoking_vertex GL_ARB_seamless_cube_map GL_ARB_shader_objects GL_ARB_shader_texture_lod GL_ARB_shading_language_100 GL_ARB_shadow GL_ARB_shadow_ambient GL_ARB_sync GL_ARB_texture_border_clamp GL_ARB_texture_compression GL_ARB_texture_compression_rgtc GL_ARB_texture_cube_map GL_ARB_texture_env_add GL_ARB_texture_env_combine GL_ARB_texture_env_crossbar GL_ARB_texture_env_dot3 GL_ARB_texture_float GL_ARB_texture_mirrored_repeat GL_ARB_texture_non_power_of_two GL_ARB_texture_rectangle GL_ARB_texture_rg GL_ARB_transpose_matrix GL_ARB_vertex_array_bgra GL_ARB_vertex_blend GL_ARB_vertex_buffer_object GL_ARB_vertex_program GL_ARB_vertex_shader GL_ARB_window_pos GL_EXT_abgr GL_EXT_bgra GL_EXT_bindable_uniform GL_EXT_blend_color GL_EXT_blend_equation_separate GL_EXT_blend_func_separate GL_EXT_blend_minmax GL_EXT_blend_subtract GL_EXT_clip_volume_hint GL_EXT_debug_label GL_EXT_debug_marker GL_EXT_depth_bounds_test GL_EXT_draw_buffers2 GL_EXT_draw_range_elements GL_EXT_fog_coord GL_EXT_framebuffer_blit GL_EXT_framebuffer_multisample GL_EXT_framebuffer_object GL_EXT_framebuffer_sRGB GL_EXT_geometry_shader4 GL_EXT_gpu_program_parameters GL_EXT_gpu_shader4 GL_EXT_multi_draw_arrays GL_EXT_packed_depth_stencil GL_EXT_packed_float GL_EXT_provoking_vertex GL_EXT_rescale_normal GL_EXT_secondary_color GL_EXT_separate_specular_color GL_EXT_shadow_funcs GL_EXT_stencil_two_side GL_EXT_stencil_wrap GL_EXT_texture_array GL_EXT_texture_compression_dxt1 GL_EXT_texture_compression_s3tc GL_EXT_texture_env_add GL_EXT_texture_filter_anisotropic GL_EXT_texture_integer GL_EXT_texture_lod_bias GL_EXT_texture_mirror_clamp GL_EXT_texture_rectangle GL_EXT_texture_shared_exponent GL_EXT_texture_sRGB GL_EXT_texture_sRGB_decode GL_EXT_timer_query GL_EXT_transform_feedback GL_EXT_vertex_array_bgra GL_APPLE_aux_depth_stencil GL_APPLE_client_storage GL_APPLE_element_array GL_APPLE_fence GL_APPLE_float_pixels GL_APPLE_flush_buffer_range GL_APPLE_flush_render GL_APPLE_object_purgeable GL_APPLE_packed_pixels GL_APPLE_pixel_buffer GL_APPLE_rgb_422 GL_APPLE_row_bytes GL_APPLE_specular_vector GL_APPLE_texture_range GL_APPLE_transform_hint GL_APPLE_vertex_array_object GL_APPLE_vertex_array_range GL_APPLE_vertex_point_size GL_APPLE_vertex_program_evaluators GL_APPLE_ycbcr_422 GL_ATI_blend_equation_separate GL_ATI_blend_weighted_minmax GL_ATI_separate_stencil GL_ATI_texture_compression_3dc GL_ATI_texture_env_combine3 GL_ATI_texture_float GL_ATI_texture_mirror_once GL_IBM_rasterpos_clip GL_NV_blend_square GL_NV_conditional_render GL_NV_depth_clamp GL_NV_fog_distance GL_NV_light_max_exponent GL_NV_texgen_reflection GL_NV_texture_barrier GL_SGI_color_matrix GL_SGIS_generate_mipmap GL_SGIS_texture_edge_clamp GL_SGIS_texture_lod 

(edited)