Closed Acren closed 2 years ago
This error can typically comming if you have 2 unreal editor open in your system (look your task manager, sometime unreal can be start more than one). Another way, the source control setup are correctly setup ? In the right ui, have you a green circle to comfirm everything are setup about the source control ?
do you have git hooks set up for LFS?
Another way, the source control setup are correctly setup ? In the right ui, have you a green circle to comfirm everything are setup about the source control ?
Yep, always green circle and everything mostly works in editor.
do you have git hooks set up for LFS?
I'm not too sure - LFS appears to be working normally in most cases. Is there a way we can check this? There seem to be LFS related hooks (post-commit, post-merge, pre-push etc) in the hooks directory, if that's any indication.
Thanks again
I'm seeing this also
Could you give more information about reproduction?
This has not happened again. Sorry for the noise!
Hi, This is happening to me on the regular. Here are the steps to reproduce (on release 3.16):
Hi,
I'm also experiencing this 100%. I'm also unable to do anything much really. I followed the installation instructions (except I installed the plugin in the project not the editor) + I turned on lfs lock using the command line indicated in the logs.
Here is what I see if I right click in the Content browser: I don't have the option to checkout the file.
When I open the file and then try to save:
The only way to be able to edit a file is to manually lock the file
git lfs lock Project/Content/Blueprints/Actor/ActorName.uasset
Now I can edit, but when I commit, the file is still locked...
UE 5.3.2 Plugin 3.16 Azure Dev Ops Git Hosting git 2.45.2.windows.1 git credentials
When I start the project although the revision control is enabled, I see this the Revision Control Log:
Revision control is disabled
Revision control is disabled
Revision control is disabled
Revision control is disabled
When I press Accept settings, no change happens.
Thanks for your help.
Hey there and thanks for the plugin!
My team's been using it for a bit and there seems to be a somewhat common issue among us where files seem to be getting left as read-only even when they are checked out, and we're not sure what's causing it.
Then when Unreal tries to save the checked-out asset it fails because it's read-only, and as a result we have to spend a lot of time manually going into the filesystem in explorer and making files writable again so that we can save them.
Has anyone encountered an issue like this before? We're using UE 5.0 release with 3.0.4 of this plugin.
Much thanks!