Major - UEFN - UEFN locks access to source control, causing commit conflicts

General Issues and Bug Reporting
,
1

I committed a material change to a server, then updated another device to see the changes, but I got the following error from source control:

Update to HEAD: Problem running log
Failed to run the WC DB work queue associated with 'C:\Users\apapo\Documents\Fortnite Projects\SVN\GemstoneTycoon\Plugins\GemstoneTycoon\Content\Materials',
work item 169 (file-install GemstoneTycoon/Plugins/GemstoneTycoon/Content/Materials/Diamond_Sticker.uasset 1 0 1 1)
Access is denied.
Can't move 'C:\Users\apapo\Documents\Fortnite Projects\SVN.svn\tmp\svn-994A54B8' to 'C:\Users\apapo\Documents\Fortnite
Projects\SVN\GemstoneTycoon\Plugins\GemstoneTycoon\Content\Materials\Diamond_Sticker.uasset': Access is denied. (2 entries)

Seems that having UEFN open locks certain aspects of the editor, so when a repository is updated, it get corrupted. This is happening with almost anything I commit, and I have to delete the working copy to get another one from the server when that happens. Would love if I could figure out a way for this to not happen

2

After asking around, it seems like we do not recommend updating from source control while the editor is running.

3

Yup, I figured that out and told my teammates what to do if they have it open and it corrupts everything

I found that there are specific things that cause it (like materials), so maybe if those are tracked down and not made to lock the project, that would be beneficial for all source control types and help us not have to close the project when trying to grab something a teammate sent us.