Package Details: unreal-engine 4.15.1-1

Git Clone URL: https://aur.archlinux.org/unreal-engine.git (read-only)
Package Base: unreal-engine
Description: A 3D game engine by Epic Games which can be used non-commercially for free.
Upstream URL: https://www.unrealengine.com/
Keywords: 3D engine game UE4 Unreal
Licenses: custom:UnrealEngine
Conflicts: hardening-wrapper
Submitter: acerix
Maintainer: acerix (zerophase)
Last Packager: acerix
Votes: 14
Popularity: 1.249338
First Submitted: 2016-05-01 18:37
Last Updated: 2017-03-20 18:22

Latest Comments

CAPTNCAPS commented on 2017-03-16 17:16

Well I don't know what kinda fancy drivers you're using but last time I checked (which is just like a few months back) the nvidia drivers conflicted with all mesa packages... because the proprietary driver brings it's own OpenGL implementation!
Maybe you could let me know how that's supposed to work, because I sure didn't find anything about Mesa + Proprietary anywhere!

Anyway, this is getting offtopic. It was officially confirmed that Mesa 13+ is NOT supported, see the link. It is NOT an AMD issue.

zerophase commented on 2017-03-15 19:27

@CAPTNCAPS

It still needs mesa installed for the opengl functionality it uses. It just doesn't use their implementation. Use the proprietary drivers, not nouveau.

CAPTNCAPS commented on 2017-03-13 12:52

@zerophase
If you aer using Nvidias proprietary drivers, then you are not using Mesa, that's the whole point behind the proprietary driver.
And yes I do have an Nvidia card to test with, but nouveau is so unstable it can't even run my Desktop (KDE) and as you said, the proprietary driver works.

zerophase commented on 2017-03-04 13:50

@CAPTNCAPS I think it's an AMD issue. I'm running Mesa 17, and Unreal uses opengl 4.3 without issue. I'm on an NVidia card using their proprietary drivers.

Do you have an NVidia card to test with?

CAPTNCAPS commented on 2017-03-04 13:18

Just a note in case you don't know yet:
Unreal Engine 4 does currently NOT SUPPORT MESA 13+!

Officially confirmed: https://answers.unrealengine.com/questions/540613/ue4editor-not-starting-when-using-mesa-13.html

rmolin88 commented on 2017-02-01 11:31

@zerophase Thank you very much for the quick reply. That did it!

zerophase commented on 2017-01-31 01:26

@rmolin88 create a group for Unreal, and add every unreal file to that group. I believe arch frowns upon adding groups through aur packages.

rmolin88 commented on 2017-01-31 01:23

Hello guys. Thanks for the package.
I'm getting this error when I want to create a new c++ project:
Running /opt/unreal-engine/Engine/Binaries/DotNET/UnrealBuildTool.exe -makefile -kdevelopfile -qmakefile -cmakefile -codelitefile -project="/home/reinaldo/Documents/UnrealProjects/MyProject2/MyProject2.uproject" -game -engine -progress
Discovering modules, targets and source code for project...
Discovering modules, targets and source code for project...
Discovering modules, targets and source code for project...
UnrealBuildTool Exception: System.UnauthorizedAccessException: Access to the path "/opt/unreal-engine/Engine/Source/ThirdParty/PhysX/Lib/Linux/arm-unknown-linux-gnueabihf/st0Ik7rX" is denied.

Here is a link to a screenshot: https://drive.google.com/open?id=0B65GtWgJn1tFcnBSUmJSTzF1eHc
The file doesnt even exist. Should I change the /opt/unreal-engine folder to my user? Thanks in advance

acerix commented on 2017-01-29 21:06

@labotsirc Thanks for the solution, the same worked for me. I added hardening-wrapper to conflicts for now, although it would be better to turn off "HARDENING_PIE" or whatever is giving these errors in the build step, let me know if anyone has a better fix.

@zerophase Yes, I have 4 cores and 4 jobs in /etc/makepkg.conf:

MAKEFLAGS="-j4"

"make -j1" overrides that to use 1 job since the Unreal build tool has it's own multi-threading.

zerophase commented on 2017-01-17 00:24

@labotsirc No idea. Have you tried installing in a bare bones vm? You most likely won't be able to run the engine, but it should be able to compile. (driver issue)

I have a feeling something with your system configuration might be causing issues.

@acerix how many jobs do you have makepkg configured to start? Does it match your core count?

All comments