Search Issue Tracker
Fixed in 2019.3.X
Votes
0
Found in
2019.3.0a3
Issue ID
1169664
Regression
No
VCS: editor needs a command line argument to set VCS mode
For some Continuous Integration situations it would be helpful to have a command line argument to unity editor that could set the Editor Settings "Version Control" mode setting (m_ExternalVersionControlSupport).
Today it is possible to work around this by either manually editing EditorUserSettings.asset file, or by invoking a static C# method (that one happens "too late" though, after initial import & VCS connection is already done).
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
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
Resolution Note (fix version 2019.3):
Fixed in: 2019.3.0a12