"Camera Raw Graphics Acceleration Is Not Supported By Your System"

[#1]

I have a couple of different user logins to my MacBook Pro, and when I edit in Camera Raw with one login, Camera Raw doesn't use the computer's graphics processor, and when I open the ACR Preferences, instead of being able to select "Auto," "Custom," or "Off," the settings window shows "Camera Raw Graphics Acceleration Is Not Supported By Your System."

However, when a different user login is used, Camera Raw uses the graphics processor and everything works as it should.

I've tried uninstalling everything Adobe related and reinstalling, but run into the same issue.

Without graphics acceleration, cropping or straightening raw photos is painfully slow.

I'm using a 2020 13-inch MacBook Pro with Intel Iris Plus Graphics 1536 MB running macOS Big Sur version 11.1

Photoshop is version 22.1.0, and Camera Raw is version 13.1.0.658

[#2]

I have a couple of different user logins to my MacBook Pro, and when I edit in Camera Raw with one login, Camera Raw doesn't use the computer's graphics processor, and when I open the ACR Preferences, instead of being able to select "Auto," "Custom," or "Off," the settings window shows "Camera Raw Graphics Acceleration Is Not Supported By Your System."

However, when a different user login is used, Camera Raw uses the graphics processor and everything works as it should.

I've tried uninstalling everything Adobe related and reinstalling, but run into the same issue.

Without graphics acceleration, cropping or straightening raw photos is painfully slow.

I'm using a 2020 13-inch MacBook Pro with Intel Iris Plus Graphics 1536 MB running macOS Big Sur version 11.1

Photoshop is version 22.1.0, and Camera Raw is version 13.1.0.658

[#3]

I've followed troubleshooting advice I've seen on other forums, and nothing listed below has worked.

I couldn't find a TempDisableGPU file either.

Troubleshooting GPU AccelerationProblems

If GPU acceleration is not enabled or not working as expected, use the following troubleshooting guide to gather more information.

1. Verify You Have Installed the Latest Version of Camera Raw or Lightroom 2. Verify Your System Meets the Requirements for GPU Acceleration

Note For Lightroom Classic 8.4 and later and Lightroom 3.0 and later the technical GPU hardware and software requirements for GPU acceleration are exactly the same as for Camera Raw.

• Camera Raw GPU System Requirements (Note: this may be the older 11.4 requirements)
• Lightroom Classic GPU System Requirements (Note: this may be the older 8.4 requirements)

3. Examine the Preferences Dialog

Open the Camera Raw or Lightroom preferences and examine what information about the error and the system is available there, on the Performance tab. When reporting problems on user forums or to technical support, it’s useful to include this information.

1. The exact version of Camera Raw or Lightroom
2. The name of the GPU
3. The amount of GPU Ram
4. Current position of the options and checkboxes
5. The status message. (Which may note an error.)

4. Collect Detailed Logs

Please collect and send logs to Adobe when reporting problems.

IMPORTANT You must QUIT the host application (Bridge, Photoshop or Lightroom) BEFORE you collect the log files.

Logging related to GPU acceleration are written to the same folder for Camera Raw, Lightroom and Lightroom Classic.

The best way to collect a log about a bug is to.

1. Quit the host app.
2. Re-launch the host app.
3. Perform the minimum number of steps required to reproduce the problem.
4. Quit the host app again.
5. Now collect the log files.

On Windows the log location is:

%APPDATA%\Adobe\CameraRaw\Logs

One shortcut to get to this folder on Windows is to…

1. Tap the Windows key
2. Enter “Run”
3. Enter “%APPDATA%\Adobe\CameraRaw\Logs”

For example:

C:\Users\tester\AppData\Roaming\Adobe\CameraRaw\Logs

On Mac the log location is:

~/Library/Application Support/Adobe/CameraRaw/Logs

For example:

/Users/tester/Library/Application Support/Adobe/CameraRaw

One shortcut to get to this folder on Mac is to…

1. In the Finder open the Go menu.
2. Select Go to Folder…
3. Enter the path ~/Library/Application Support/Adobe/CameraRaw
4. Click Go

4.5 Windows Only: Save the DxDiag Report

The tool dxdiag produces a report that may be helpful to the engineering team when investigating problems.

1. Tap the Windows key on your keyboard or click on the Windows button in the task bar.
2. Type in dxdiag (this does a search for the program)
3. Hit the Enter key
4. Wait for the DxDiag window to appear.
5. When it’s enabled click the Save All Information button
6. Save the DxDiag.txt file and submit it when reporting problems

5 Update Your Drivers and OS

If you see issues, the first thing to do is note the OS version and GPU driver version you have now, try updating to the latest versions, then see if the problem persists.

If updating the OS or GPU driver is a fix, please report your findings (Ex: “version n is busted but n+1 works.”)

6 Check for and Delete TempDisableGPU3 or TempDisableGPU2 Files

Using the same methods you used to find the Logs folder, find the CameraRaw/GPU folder.

On Windows the location is:

%APPDATA%\Adobe\CameraRaw\GPU

On Mac the location is:

~/Library/Application Support/Adobe/CameraRaw/GPU

If an un-handled, fatal error occurs during GPU initialization, Camera Raw or Lightroom will leave behind a file named TempDisableGPU3 or TempDisableGPU2.

In the GPU folder find the sub folder for the application you are using and check for these files.

If a TempDisableGPU file exists at initialization time, Camera Raw will disable GPU acceleration. This prevents any sort of bad crashing bugs that happen during initialization from making the app crash every launch.

You can delete the file to run initialization again. If the original failure condition is transient, GPU acceleration may work correctly after deleting the file.

If you find a TempDisableGPU file, try the following troubleshooting steps.

1. Quit the app.
2. Delete the TempDisableGPU file.
3. Relaunch the app.
4. Open app and preferences dialog.
5. Check the GPU status again in the–is it working now?
6. Check to see if a TempDisableGPU file was created again.
7. Quit the host app.
8. Collect logs.