Search Issue Tracker

Fixed

Fixed in 2020.3.46f1, 2021.3.21f1, 2022.2.8f1, 2023.1.0b5, 2023.2.0a3

Votes

0

Found in

2020.3.43f1

2021.3.16f1

2022.1.24f1

2022.2.2f1

2023.1.0a24

2023.1.0b2

2023.2.0a1

Issue ID

UUM-21728

Regression

No

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

--

-

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)

  1. Resolution Note (fix version 2023.2.0a3):

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

  2. Resolution Note (fix version 2023.1.0b5):

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

  3. Resolution Note (fix version 2022.2.8f1):

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

  4. Resolution Note (fix version 2021.3.21f1):

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

  5. Resolution Note (fix version 2020.3.46f1):

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

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.