thedarthtux Benchmarks: 49
Ray tracing test 2 4K High Settings SSOA Disabled MSAA Disabled
Distro: Garuda Linux Kernel: 6.0.12-zen1-1-zen GPU Driver: 4.6 Mesa 22.3.1 GPU: Radeon RX 6800/6800 XT / 6900 XT CPU: AMD Ryzen 9 3950X 16-Core Processor RAM: 65 GB
Ray tracing test 1 4K High Settings SSOA Disabled MSAA X2
4K Ray tracing High Settings DLSS/FSR Disabled
Distro: Steam Runtime 2 (soldier) Kernel: 6.0.12-zen1-1-zen GPU Driver: GPU: Radeon RX 6800/6800 XT / 6900 XT CPU: AMD Ryzen 9 3950X 16-Core Processor RAM: 65 GB
4K Ray tracing Very High Settings DLSS/FSR Disabled
Very High Settings Ray tracing: High DLSS/FSR Disabled ****THERE SEEMS TO BE SOMETHING GOING ON WITH CRYSIS 3 THAT IS CAUSING MANGOHUD NOT RECORD FRAME RATES PROPERLY. IN GAME AVG FPS WAS AROUND 35fps**** https://odysee.com/@GamingonLinux:0/Linux-Experience---RX-6900XT-Ray-Tracing-in-Crysis-3-Remastered:3?r=5CJHzrTZKQDYsR6H6N57eMUiYQtzBxgq
Checking the ray tracing performance uplift going from the Sapphire Nitro+ RX 6900 XT to the Sapphire Nitro+ RX 7900 XTX
Ray Tracing Test Ultra Settings FSR Disabled HD Textures
Full classic match Mesa 22.3.3 SAM enabled MSAA x4 Ultra Windowed borderless Vulkan Driver: RADV Game drops to 60fps and below during and while transitioning into cut scenes and replays
Distro: Steam Runtime 2 (soldier) Kernel: 6.1.5-zen2-1-zen GPU Driver: GPU: Radeon RX 6800/6800 XT / 6900 XT CPU: AMD Ryzen 9 3950X 16-Core Processor RAM: 65 GB
Level of Detail: Ultra Texture Quality: High SSAO: Off Steam Launch Options: AMD_VULKAN_ICD=RADV ENABLE_VKBASALT=1 OBS_VKCAPTURE=1 MANGOHUD=1 DXVK_ASYNC=1 WINEFSYNC=1 VKD3D_FEATURE_LEVEL=12_2 VKD3D_CONFIG=dxr11 RADV_PERFTEST=sam,rt %command%
Distro: Steam Runtime 2 (soldier) Kernel: 6.1.1-zen1-1-zen GPU Driver: GPU: Radeon RX 6800/6800 XT / 6900 XT CPU: AMD Ryzen 9 3950X 16-Core Processor RAM: 65 GB
Ultra settings FSR: Disabled VRS: Disabled (ray tracing in Hitman III even though enabled in the settings does not seem to work under Linux yet)
Ultra Settings DLSS/FSR/XeSS: Disabled VRS: Off (ray tracing in Hitman III even though enabled in the settings does not seem to work under Linux yet)
High/Ultra Settings RT: High + Reflections FSR: Disabled VRS: 4x No menu items captured in benchmark and all cut senses intractable and in engine
Testing FSR 3.1 with very high ray tracing at 4K. This is a very short run. Upscaling with XeSS is best for ray tracing than FSR 3,1 quality setting
Distro: Steam Runtime 3 (sniper) Kernel: 6.9.7-zen1-1-zen GPU Driver: GPU: AMD Radeon RX 7900 XTX (RADV NAVI31) CPU: AMD Ryzen 9 3950X 16-Core Processor RAM: 65 GB
High Setting FSR: Disabled
High Settings FSR: Disabled
Ultra/Very High/High Settings FSR: Disabled VRS: Disabled
Ultra Settings FSR: Disabled VRS: Disabled
Testing Vulkan at New Babbage
Distro: Steam Runtime 3 (sniper) Kernel: 6.12.4-zen1-1-zen GPU Driver: GPU: AMD Radeon RX 7900 XTX (RADV NAVI31) CPU: AMD Ryzen 9 3950X 16-Core Processor RAM: 65 GB
First benchmark at Loreville. Have not decided on the best route yet
Distro: Garuda Linux Kernel: 6.8.8-zen1-1-zen GPU Driver: GPU: AMD Radeon RX 7900 XTX (RADV NAVI31) CPU: AMD Ryzen 9 3950X 16-Core Processor RAM: 65 GB
Just testing performance in Area 18 with AMD's FSR vs CIG's TSR in Vulkan under XOrg. Visually CIG's TSR has much better image stability Test Circuit Path: Habs building entrance -> Area 18 Plaza -> Astro Armada -> Food Court -> G-Loc Bar -> Twitch Pacheco -> Convention Centre -> Riker Memorial Spaceport -> Habs building entrance
Revisiting Vulkan behaviour issue after collecting other backers' experiences and testing. It seems the issue is related to Wayland. Vulkan on XOrg gives similar results as DX11 but is orders of magnitude smoother Test Circuit Path: Habs building entrance -> Area 18 Plaza -> Astro Armada -> Food Court -> G-Loc Bar -> Twitch Pacheco -> Convention Centre -> Riker Memorial Spaceport -> Habs building entrance
This is not a really scientific comparison. However, I am comparing the frame time spikes above 100 ms between both APIs
Distro: Garuda Linux Kernel: 6.8.7-zen1-2-zen GPU Driver: GPU: AMD Radeon RX 7900 XTX (RADV NAVI31) CPU: AMD Ryzen 9 3950X 16-Core Processor RAM: 65 GB
This is not a really scientific comparison. I removed all the frame time spikes above 100 ms. I have those in the a different benchmark. The DX11 file has also been reduced to the last few frames to align with the Vulkan log because I started logging the DX11 run earlier than I did the Vulkan one.
Distro: Garuda Linux Kernel: 6.2.1-zen1-1-zen GPU Driver: 4.6 Mesa 23.1.0-devel GPU: Radeon RX 7900 XT/7900 XTX CPU: AMD Ryzen 9 3950X 16-Core Processor RAM: 65 GB
Comparing Alpha 3.17.5 Live to Alpha 3.18 PTU at New Babbage
Testing my theory that the issue at Orison is not the clouds but other things being rendered at Green Circle, Cloudview Centre. It does make some sense that the High settings get slightly higher frame rates because High pushes the GPU more than turning the clouds Off
Distro: Garuda Linux Kernel: 6.1.12-zen1-1-zen GPU Driver: 4.6 Mesa 23.1.0-devel GPU: Radeon RX 7900 XT/7900 XTX CPU: AMD Ryzen 9 3950X 16-Core Processor RAM: 65 GB
Determining performance uplift going from the Sapphire Nitro+ RX 6900 XT to the Sapphire Nitro+ RX 7900 XTX at Orison with clouds Medium at Green Circle Cloudview Centre. Medium is the recommended settings for clouds because high still uses the CPU in ways it should not. CIG are aware of this issue
Distro: Garuda Linux Kernel: 6.1.8-zen1-1-zen GPU Driver: 4.6 Mesa 22.3.3 GPU: Radeon RX 6800/6800 XT / 6900 XT CPU: AMD Ryzen 9 3950X 16-Core Processor RAM: 65 GB
Determining performance uplift going from the Sapphire Nitro+ RX 6900 XT to the Sapphire Nitro+ RX 7900 XTX at Orison with clouds off and set to high at Green Circle, Cloudview Centre.
Testing Quantum Travel between MicroTech and Crusader at 4K in 400i with RX 6900 XT (mesa-git 22.3.3) vs RX 7900 XTX (mesa-git 23.1)
Distro: Garuda Linux Kernel: 6.1.7-zen1-1-zen GPU Driver: 4.6 Mesa 22.3.3 GPU: Radeon RX 6800/6800 XT / 6900 XT CPU: AMD Ryzen 9 3950X 16-Core Processor RAM: 65 GB
Logging the performance delta between Quantum Travel in first person view and Quantum Travel in third person view (i.e. outside ship camera). This comparison is to see the performance drop associated with the ship cockpit UI/HUD
Testing performance uplift from Sapphire Nitro+ RX 6900 XT to Sapphire Nitro+ RX 7900 XTX at New Babbage
Testing the WINE_CPU_TOPOLOGY for AMD Zen CCX usage in Star Citizen based on the LUG recommendation (https://github.com/starcitizen-lug/knowledge-base/issues/6)
Distro: Garuda Linux Kernel: 6.1.9-zen1-1-zen GPU Driver: 4.6 Mesa 22.3.4 GPU: Radeon RX 6800/6800 XT / 6900 XT CPU: AMD Ryzen 9 3950X 16-Core Processor RAM: 65 GB
Testing my theory that the issue at Orison is not the clouds but other things being rendered at Green Circle. It does make some sense that the High settings get slightly higher frame rates because High pushes the GPU more than turning the clouds Off
Very High There were unrealistic spikes in frame rates during the run. Actually observed fps was ~17fps Avg and 31fps Max. So benchmark is currently invalid till I rerun
Very High Settings Walking around Area 18 and flight to outside atmosphere and entry into QT
Very High Settings Run from New Babbage and flight to Area 18 hospital
Very High Settings Walking around Area 18 then flying to MIC-L1
Very High Settings Moving around all main platforms in Orison
4K Very High Render Resolution 1800p
Distro: Garuda Linux Kernel: 5.16.3-zen1-1-zen GPU Driver: 4.6 Mesa 21.3.5 GPU: Radeon RX 6800/6800 XT / 6900 XT CPU: AMD Ryzen 9 3950X 16-Core Processor RAM: 65 GB
4K Very High Test Run Between New Babbage and Area 18
Testing FSR 3.1 Performance with Frame Generation Native vs FSR Quality
Distro: Steam Runtime 3 (sniper) Kernel: 6.9.5-zen1-1-zen GPU Driver: GPU: AMD Radeon RX 7900 XTX (RADV NAVI31) CPU: AMD Ryzen 9 3950X 16-Core Processor RAM: 65 GB
Testing FSR 3.1 Native AA with and without frame generation 4K/2160p
4K Native Very High