SourceControlSettings.ini is not created on some projects

Development Getting Started & Setup
,
1

Is there someone who knows why in some of our project the file
“C:\Perforce\ProjectA\Saved\Config\WindowsEditor\SourceControlSettings.ini”
is never created locally?

------------ Details follow:

  • We open ProjectA.uproject, setup source control (Perforce, workspace). We can checkout files. We close the editor, the file SourceControlSettings.ini is not created.

  • We perform the same operations on ProjectB.uproject (on same perforce depot), and the SourceControlSettings.ini IS created for that project.

  • No crash is visible in ProjectA.log (in fact the ProjectA.log and ProjectB.log are very similar).

  • We do not see any difference in the other .ini files (under …\ProjectX\Config\ and under …\ProjectA\Saved\Config\ )

  • We are using 5.4.1 (but it does the same issue when we use 5.4.4)

2

Hey @sbinetRodeoFxUe!

So this is interesting! Can I ask a few more questions?

  • Are you able to use the source control after you close and reopen?
  • Is there anything stopping you from using the source control on either client?
  • Are these clients on separate computers?
  • Are these clients at the same User level on Perforce?

Let us know!

3

To answer your questions:

  • No. When we re-open unreal editor (ProjectA), the source control is disconnected.
  • No. After opening ProjectA and enabling the source control (selecting Perforce + the workspace from the drop-down list), then we can perforce check-out from the editor.
  • No. The client are on the same computer. It is a very simple setup. The projects are simply in two folders under the same Perforce depot.
  • Yes, same user, same depot, same drive, same perforce client. The only difference is that each project is using a copy of the engine in a different folder.

D:\Unreal_Pipeline_Engines\ProjectA\5_4_1_Vanilla\Engine\Binaries\Win64\UnrealEditor.exe
D:\Unreal_Pipeline_Engines\ProjectB\5_4_1_Vanilla\Engine\Binaries\Win64\UnrealEditor.exe

4

Thanks for those!

Are you using a separate workspace for each?

Also the project is the only thing being held in the depot, you’re not uploading engine parts, is that correct?

5

Responses to Mind-Brain questions:

  • We are using the same workspace to hold both projects.
  • There are other projects in the same depot.
  • The depot is mapped as follows:
    //P4Depot/ProjectA/... //sbinet_MACHINENAME/ProjectA/...
    //P4Depot/ProjectB/... //sbinet_MACHINENAME/ProjectB/...
    //P4Depot/ProjectC/... //sbinet_MACHINENAME/ProjectC/...
  • We do not hold neither engines nor plugins in our Perforce depot .
1 Like
6

Ah that could be the issue.

Try using one project per workspace. The file may be limited to one workspace, I think logically that doesn’t make a whole lot of sense but frankly Perforce can be very obtuse sometimes.

7

Thanks Mind-Brain, but since it is only one of our project that is having this strange behavior (not creating the SourceControlSettings.ini), I think your suggestion has very-very little chance of success in our case. I will wait for another suggestion :slight_smile: .

8

Have you tried copying the .ini from one project to another and altering it? Would that be doable? I’ve never seen inside of one but most .ini’s are VERY simplistic and can be changed using notepad to fit the new use case.

I know that doesn’t solve WHY but it could allow you to move forward!

9

@Mind-Brain:
Last week I have performed the test you suggest.
I have tried to copy the .ini from one project to another and altering it (from ProjectB to ProjectA).

Then ProjectA behaves almost as expected:

When opening ProjectA the unreal source control is enabled and history works fine.

But if from the Unreal Editor I modify the source control configuration and quit Unreal, then the ProjectA .ini is not modified on disk!!! So the just-made modification is lost.

We are still trying to isolate the root cause of the problem. Any additional idea is welcome.