Search Issue Tracker
Duplicate
Votes
5
Found in
2019.4
2020.3
2020.3.28f1
2021.2
2022.1
2022.2
Issue ID
1409347
Regression
No
Player lighting not generated when building the project using command line
How to reproduce:
1. Create a new project
2. Add a GameObject to the scene (e.g. Cube)
3. Go to File > Build Settings and press Add Open Scenes
4. Close the Editor
5. Build the project using command line
Expected result: The Player has lighting generated
Actual result: The Player doesn't have lighting generated
Reproducible with: 2019.4.36f1, 2020.3.32f1, 2021.2.16f1, 2022.1.0b13, 2022.2.0a9
Notes:
1. Not reproducible on macOS
2. If you go to Window > Rendering > Lighting and click Generate Lighting then the issue is not reproducible
Command used on windows:
Unity.exe -batchmode -projectPath "projectPath" -buildTarget Win64 -logFile .\Build\Windows\CommandLine.log -releaseCodeOptimisation -quit -buildWindows64Player "playerPath\build.exe"
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
- Opening Terrain Prefab in Prefab Editing Mode throws "NullReferenceException" error
- [Search] Dragging query pills put them behind the search text field
- A CustomPropertyDrawer that returns a PropertyField for a property named the same as a child field will not render all child fields
- Graphics Settings shows default values instead of the real values in the Rendering Debugger when Volume.profile is assigned via script
- Deleting multiple Tags throws “NullReferenceException”, and "Retrieving array element that was out of bounds" errors when holding the Enter key
This is a duplicate of issue #1375015