We do often include affiliate links to earn us some pennies. See more here.

Unreal Tournament Has Public Builds Available For All Platforms Now

By anchor -
The new Unreal Tournament is being built out in the open and with community input as we already know, but now anyone who is logged into their forum can get access to the builds.

All you need to do is register and login on their official forum, and then proceed to the alpha topic to see the download links. The Linux download comes in at just under 800mb, so those with little bandwidth should hold off.

See a video of it in action below (the video is a bit old though):
https://www.youtube.com/watch?v=NQ9iN90b2wU

It doesn't seem to work on my end:
image
It might work for you, so if you do get it to work be sure to let people know how in the comments.

Update
To get it to run you need to do this in terminal:
QuoteEngine/Binaries/Linux/UE4 UnrealTournament -SaveToUserDir

Thanks, KimmoKM! Article taken from GamingOnLinux.com.
0 Likes
The comments on this article are closed.
19 comments
Page: 1/2»
  Go to:

Lintux Oct 22, 2014
Same Error here on Ubuntu 14.10
pmasterBR Oct 22, 2014
I have this problem also on Linux, guess I'll have to wait out a new update. Ubuntu 12.04 64 bits.
lave Oct 22, 2014
can you PLEASE stop posting that Fatal1ty movie ever again. that guy made himself a name with stuff like gamerfood but is quite bad by nowadays standarts and kinda fails to deliver what unreal tournament looks like if played right.


heres a proper one: not intending to shitstorm at fatal1ty (altho i should, just like every fellow quaker) but this really is way better
http://www.youtube.com/watch?v=0CwDCXL2858
Sslaxx Oct 22, 2014
Looking like they just released this without testing it.
pete910 Oct 22, 2014
View PC info
  • Supporter Plus
Don't work for me neither. :(
KimmoKM Oct 22, 2014
Windows version had a batch file that gave UE4.exe arguments UnrealTournament -SaveToUserDir

Try running this command instead: Engine/Binaries/Linux/UE4 UnrealTournament -SaveToUserDir
masteredu Oct 22, 2014
It has nothing to do with UserDir, but you are right, you have to open it with the UE4 engine, like KimmoKM said. ./UE4 UnrealTournament or something like this.

Ask on #UE4Linux on Freenode IRC for more help.
Beamboom Oct 22, 2014
Quoting: KimmoKMWindows version had a batch file that gave UE4.exe arguments UnrealTournament -SaveToUserDir

Try running this command instead: Engine/Binaries/Linux/UE4 UnrealTournament -SaveToUserDir

I can confirm this works.
Liam Dawe Oct 22, 2014
Quoting: lavecan you PLEASE stop posting that Fatal1ty movie ever again. that guy made himself a name with stuff like gamerfood but is quite bad by nowadays standarts and kinda fails to deliver what unreal tournament looks like if played right.


heres a proper one: not intending to shitstorm at fatal1ty (altho i should, just like every fellow quaker) but this really is way better
http://www.youtube.com/watch?v=0CwDCXL2858
When I approved the article I checked the video and it's fine with me. Simple as that and it won't be changed.
Orkultus Oct 22, 2014
Quoting: Beamboom
Quoting: KimmoKMWindows version had a batch file that gave UE4.exe arguments UnrealTournament -SaveToUserDir

Try running this command instead: Engine/Binaries/Linux/UE4 UnrealTournament -SaveToUserDir
I can confirm this works.

I ran it with this command, the window opened up, but then gave me this error.

EngineCrashHandler: Signal=11
[2014.10.22-21.01.26:016][ 0]LogLinux: === Critical error: ===
Unhandled Exception: SIGSEGV: invalid attempt to access memory at address 0x00000003

[2014.10.22-21.01.26:016][ 0]LogLinux: Assertion failed: Assertion failed: NumDirtyVectors [File:D:\BuildFarm\buildmachine_++depot+UE4-UT\Engine\Source\Runtime\OpenGLDrv\Private\OpenGLShaders.cpp] [Line: 1993]



[Callstack] 02 0x00007f316ccf8a13 ReportCrash(FLinuxCrashContext const&)
[Callstack] 03 0x0000000000417bbf EngineCrashHandler(FGenericCrashContext const&)
[Callstack] 04 0x00007f316ccfac0c PlatformCrashHandler(int, siginfo*, void*)
[Callstack] 05 0x00007f316d350200 /usr/lib/libpthread.so.0(+0x10200) [0x7f316d350200]
[Callstack] 06 0x00007f316ccfb193 FOutputDeviceLinuxError::Serialize(wchar_t const*, ELogVerbosity::Type, FName const&)
[Callstack] 07 0x00007f316cd7999c FOutputDevice::Logf(wchar_t const*, ...)
[Callstack] 08 0x00007f316cd68bcb FDebug::AssertFailed(char const*, char const*, int, wchar_t const*, ...)
[Callstack] 09 0x00007f314fa2d0b6 FOpenGLShaderParameterCache::CommitPackedGlobals(FOpenGLLinkedProgram const*, int)
[Callstack] 10 0x00007f314fa2c428 FOpenGL[2014.10.22-21.01.26:016][ 0]LogExit: Executing StaticShutdownAfterError
Starting ../../../Engine/Binaries/Linux/CrashReportClient
[2014.10.22-21.01.26:032][ 0]LogHAL: FLinuxPlatformProcess::CreateProc: spawned child 14782
Aborted (core dumped)

Running Arch Linux 64bit.
While you're here, please consider supporting GamingOnLinux on:

Reward Tiers: Patreon. Plain Donations: PayPal.

This ensures all of our main content remains totally free for everyone! Patreon supporters can also remove all adverts and sponsors! Supporting us helps bring good, fresh content. Without your continued support, we simply could not continue!

You can find even more ways to support us on this dedicated page any time. If you already are, thank you!
The comments on this article are closed.