Why redundant info in the graphs? Why two kinds of graphs for similar kind of data? Some people prefer to deal only with basic info such as average FPS or average frametimes, while others prefer more advanced info such as percentiles or want to see graphs over time, choose the ones you're comfortable with and ignore the others. Why not Min/Max bars/values? Because they're pretty much useless if you want to see how performance varies over time, there are some graphs for that instead, or check the "Percentiles" results. Why choose Medium settings? Because Medium is the sweet spot for my older card. Is also easier here to edit the info (if I make mistakes) or add some more later. Why not all relevant (system/settings) info in the video? I used to put them in the video, but people seems to ignore them. Usage data is collected at one second intervals and written directly to RAM in order to cause no drive activity. By default the game benchmark is divided in three sections with their own results, however in order to simplify the graphs I combined them together in a single section. Nevertheless I set the Textures to Very High on Linux too, so keep that in mind when looking at the graph results (my card has only 3 GB VRAM). The "Very High" settings on Linux doesn't use Very High Textures (needs more than 4 GB VRAM) as the Windows version does. Lens Flares removed because this ain't freaking Star Trek and J.J Abrams has no saying in my house. Ambient Oclusion set to ON since is the only option on Linux. The test were done using the default settings as much as possible, so no extra AA settings, only FXAA, also: In this case I had the overlay/FPS counter enabled. The video comparison was recorded with the game running at Medium settings. I found few times in the past that the overlay affects Vulkan performance, and even here it drops the perf just a lower bit. The benchmark data was collected with the Steam overlay disabled. All tests at 1920x1080 resolution, performance mode enabled for the CPU. All tests were done after several dry runs/restarts and allowing time for shaders to be compiled first. Videos recorded with an external Blackmagic Intensity Pro 4K card and Media Express recording software (no game performance loss). The game is Vulkan-only on Linux and DX11-DX12 on Windows. Windows 10 Pro, Radeon Software Adrenalin Edition 18.3.4 Note: AMDGPU/RADV is not enabled by default on this older card, you'll have to do it manually. i7-4790K with Hyper-threading disabled. For some newer cards though the game still needs at least Mesa 18. That being said, even with the older SteamOS's Mesa the game still runs with (roughly) just 3 FPS lower. Usually I make my benchmarks on SteamOS, but since SteamOS has an older Mesa version (17.2.4), I used here Ubuntu with Padoka PPA and a newer kernel version. I expect also that Nvidia results to be somewhat better, considering that RADV still has some catch up to do.įor more benchmarks and info about the Linux version of this game check these sites: Keep in mind that the card used here is below game's requirements, but is the newest card I have now (sadly my Nvidia died peacefully in its sleep).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |