Unreal Engine 4
Unreal Engine 4 is the latest version of the videogame Engine Created By Epic Games
The content of this article was originally written on Unreal Engine wiki and adapted specifically for Arch Linux.
- 1 Prerequisites
- 2 Compilation
- 3 Troubleshooting
- 4 Additional Content
See Recommended Hardware.
Gain access to the source code
To gain access, login or register at Epic Games Accounts and provide an accessible GitHub username at the bottom of the Epic Games 'Connected Accounts Dashboard' page. You will then receive an invite to access the private Github repository.
You can compile manually from a downloaded GitHub release or install from AUR.
Compile manually from source code
You can get the most recent releases on GitHub as zips.
Generate project files:
$ make -j1
This will compile the Unreal Engine and the Unreal Editor.
Installing from the AUR
Unreal Engine 4 is available in the AUR as the AUR package. You might have to fix permissions for UE4 to precompile shaders on first launch:
sudo chmod -R a+rwX /opt/unreal-engine/Engine.
The package is ~70 GiB installed (after compiling shaders on first launch) and needs ~120 GiB to build with an output ABS package of ~9 GiB when compressed. This AUR package downloads ~10 GiB of source files plus ~5 GiB of dependencies.
Since the repository is private, you can set up an SSH key so your GitHub account is used to download the source.
The compilation can take from 20 minutes up to a few hours depending on your machine. As an example on a AMD FX-8350 (8 threads) with 16GB DDR3 on a SSD and Clang 3.8.1 takes roughly 40 minutes. (This doesn't include shaders compilation)
If the compilation fails you should try building the Editor using the Debug profile:
$ make UE4Editor-Linux-Debug
However, this might have some performance impact.
Another approach would be to use different clang version (e.g. 3.8 or 4.0)
If the editor doesn't start from the menu, or something doesn't work right, start it in a console and check the output for errors.
C++ code project problems
After creating a code project, the new project opens in a text editor instead of in UE4Editor as it should. After re-launching the editor, the new project shows up and can be opened, but on the first run, it takes a half-hour or so to compile, and since this happens in the background (no GUI) it might not seem to be doing anything. The CPU usage should show that it's still compiling, and you may want to launch the editor from a console to see progress.
If while trying to open the project in UE for the first time, you get a message about editor modules being out of date, you need to build the
UE4Editor target in your IDE. Do not abort this build, or you will brick UE4 and will need to reinstall
unreal-engine. Afterwards, it will open and ask you to rebuild the project class, after which you can actually start working on your new project.
Note that completing both of these rebuilds can very well take over an hour, depending on your system specs.
UE4's mouse-over tooltips might be rendered very slow. They can be disabled by adding to
Random freeze under KDE
Disable index file content in the KDE file search options.
Slow rendered tooltips in KDE
Epic suggest to allow compositing for the Unreal Editor, which is stopped by default. Source: https://www.ue4community.wiki/Legacy/Linux_Known_Issues#KDE
Blank window in Blueprint with multi-monitor configuration
For fix big blank window go to Edit Preferences -> User interface -> Enable Window Animation and activate the checkbox
The StarterContent project is installed to /opt/unreal-engine/Samples/StarterContent/StarterContent.uproject, you can browse to it from the launcher.
The marketplace apps can be downloaded using the launcher on Windows (or Mac), they are stored in:
/Program Files (x86)/Epic Games/Launcher/VaultCache/
Also there is an implementation of UE4 Marketplace Downloader written in JS.