Unity Issue Tracker - Editor.log isn't created when the Editor is ran from a command line with a "-nographics" option included

2023.2.X

2023.1.X

2022.2.X

2021.3.X

2020.3.X

2022.1.X

Documentation: Documentation update surrounding logs when running -batchmode with -nographics.

Documentation: Documentation update surrounding logs when running -batchmode with -nographics

Documentation: Documentation update surrounding logs when running -batchmode with -nographics.

2022.1 has reached end of life so the issue will be fixed in a newer version.

Documentation: Documentation update surrounding logs when running -batchmode with -nographics.

Reproduction steps:

Delete the “Editor.log” file located in the “%AppData%\Local\Unity\Editor” folder
Run the attached project (MyProject.zip) from the command line using the “ {Unity.exe path}
-projectPath
{project path}
-quit -batchmode -nographics” command
Observe the “%AppData%\Local\Unity\Editor” folder

Expected result: “Editor.log” file has been created and contains Editor runtime information
Actual result: “Editor.log” is not created

Reproducible with: 2020.3.43f1, 2021.3.16f1, 2022.1.24f1, 2022.2.2f1, 2023.1.0a24

Reproducible on: Windows 10 (21H2)

Editor.log isn't created when the Editor is ran from a command line with a "-nographics" option included