Search Issue Tracker
Fixed in 2020.2.X
Votes
0
Found in
2019.3.0b1
2019.3.4f1
2020.1
Issue ID
1226304
Regression
Yes
[VCS] -vcsMode CLI argument modifies project settings file, need a way to set VCS mode only for one session
Reproduction steps:
1. Open attached project "CLI.zip" folder, ./Project Settings/EditorSettings.asset
2. Observe line 7, "m_ExternalVersionControlSupport: Visible Meta Files"
3. Launch Unity Editor with "-vcsMode Perforce" argument
4. Close Unity Editor
5. In ./Project Settings/EditorSettings.asset, observe line 7
Expected result: It remains "m_ExternalVersionControlSupport: Visible Meta Files"
Actual result: It has changed to "m_ExternalVersionControlSupport: Perforce"
Reproducible with: 2019.3.0b1, 2019.3.9f1, 2020.1.0b4
Not reproducible with: 2019.3.0a12, 2020.2.0a5
Could not test with: 2017.4.39f1, 2018.4.20f1 (-vcsMode CLI argument not available)
-
harry_js
Aug 20, 2020 19:08
Pretty please
-
harry_js
Jun 04, 2020 13:59
Can we get this pushed back into 2019 LTS? This is quite important for cleaner CI logs
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 2020.2):
New CLI argument added in 2020.2.0a13 - vcsModeSession. Use this argument to switch vcs modes for the current session only.