Engine Source Installation and Team Deployment Recommendation

Development Getting Started & Setup
, , ,
11

Ok, mate, here’s a plan.

  1. Build engine
  2. Register engine
  3. Change Registry parameter name to something like “MyCustom4.4”
  4. Run engine association
  5. …
  6. PROFIT

Now the only thing your mates will do is just renaming registry parameter after engine registration. You can even write a simple script for it. Then your .uproject file will be like:

{
	"FileVersion": 3,
	"EngineAssociation": "MyCustom4.4",
	"Category": "",
	"Description": "",
	"Modules": [
		{
			"Name": "MyProject",
			"Type": "Runtime",
			"LoadingPhase": "Default"
		}
	]
}

and you won’t need custom uproject file for every developer.

OR more difficult way.

  1. Edit Your UnrealVersionSelector and make it not to generate some random GUID but write your “MyCustom4.4” there instead.
  2. Build your engine
  3. Run UVS.
  4. Run engine association

And that’s it.

What UnrealVersionSelector does?
It checks if this folder to register is already in registered installations list. If not it registers it. If there’s no launcher installed it registers file association and context menu options to UVS.