How to reproduce:
1. Ensure that the “Graphics Tools” optional feature is installed through Windows Settings (System → Optional Features)
2. Create and open a new project
3. Build the project (File → Build Profiles → Build)
4. Once the build finishes, navigate to the build folder in Windows Explorer
5. Right-click and select “Open in Terminal”
6. In the terminal window, enter “.\<ProjectName>.exe -force-d3d12-debug” and press Enter
7. Open the Player.log file (%USERPROFILE%\AppData\LocalLow\DefaultCompany\<ProjectName>\Player.log)
8. Observe the result
Actual result: A line in the Player.log shows “Couldn't activate D3D12 debug layer! Make sure to add "Graphics Tools" in Windows Settings”
Expected result: A message is shown indicating that the -force-d3d12-debug argument is not supported on release builds
Reproducible with: 6000.3.11f1, 6000.4.0f1, 6000.5.0a9, 6000.6.0a1
Could not test with: 2023.1.0a4, 6000.0.71f1 (When using the launch argument, a “failed to create D3D12 device (0x80070057)” message is shown, and the Player falls back to using DX11)
Reproducible on: Windows 11
Not reproducible on: No other environments tested
Note: Not reproducible on a development build