Good evening,
I’m trying to setup a small unity project with perforce helix core (on a server).
We are a small team of 4 people, never worked with perforce.
To my problem: Everytime I open Unity a Temp folder is created in my workspace. In the temp folder is a file called TutorialLayout.wlt. Unity now is throwing an Exception UnauthorizedAccessException: Access to the path "E:\Perforce\workspace_b\project\Temp\TutorialLayout.wlt" is denied.
I think this is because every file is read-only before you Checkout, but checking out the whole project is kind of false workflow for me. I already added the Temp folder to the .p4ignore and the typemap.
It appears that your Temp folder was pushed to the depot at some point, and its content is now under version control.
As you correctly pointed out, Perforce puts all controlled files in read-only mode as a way to force the checkouts.
If there is no need for the Temp folder to be under control, I suggest removing it from the depot and keeping only the local folder, which would no longer be shielded by Perforce.
For reference, this is the initial list of project folders that are normally synced to version control:
Good morning,
It’s been a year since the first post, but I have the exact same issue with the exact same file, except the Temp folder is in the workspace but NOT included in the depot nor any changelist.
I have tried:
Manually removing the read-only
Adding it as Mark for Add in a changelist, so Perforce “recognizes” it and perhaps doesn’t set it to read-only.
Yet something sets the file to read-only anyways at some point. I also want to point out that the other files next to it do not have this issue, they’re not set as read-only.
Maybe it’s something within Unity that sets it? Deleting the file and reopening Unity regenerates the file and logs the error again.
For the record, this doesn’t impact the build game in any way, but the log clutters the console with irrelevant errors.
EDIT:
I am using the version 6000.0.24f)
