files submitted to Perforce are set to have read/write permission

[OrbitalZones]

I am facing an issue with Perforce, even if only for a single project. The Perforce depots are accessed by a super user, there is only one workspace that contain a bunch of projects. All Perforce permissions are the same. There are no such issues with the other projects.

When pulling the project files from Perforce to a new computer, all files have read/write permisions per default. - They are not checked out, but they have write permission !

When checking in a file, file access is set to read/write. - Files can be checked out from other computers, but still can be modified locally as well

But most strange, when permission of an already checked out file is set manually to read only, submitting it to Perforce server will change the permission back to read/write.

Anyone ever had something like this? What could I do to solve this, other then to re-create the project in the Perforce workspace?

[OrbitalZones]

After checking the file history of one of the affected assests, I noticed that they are stored in the Helix depot with+w at the end. I remeber some ‘experimental’ changes that I made in the typemap file, could be that the file types were set to ‘binary+w’ for Unreal asset files. But not longer than half a day, then I set all types back to default (without any option).

But anything that have been submitted that time, has been saved as ‘binary+w’.

Solution:

• Compress the affected files/folders to a .zip archive - do not move or copy them !
• mark the folders to delete, submit that change to Helix depot (will delete local files as well)
• unzip the files/folders to their original loication in the Unreal project
• mark them to add and submit to the depot again

I still can check-out the old revisions

Strange that the p4 client did not check the typemap file, after I have reverted my changes.