Search Issue Tracker
Fixed
Votes
0
Found in
4.2.0a4
Issue ID
540664
Regression
No
Version control is disabled if e.g. out of date files
Version: Version 4.2.0a4 (446ff42468b3)
Version control plugin: Perforce
1. Two editor instances, both updated with latest files from depot
2. Instance #1: Modify e.g. a material and check it in
3. Instance #2: Modify same material and check it in (without getting latest)
(Can also be repro’ed by e.g. trying to submit file locked by another client)
Result:
Message from P4 shown in console:
Version Control General: Out of date files must be resolved or reverted.
Submit failed -- fix problems above then use 'p4 submit -c 17'.
But then version control gets disabled
At least in this case, version control shouldn’t be disabled, as we would like to resolve files right away.
Workaround is to click “Settings” and reconnect to Perforce.
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
Add comment