Search Issue Tracker
Fixed in 2022.1.X
Votes
0
Found in
2017.4
2018.4.22f1
2020.2
Issue ID
1249100
Regression
No
-openscene command line agrument doesn't open scenes when using -batchmode
How to reproduce:
1. In the attached project "batchmode.zip", edit the "run.bat" or "run.sh" file and set the correct Unity Editor path
2. Execute the "run.bat" or the "run.sh" file and wait until it closes
3. Locate your "Editor.log" file:
Windows: C:\Users\username\AppData\Local\Unity\Editor\Editor.log
macOS: ~/Library/Logs/Unity/Editor.log
Linux: ~/.config/unity3d/Editor.log
4. Open the "Editor.log" file and locate keywords "current scene"
Expected result: "Editor.log" shows "current scene: Assets/Scenes/SampleScene.unity"
Actual result: "Editor.log" shows "current scene: "
Reproducible with: 2017.4.40f1, 2018.4.23f1, 2019.4.0f1, 2020.1.0b12, 2020.2.0a14
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Scrolling on a default ScrollView in a WebGL build is too sensitive when compared to other platform builds and the Editor
- "Fix All" button does not disappear after applying fixes when setting up DXR
- Custom ScriptableObject asset in the project setting are not well deserialized during the Reimport All process
- Fixing Message Loss in UMPE During Domain Reload
- The Editor freezes when ScheduleReadOnly of IJobParallelForTransform with dependency is used
Resolution Note (fix version 2022.1):
Fixed in: 2022.1.0a7