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
- Highlighter.Highlight does not find window when using class name as window title
- Highlighter.Highlight highlights a different component when multiple components have the same property path
- Highlighter.Highlight does not find elements in an array or list when the array or list is collapsed
- [URP][NRP] RenderPass, BeginSubPass, and EndRenderPass errors are thrown when Native RenderPass is enabled
- D3D11 swapchain error pop-up appears and the Editor shuts down when Generating Lighting with Probe Volumes present
This is a duplicate of issue #1375015