Search Issue Tracker
By Design
Votes
0
Found in
5.5.1p3
Issue ID
960773
Regression
No
Removing the Readonly flag on a file in Unity will not cause P4 to checkout the file
if you remove the readonly flag on a file Unity will think it is checked out but not perforce
The file should be checked out in both Unity and in Perforce.
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
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
- Addressables content build fails but the Player build is successful when building a development build
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
Resolution Note:
We don't support external changes to unity files like this.
Version control related operations need to be done in Unity or in p4v.