Search Issue Tracker
Fixed in 2022.1.X
Votes
0
Found in
2021.2
2022.1
Issue ID
1354146
Regression
No
[deprecated] BuildOptions.EnableHeadlessMode needs clearer warning for its conflicts with BuildOptions.subtarget field
How to reproduce:
1. Open attached project "ServerBuildHeadless.zip" and scene "SampleScene"
2. In Editor Menu, click Bug -> Repro
3. After the build completes, observe the executed Build
Expected result: A Dedicated Server application is launched
Actual result: A Standalone application is launched, the user isn't informed about conflicts between BuildOptions.EnableHeadlessMode and BuildOptions.subtarget field
Reproducible with: 2021.2.0b5, 2022.1.0a4
Could not test with: 2019.4.29f1, 2020.3.15f1, 2021.1.16f1 (Dedicated Server functionality not implemented)
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
- Any small change in UI Builder Inspector refreshes Editor Inspector
- Inaccurate Box Collider boundaries on a rotated child Cube when the parent GameObject Scale is non-uniform
- [Android] "SHADOWS_SCREEN" set as shader Keyword when no "_ShadowMapTexture" is bound leads to freeze on a build on some Mali GPU devices
- The global scene list is overridden in a project built with command line when the Override Global Scene List setting is disabled in the build profile
- Global Scenes are not included in the Build when building multiple Build Profiles at the same time
Resolution Note (fix version 2022.1):
Fixed in 2022.1.0a8.
Passing BuildOptions.EnableHeadlessMode = true will automatically adjust the subtarget to kStandaloneBuildSubtargetServer given the platform group is compatible otherwise it will be ignored. This should be enough to maintain backward compatibility until the option is completely removed.