How to reproduce:
1. Open the project “IN-117286_TestDebugHDRP”
2. Run the project in -batchmode (see notes)
3. Observe the outputted log file

Expected result: The output contains “SetRenderingFeatures” text printed out
Actual result: The log “SetRenderingFeatures” is not printed out

Reproducible with: 2023.1.0a1, 6000.0.59f1, 6000.2.7f1, 6000.3.0b4, 6000.4.0a1

Reproducible on: Windows 11
Not reproducible on: No other environments tested

Notes:

• The project has “Debug.LogWarning("SetRenderingFeatures");” added in “/Packages/com.unity.render-pipelines.high-definition/Runtime/RenderPipeline/HDRenderPipeline.cs”
• The -batchmode command used for testing on Windows 11, cmd:

"<unity-version-directory>\Unity.exe" ^
-batchmode ^
-projectPath "<project-directory>" ^
-logFile “<directory-to-save-log>\batchmodeTest.log"
After running the command, you have to wait until Unity finishes, this can be seen by opening the “batchmodeTest.log” file and looking at the last line.
After Unity has finished executing, kill the process with “taskkill /F /IM Unity.exe /T”

• To edit the HDRP package script, the “com.unity.render-pipelines.core” package is necessary
• The log shows up when the project is opened through the hub and also when entering Play mode