![]() You can later on move the folder to a system directory like. I can't recall exactly when you need to define the directory or when it occurs, but it's probably going to happen if you execute the game from a different directory (example: through a symlink/shortcut)I have overcomplicated everything: Just go to the directory where you extracted the game and try executing either a xonotic-linux-sdl or a xonotic-linux-glx (pick the 64 bit variants if on 64 bit system etc). Depending on where you execute the game from you might get a -basedir something issue after the game launches, just post it here if it happens. I'm not sure about how the executables are named but if they're not named as 32 and 64 bit ones then the one filename missing a specific number should be the missing architecture (example: having xonotic64-linux-sdl or however its named and xonotic-linux-sdl means xonotic-linux-sdl is 32bit and vice versa).Make sure you don't try to execute the win32 ones. This year we've seen Warsow open-source their game match-maker service. However, a Warsow 1.1 (or 1.5) update is still being worked on and it will be landing heavy with new features/improvements. The CPU architectures listed is where successful result uploads occurred, namely for helping to determine if a given test is compatible with various alternative CPU architectures.If you're using a monitor with overscan and are hacking you way around a modeline with xrandr and panning (which I'm 99.9% sure you are not) then sdl might not work fine with a reduced modeline, but other than that you should be fine with either.If you downloaded the archive from xonotic's website then you're more than likely to have both 32 and 64 bit executables. Before giving Warsow a try, I considered Xonotic to be the best FPS that can be played under Linux so from the moment that I launched Warsow I had the intention. It's been a long time since last having anything to report on with the Warsow, the open-source first person shooter powered by the Qfusion game engine. This benchmark has been successfully tested on the below mentioned architectures. RE: Warsow - LeeStricklin - 09-25-2011 sees a Warsow thread on a piece of the internet he lurks Get this crap outta here. there might be also other changes included to that. Note: data isnt very accurate because X DRI3 was broken around that time so the gap between useful numbers was over week, i.e. This test profile binary relies on the shared libraries libSDL2-2.0.so.0, libpthread.so.0, libtheoradec.so.1, libm.so.6, libdl.so.2, librt.so.1, libuuid.so.1, libatomic.so.1, libc.so.6, libasound.so.2, libpulse.so.0, libX11.so.6, libXext.so.6, libXcursor.so.1, libXinerama.so.1, libXi.so.6, libXfixes.so.3, libXrandr.so.2, libXss.so.1, libXxf86vm.so.1, libdrm.so.2, libgbm.so.1, libwayland-egl.so.1, libwayland-client.so.0, libwayland-cursor.so.0, libxkbcommon.so.0, libdecor-0.so.0, libcairo.so.2, libpulsecommon-15.0.so, libdbus-1.so.3, libxcb.so.1, libXrender.so.1, libwayland-server.so.0, libexpat.so.1, libffi.so.8, libpixman-1.so.0, libfontconfig.so.1, libfreetype.so.6, libpng16.so.16, libxcb-shm.so.0, libxcb-render.so.0, libz.so.1, libsndfile.so.1, libX11-xcb.so.1, libsystemd.so.0, libasyncns.so.0, libwrap.so.0, libapparmor.so.1, libXau.so.6, libXdmcp.so.6, libbrotlidec.so.1, libFLAC.so.8, libvorbis.so.0, libvorbisenc.so.2, libopus.so.0, libogg.so.0, liblzma.so.5, libzstd.so.1, liblz4.so.1, libcap.so.2, libgcrypt.so.20, libnsl.so.2, libbsd.so.0, libbrotlicommon.so.1, libgpg-error.so.0, libtirpc.so.3, libmd.so.0, libkrb5.so.3, libk5crypto.so.3, libkrb5support.so.0, libkeyutils.so.1, libresolv.so.2. According to the test data, the performance drop was largest for GLbenchmark 2.7 T-Rex
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |