Search Issue Tracker
By Design
Votes
0
Found in
5.6.0b5
Issue ID
932877
Regression
No
[Collab] Version control mode remains the same after enabling collab, but selection field becomes disabled
To reproduce:
1. Open new project.
2. Set Project Settings -> Editor -> Version control mode to Hidden meta files
3. Enable collab.
4. Look at Version control mode, value remains the same (hidden)
[optional]
5. Disable collab
6. Set Project Settings -> Editor -> Version control mode to Visible meta files
7. Enable collab.
8. Look at Version control mode, value remains the same (Visible meta files) (and in explorer they are visible)
Actual result: Version control mode remains the same after enabling collab, but selection field becomes disabled
Expected result: Version control mode should be forced to visible meta files (if it's actually necessary) OR Collab seemed to work fine with both visible and invisible meta files., if so, guess this option should be always available, no matter if collab is used or not (maybe user doesn't want to see meta files in explorer even when using collab)
Reproduced on: 2017.3.0a1
Comments (1)
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
wendelay
Sep 30, 2023 02:48
Porque nao add um opcao de ativar e desativar de formar facil? vou tentar amanha, se nao irei desistalar o programa e retornar para Unreal