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
- ScrollView speed is slower when entering Play mode
- UI Builder elements disappear and "Semantic - Unknown template name" error appears when changes to "Template" parameter are saved
- Renderers outside Light Probe hull use incorrect Ambient Probe values when "Renderer Light Probe Selection" is set to "Use Ambient Probe" and "Light Probes" on Mesh is set to "Blend Probes"
- ArgumentNullException error occurs when selecting a Camera in the Hierarchy with the Scene view open
- Clicking 'Open Editor Log' through the Console fails to open redirected Logs when relative Log files exist outside of the Project root
Add comment