With the release of League of Legends Patch 10.16 there is now official (beta) support for the Direct X11 Rendering backend for League of Legends (LoL). I have conducted a side by side comparison between the old rendering backend D3D9 (DirectX 9) and the new D3D11 (DirectX 11). If you want to enable DX11 in your own game you can follow the instructions provided by Riot here.
RTX 2080 8GB
i7 9700K @ 4.6Ghz
16GB DDR4 RAM
Windows 10 1909
League of Legends
Medium, Shadows Disabled
240 FPS Framerate Limit (Recommend)
DX9 Average: 168.6
DX11 Average: 175.2
Performance Advantage FPS: 6.5+ DX11
Performance Gain Percent: 3.91%
Note: The impact of OBS with these settings is as low as ~5FPS. When running the tests I had no additional software running other than OBS and League of Legends. In a real use case even if you don’t record/stream the performance impact should be similar to having Chrome/Firefox open with a YouTube video or Discord ect.
H.265 NVENC Encoder Max Quality preset, 2300kbps Bitrate, 1280×720
Long time no see iOS/Android enthusiasts. I wanted to share a useful app I created to automated the process of running checkra1n for arm64 (Android Phone/Tablet) in TWRP (Team Win Recovery Project). This is a fully open source program (excluding the checkra1n binary) licensed under Zero Clause BSD. View it on GitHub here.
TWRP has a built in functionality to queue commands for the next recovery boot. These commands are located in /cache/recovery/command which is just a text file that TWRP reads. This is the same functionality that allows Over The Air (OTA) updates for custom ROMs to boot and reflash themselves.
Using this queue system the checkra1n TWRP app copies an Open Recovery Script (flashable .zip) to /data/checkra1n/checkra1n.zip and boots to recovery by invoking reboot recovery. The included checkra1n.zip then executes and boots back to system reboot system after the checkra1n log message of [*]: All Done is received.
This will not increase the comparability of checkra1n for Android devices but my 2015 Nexus 5X and 2018 Mi Mix 3 both run this application flawlessly. If you were already using your Android device to run checkra1n this should make things easier for you as you don’t need to interact with a shell at all on invoke/remember commands.
To flash the .zip within TWRP without running the app, which is useful if you leave your Android turned off until you need it for a retether, you can find the flashable Open Recovery Script in /data/checkra1n/ and flash it from the Install menu within TWRP.
Happy jailbreaking! (please report bugs on the Github Bug Tracker)
Note the location you downloaded the file to. You will need to know the absolute path the file is located so you can execute it from a terminal command line.
Once you have the file downloaded boot your Android phone into Custom Recovery. Running the tool from Custom Recovery instead of directly inside Android you don’t need to worry about a conflict between different processes fighting over the USB controller. I wasn’t able to run checkra1n from a fully booted Android 10 but I was able to run it from Custom Recovery! Your luck may vary but Custom Recovery is the most reliable option.
Open a Terminal in Custom Recovery (TWRP 3.3.1-17 was used in my video) and change directory to where you saved checkra1n
Next we need to add the execute flag to the binary so it can be run as a program
chmod +x checkra1n
Finally we can run checkra1n from Android
./checkra1n -c -v
Connect your iOS device using your USB-C to USB-A adapter and your Lightning cable.
Now we need to manually enter DFU mode on our iOS device. This is done differently on different devices so if you are unsure just look up “How to put iPhone X into DFU mode” replacing iPhone X with your model and you should find some button combinations to enter DFU.
If you have successfully put your iOS device into DFU and it is connected to your Android Phone running checkra1n the program should recognize the DFU mode USB device and run the exploit!
Hey gamers, this is downthecrop and today we have a very special video explaining the best Linux Distro recommendations for gaming in 2020.
I’ll be explaining some more technical reasons for why the distribution you decide to choose is not that important. The most important thing to remember for gaming on GNU+Linux is that you need to have your Window Manager Compositor or DE Compositor disabled for your games. This can be done in Compton (Picom) compositor and the GNOME Mutter Compositor. The performance impact of an incorrectly configured compositor will outweigh any effect the light weight Desktop Environment might provide.
Linux Gaming Drivers
Using the latest drivers will very likely have an effect on performance, as of writing this, Ubuntu LTS 18.04 is using Nvidia Linux Driver Version 430.64 and Manjaro is using Nvidia Linux Driver Version 440.59. Bleeding edge distros like Arch Linux, Void Linux, and Manjaro will all provide up to date Kernels and the latest Linux Drivers for both AMD and Nvidia. Slow annual releases like Ubuntu are known to be more stable due to them waiting to push updates to driver and applications until they have been tested for a longer time. You can bypass this slower release cycle with third-party PPA’s or installing through the .run script available from Nvidia/AMD’s websites.
Compositors and Gaming Performance in Linux
A compositor is in charge of an off screen buffer for each application window in a desktop environment. Compositing windows managers are responsible for things like desktop transparency and drop shadow effects.
Without a compositor each application is rendered directly which allows for better gaming performance.
GNOME uses a compositor called Mutter
Compton (now forked to Picom) can be used for OpenBox/LXQt
Your compositor settings will have the largest impact on performance. This is to say that the distribution of GNU+Linux you choose is not very important. The settings of your compositor can greatly affect your FPS. Make sure that all fullscreen applications are ignored or bypass the Compositor. Completely disabling the compositor is the best option as it may increase performance by removing the background buffer of your application windows (X11 Clients) and the output to your screen.
Really just disable your compositor and you can use anything you like. Fedora Linux, Gentoo, Elementary OS, use anything you like for gaming. If you have the RAM overhead available most DE’s really won’t make a difference in gaming performance.
Manjaro is probably the best option for most people new or returning to gaming on GNU+Linux. Easily to install. Easy to use. Easy to update.
Manjaro is a rolling release which means that it will always have the latest versions of software after you’ve updated. There is no Manjaro 19.04 ect because ALL versions are the latest version you just need to re-sync with the update server.
Manjaro has out of the box support for non-free drivers and a graphical utility for installing them as well. 32-bit libraries which are a common issue among those new to Linux gaming are easy to install too.
MX Linux by its design is going to be a little bit out of date compared to Manjaro/Arch/Void and that’s because it’s not rolling release, and it’s based on Debian which is a very slow to update, stable distro.
MX Linux comes with options for non-free drivers during the install and is also systemd free. Yes! No systemd to mess with your gaming.
I suggest MX Linux to people who are uncomfortable with Arch/Manjaro and just want a system they are familiar with. The XFCE default spin is very similar to Unity or GNOME on Ubuntu so it should be easy to figure out for anyone new to Linux gaming.